CVE
Red Hat Satellite authentication bypass in dynflow console
- Exploited
- No known exploitation
- Fix
- See vendor advisory
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Dynflow web console is enabled with console_auth true, which is the default
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.26% · 18th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 30/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Red Hat Satellite 6 with the rubygem-smart_proxy_dynflow package has a flaw in its task console that accepts any client certificate signed by the capsule's certificate authority, without checking the list of servers the capsule trusts. A low-privileged attacker on the network who already holds such a certificate can open the console to read job details, including any passwords given to a job, and can cancel running tasks.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original 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.
Who should check
Teams running Red Hat Satellite 6.16 on RHEL 8 or RHEL 9, and Satellite 6.17 on RHEL 9, with the Dynflow console (smart_proxy_dynflow) in use
Read the source excerpt
“An update is now available for Red Hat Satellite 6.16 for RHEL 8 and RHEL 9.”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach10/20Shipped in major Linux distributions
- Severity7.1/10CVSS 7.1
- No patch5/5No fixed version listed; see vendor advisory
What would change the score
- Would score about 80 if added to CISA KEV
- Would score about 75 if CISA's SSVC rates exploitation active
- Would score about 37 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Dynflow web console is enabled with console_auth true, which is the defaultWorkaround: The checked facts do not include a workaround. The only setup condition they give is console_auth set to true, so Red Hat's guidance on that setting is the place to look while no fix is available.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-107152 (Rubygem-smart_proxy_dynflow: dynflow console authorizes any client certificate the capsule ca signed), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-107152 (entry last updated 2026-11-12):
Affected:
- Red Hat Red Hat Satellite 6.16 for RHEL 8: version range not reported
- Red Hat Red Hat Satellite 6.16 for RHEL 9: version range not reported
- Red Hat Red Hat Satellite 6.17 for RHEL 9: version range not reported
- Red Hat Red Hat Satellite 6.18 for RHEL 9: version range not reported
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Dynflow web console is enabled with console_auth true, which is the default (source: https://bugzilla.redhat.com/show_bug.cgi?id=2547374)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-107152 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-107152 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://access.redhat.com/errata/RHSA-2026:99949
- https://access.redhat.com/errata/RHSA-2026:99950
- https://access.redhat.com/errata/RHSA-2026:99952
- https://bugzilla.redhat.com/show_bug.cgi?id=2547374
- https://access.redhat.com/security/cve/CVE-2026-107152
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-107152
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-107152"}.Timeline
- CVE published
- First seen by cve.now
- Record last updated
Affected versions
- rubygem-smart_proxy_dynflow
Version range not reported
- rubygem-smart_proxy_dynflow
Version range not reported
- rubygem-smart_proxy_dynflow
Version range not reported
- rubygem-smart_proxy_dynflow
Version range not reported
Evidence 7
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Write-ups · 1
Establishes: Technical detail and context.
- Report
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-107152
Is CVE-2026-107152 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The Dynflow web console authorizes any client certificate that the capsule CA has signed, so a certificate does not need to be specifically approved to get access.Source: bugzilla.redhat.com
Am I affected, and how do I check?
Red Hat Satellite 6.16 for RHEL 8, Satellite 6.16 for RHEL 9, Satellite 6.17 for RHEL 9, and Satellite 6.18 for RHEL 9 are listed. The issue applies when the Dynflow web console is enabled with console_auth set to true, which is the default; check that setting in the smart_proxy_dynflow configuration.Source: bugzilla.redhat.com
How do I fix CVE-2026-107152?
The checked facts do not name a fixed version or patch ids, so no upgrade target can be confirmed from them. Check Red Hat's advisory for the fixed packages for your Satellite version.Source: bugzilla.redhat.com
What if there's no patch?
The checked facts do not include a workaround. The only setup condition they give is console_auth set to true, so Red Hat's guidance on that setting is the place to look while no fix is available.Source: bugzilla.redhat.com