Skip to content
Fencer Intel
high 7.1

CVE-2026-107152 json

Rubygem-smart_proxy_dynflow: dynflow console authorizes any client certificate the capsule ca signed

published 2d ago modified yesterday also EUVD-2026-124668

cvss
7.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 20%
public exploits
0
none known

Summary

An improper authentication vulnerability has been found in the task console in the smart_proxy_dynflow package. The console accepts any client certificate signed by the capsule's certificate authority. It does not check the list of servers the capsule trusts. A low-privileged network attacker or user must already hold such a certificate. They can open the console and read job details. Those details include passwords when a job was given them. They can also cancel a running task.

Patch / fix

  • Red Hat Red Hat Satellite 6.16 for RHEL 8 0:0.9.3-2.el8sat
  • Red Hat Red Hat Satellite 6.16 for RHEL 9 0:0.9.3-2.el9sat
  • Red Hat Red Hat Satellite 6.17 for RHEL 9 0:0.9.4-2.el9sat
  • Red Hat Red Hat Satellite 6.18 for RHEL 9 0:0.9.4-2.el9sat
  • Red Hat Red Hat Satellite 6.19 for RHEL 9 0:1.0.0-3.el9sat

Is CVE-2026-107152 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-107152 updated cvss 7.1

rubygem-smart_proxy_dynflow: Dynflow console authorizes any client certificate the capsule CA signed

  • Red Hat Satellite 6.16 for RHEL 8 rubygem-smart_proxy_dynflow 0.9.3-2.el8sat Red Hat Satellite 6.16 for RHEL 9 rubygem-smart_proxy_dynflow 0.9.3-2.el9sat
    fixed: vendor fix RHSA-2026:99949
  • Red Hat Satellite 6.17 for RHEL 9 rubygem-smart_proxy_dynflow 0.9.4-2.el9sat
    fixed: vendor fix RHSA-2026:99950
  • Red Hat Satellite 6.18 for RHEL 9 rubygem-smart_proxy_dynflow 0.9.4-2.el9sat
    fixed: vendor fix RHSA-2026:99952
  • Red Hat Satellite 6.19 for RHEL 9 rubygem-smart_proxy_dynflow 1.0.0-3.el9sat
    fixed: vendor fix RHSA-2026:100120
  • Red Hat Satellite 6.16 for RHEL 8 candlepin 4.4.26-2.el8sat, foreman 3.12.0.26-1.el8sat, satellite 6.16.15-1.el8sat, python-pyjwt 2.15.1-1.el8pc, rubygem-puma 6.4.3-2.el8sat, rubygem-crass 1.0.8-1.el8sat, +30 more Red Hat Satellite 6.16 for RHEL 9 candlepin 4.4.26-2.el9sat, foreman 3.12.0.26-1.el9sat, satellite 6.16.15-1.el9sat, python-pyjwt 2.15.1-1.el9pc, rubygem-puma 6.4.3-2.el9sat, rubygem-crass 1.0.8-1.el9sat, +30 more Red Hat Satellite 6.17 for RHEL 9 candlepin 4.4.26-2.el9sat, foreman 3.14.0.26-1.el9sat, satellite 6.17.13-1.el9sat, python-pyjwt 2.15.1-1.el9pc, rubygem-puma 6.6.0-2.el9sat, rubygem-crass 1.0.8-1.el9sat, +35 more Red Hat Satellite 6.18 for RHEL 9 candlepin 4.6.7-2.el9sat, foreman 3.16.0.29-1.el9sat, satellite 6.18.11-1.el9sat, rubygem-puma 6.6.1-2.el9sat, rubygem-crass 1.0.8-1.el9sat, ansible-core 2.16.19-4.el9sat, +27 more Red Hat Satellite 6.19 for RHEL 9 candlepin 4.7.7-2.el9sat, satellite 6.19.6-1.el9sat, createrepo_c 1.2.6-1.el9pc, foreman 3.18.0.19-1.el9sat, rubygem-crass 1.0.8-1.el9sat, satellite-cli 6.19.6-1.el9sat, +34 more
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
yesterday

Exploit prediction

0.27% chance of exploitation in the next 30 days, higher than 20% of all scored CVEs (FIRST EPSS, 2026-11-14).

CVSS scores

assigned by version score vector
CNA 3.1 7.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N

Affected products

  • Red Hat Red Hat Satellite 6.16 for RHEL 8
  • Red Hat Red Hat Satellite 6.16 for RHEL 9
  • Red Hat Red Hat Satellite 6.17 for RHEL 9
  • Red Hat Red Hat Satellite 6.18 for RHEL 9
  • Red Hat Red Hat Satellite 6.19 for RHEL 9

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.