CVE-2026-103314

HIGHPre-NVD 7.47.4
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.4 from GitHub Security Advisory (severity: HIGH) published 2026-10-19. The CNA's CVSS baseline 7.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: the CNA's CVSS, EPSS, GitHub Security Advisory

Also known asEUVD-2026-104252 (ENISA EUVD) · GHSA-xxr5-h8gc-q63j (GitHub Security Advisories)Source: ENISA EUVD

7.4EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.4Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Fixed versions, as the CVE record's CNA (Red Hat, Inc.) states them in the record's workaround: "The highest-value action is to enforce replay tracking on the Central SAML Assertion Consumer Service endpoint to record and reject previously consumed assertion and response identifiers: upgrade to RHACS 4.11.6 (or the…"

A flaw was found in Red Hat Advanced Cluster Security for Kubernetes (RHACS). The Central SAML authentication ACS endpoint does not retain used SAML assertion or response identifiers to prevent replay. An attacker who obtains a valid, unexpired signed SAML response can submit it multiple times and receive distinct Central authentication tokens for the mapped identity.

CVSS v3
7.4
EG Score
7.4HIGHhigh confidence
EG Risk
33
EG Risk 33/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity74% × 45%
Impact severity (EG Severity): CVSS 7.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
33rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.4): severity, escalated by confirmed exploitation. This CVE's 7.4 is its impact severity (EG Severity), not escalated.

EG Severity
7.4 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 19, 2026

Last Modified

October 20, 2026

Advisory Details (2)

Auto-updated Oct 19, 2026
Patch available. Sources: redhat.
Red Hat

2543879 – (CVE-2026-103314) CVE-2026-103314 stackrox: stackrox: SAML response replay allows multiple Central authentication tokens

https://bugzilla.redhat.com/show_bug.cgi?id=2543879
Red HatMentions a patch (unverified)

CVE-2026-103314 - Red Hat Customer Portal

Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a

https://access.redhat.com/security/cve/CVE-2026-103314

Vendor Advisories for CVE-2026-103314(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 22× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  2. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  3. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  4. 2026-10-25 14:56 UTCEG score recompute
  5. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  6. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  7. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  8. 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  9. 2026-10-20 21:42 UTCEG score recompute
  10. 2026-10-20 21:42 UTCGHSA enrichmentGHSA-xxr5-h8gc-q63j · GitHub severity HIGH · GitHub CVSS 7.4
  11. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  12. 2026-10-20 13:26 UTCEG score recompute
  13. 2026-10-20 13:26 UTCGHSA enrichmentGHSA-xxr5-h8gc-q63j · GitHub severity HIGH · GitHub CVSS 7.4
  14. 2026-10-20 12:57 UTCEG score recompute
  15. 2026-10-20 12:57 UTCGHSA enrichmentGHSA-xxr5-h8gc-q63j · GitHub severity HIGH · GitHub CVSS 7.4
  16. 2026-10-19 21:09 UTCGHSA enrichmentGHSA-xxr5-h8gc-q63j · GitHub severity HIGH · GitHub CVSS 7.4
  17. 2026-10-19 16:31 UTCEG score recompute
  18. 2026-10-19 16:30 UTCGHSA enrichmentGHSA-xxr5-h8gc-q63j · GitHub severity HIGH · GitHub CVSS 7.4
  19. 2026-10-19 15:28 UTCEG score recompute
  20. 2026-10-19 13:26 UTCEG score recompute
  21. 2026-10-19 12:39 UTCEG score recomputeFirst assessed: 7.4 HIGH
  22. 2026-10-19 12:38 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-103314?
CVE-2026-103314 is a high-severity vulnerability; its CVE record was published on October 19, 2026. A flaw was found in Red Hat Advanced Cluster Security for Kubernetes (RHACS). The Central SAML authentication ACS endpoint does not retain used SAML assertion or response identifiers to prevent replay. An attacker who obtains a valid, unexpired signed SAML response can submit it multiple times and…
When was CVE-2026-103314 made public?
CVE-2026-103314 was made public on October 19, 2026: that is the date its CVE record's CNA, Red Hat, Inc., gives for when the vulnerability was made public. The CVE record itself was published on October 19, 2026. EchelonGraph's copy of the record carries a last-modified date of October 20, 2026; the record at its source may have been updated since.
Is CVE-2026-103314 actively exploited?
CVE-2026-103314 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (33rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-103314?
CVE-2026-103314 has a CVSS base score of 7.4 (the CNA's own assessment, by redhat; NVD's own analysis pending).
How do I remediate CVE-2026-103314?
A fix for CVE-2026-103314 is available: update to the fixed version the vendor names in its advisory. Fixed versions, as the CVE record's CNA (Red Hat, Inc.) states them in the record's workaround: "The highest-value action is to enforce replay tracking on the Central SAML Assertion Consumer Service endpoint to record and reject previously consumed assertion and response identifiers: upgrade to RHACS 4.11.6 (or the…" The vendor advisories EchelonGraph has for CVE-2026-103314 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-103314

Explore →

Is Your Infrastructure Affected by CVE-2026-103314?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs