CVE-2026-19278: Red Hat Advanced Cluster Security 4 · Permissive Regular Expression
Affects Red Hat Advanced Cluster Security 4Source CVE Database V5
Not known to be exploited · CVSS 6.8 Medium.
Data as of 8 Nov 2026, 23:24 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 28% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 10 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 8 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Red HatRed Hat Advanced Cluster Security 4 | Affected– | Fixed in– |
AI-suggested
Administrators should review and update all Auth Machine-to-Machine (M2M) role mappings in StackRox/RHACS Central to ensure that the valueExpression regular expressions are properly anchored using start (^) and end ($) delimiters to enforce exact claim value matching. After updating the mappings, reload the configuration or restart the Central service to apply changes.
Description
CVE-2026-19278 is a medium severity vulnerability in Red Hat Advanced Cluster Security 4's StackRox/RHACS Central Auth Machine-to-Machine (M2M) token exchange. The flaw arises from the use of unanchored regular expressions in M2M role mappings, allowing an attacker with a valid OpenID Connect (OIDC) token whose claim value is a superstring of a configured pattern to gain unauthorized roles. This can lead to privilege escalation within the system. No official patch or fix has been explicitly stated yet. Administrators are advised to review and update their M2M role mappings to use properly anchored regular expressions to ensure exact matching and prevent unintended role assignments.