Skip to main content
VulnerabilityPublished

CVE-2026-107152: An improper authentication vulnerability has been found in the task console in the

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-107152· High 7.1

Not known to be exploited · CVSS 7.1 High.

Data as of 12 Nov 2026, 22:32 UTC

CVSS 3.1 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (redhat)CVSS 3.17.1
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 12 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Red Hat Satellite 6rubygem-smart_proxy_dynflowAffected–Fixed in–

AI-suggested

Red Hat currently does not have a practical temporary workaround that fully mitigates this issue. Customers are advised to apply the relevant security updates when they become available. No other mitigations meeting Red Hat's standards for usability and stability are known at this time.

Description

CVE-2026-107152 is an improper authentication vulnerability in the task console of the smart_proxy_dynflow package. The console accepts any client certificate signed by the capsule's certificate authority without verifying the trusted server list. An attacker with a valid certificate can read sensitive job details, including passwords, and cancel running tasks. Red Hat rates this vulnerability as having a high confidentiality impact and low integrity impact. No practical workaround is currently available, and users are advised to apply security updates once released.

References

Community reviews

Loading reviews…