CVE-2026-107152

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

  • High 7.1

Description

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.

Key facts

Published
12 Nov 2026
Last changed
13 Nov 2026
Assigned by
redhat
EPSS
0.274% likely to be exploited in the next 30 days, higher than 20.047% of CVEs (scores for 15 Nov 2026)
SSVC (CISA)
Exploitation: none; Automatable: no; Technical impact: partial

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 7.1CVSS 3.1, Highfrom the CNA (redhat)CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N

What to do

  • Red Hat is not aware of a practical temporary workaround that fully mitigates this issue or meets Red Hat Product Security's standards for usability, deployment, applicability, or stability. Customers are advised to apply the relevant security updates when they become available.CNA workaround statement

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
Red HatRed Hat Satellite 6.16 for RHEL 8
  • Default status: affected
  • 0:0.9.3-2.el8sat up to but excluding * (unaffected)
Red HatRed Hat Satellite 6.16 for RHEL 8
  • Default status: affected
  • 0:0.9.3-2.el8sat up to but excluding * (unaffected)
Red HatRed Hat Satellite 6.16 for RHEL 9
  • Default status: affected
  • 0:0.9.3-2.el9sat up to but excluding * (unaffected)
Red HatRed Hat Satellite 6.16 for RHEL 9
  • Default status: affected
  • 0:0.9.3-2.el9sat up to but excluding * (unaffected)
Red HatRed Hat Satellite 6.17 for RHEL 9
  • Default status: affected
  • 0:0.9.4-2.el9sat up to but excluding * (unaffected)
Red HatRed Hat Satellite 6.17 for RHEL 9
  • Default status: affected
  • 0:0.9.4-2.el9sat up to but excluding * (unaffected)
Red HatRed Hat Satellite 6.18 for RHEL 9
  • Default status: affected
  • 0:0.9.4-2.el9sat up to but excluding * (unaffected)
Red HatRed Hat Satellite 6.18 for RHEL 9
  • Default status: affected
  • 0:0.9.4-2.el9sat up to but excluding * (unaffected)
Red HatRed Hat Satellite 6.19 for RHEL 9
  • Default status: affected
  • 0:1.0.0-3.el9sat up to but excluding * (unaffected)
Red HatRed Hat Satellite 6.19 for RHEL 9
  • Default status: affected
  • 0:1.0.0-3.el9sat up to but excluding * (unaffected)

Timeline

  1. 7 Oct 2026 Reported to Red Hat.
  2. 12 Nov 2026 Made public.
  3. 12 Nov 2026 Published

Weakness

References