CVE-2026-55171

CRITICALPre-NVD 9.19.1
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (34th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source

Also known asEUVD-2026-129304 (ENISA EUVD)Source: ENISA EUVD

9.1EG
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: 9.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Open OnDemand is an open-source high-performance computing portal. Prior to Open OnDemand 4.1.6 and 4.2.3, and prior to ood-ansible 4.2.1, the portal generator defaults OIDCCryptoPassphrase to SHA1(servername), and the templates/ood_portal.yml.j2 role checks a different variable from the documented passphrase setting. Administrators who set ood_oidc_crypto_passphrase can therefore believe a strong secret is configured while the deployment continues to use an attacker-derivable value. In OIDCSessionType client-cookie deployments, an unauthenticated remote attacker can derive the encryption key and forge a mod_auth_openidc_session cookie for another user, while server-cache deployments permit lower-impact tampering with protected OIDC state and nonce cookies. This issue is fixed in Open OnDemand versions 4.1.6 and 4.2.3 and ood-ansible version 4.2.1.

CVSS
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
41
EG Risk 41/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)
Severity91% × 45%
Impact severity (EG Severity): CVSS 9.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CVSS v4.0 confidentiality and integrity impact both High). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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
34th
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 (9.1): severity, escalated by confirmed exploitation. This CVE's 9.1 is its impact severity (EG Severity), not escalated.

EG Severity
9.1 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-21). 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, and whom BOD 26-04 binds: 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 (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CVSS v4.0 confidentiality and integrity impact both High). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CVSS v4.0 confidentiality and integrity impact both High). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” 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

November 18, 2026

Last Modified

November 18, 2026

Advisory Details (9)

Auto-updated Nov 18, 2026
Patch available. Sources: github, github_commit, github_pr, github_release.
GitHub release Patch Available

v4.2.1

Patch available: OSC/ood-ansible v4.2.1

https://github.com/OSC/ood-ansible/releases/tag/v4.2.1
GitHub pull request Patch Available

correct this variable name

Patch available: OSC/ood-ansible v4.2.1 (PR #303 merged 2026-06-09)

https://github.com/OSC/ood-ansible/pull/303
GitHub commit Patch Available

commit 29dfbc7993cf (OSC/ood-ansible)

Patch available: OSC/ood-ansible v4.2.1 (contains commit 29dfbc7993cf)

https://github.com/OSC/ood-ansible/commit/29dfbc7993cf48ae7553551c13bdf1406fa218ad
GitHub advisoryMentions a patch (unverified)

Predictable OIDCCryptoPassphrase default + ood-ansible variable mismatch enables session forgery · Advisory · OSC/ondemand · GitHub

Affected: 4.2.3 and 4.1.6.

https://github.com/OSC/ondemand/security/advisories/GHSA-3wm4-r2jj-43pp
GitHub release Patch Available

v4.2.3

Patch available: OSC/ondemand v4.2.3

https://github.com/OSC/ondemand/releases/tag/v4.2.3
GitHub release Patch Available

v4.1.6

Patch available: OSC/ondemand v4.1.6

https://github.com/OSC/ondemand/releases/tag/v4.1.6
GitHub pull request

remove this default and enforce it be set

Fix merged in OSC/ondemand PR #5559 on 2026-06-23 — awaiting tagged release

https://github.com/OSC/ondemand/pull/5559
GitHub commit Patch Available

commit 2cf5c2871622 (OSC/ondemand)

Patch available: OSC/ondemand v4.1.6 (contains commit 2cf5c2871622)

https://github.com/OSC/ondemand/commit/2cf5c2871622acf3a84c1269481c4c0ca6df543c
GitHub commit Patch Available

commit 26ff4b4f21a4 (OSC/ondemand)

Patch available: OSC/ondemand v4.2.3 (contains commit 26ff4b4f21a4)

https://github.com/OSC/ondemand/commit/26ff4b4f21a4f5a2ab8eeafe495aee883f763263

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 5× in last 7d / 5× 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 its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-22 01:15 UTCEchelonGraph re-scored
  2. 2026-11-21 16:40 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  3. 2026-11-21 00:15 UTCEchelonGraph re-scored
  4. 2026-11-20 16:37 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  5. 2026-11-19 23:17 UTCEchelonGraph re-scored
  6. 2026-11-19 16:34 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  7. 2026-11-18 22:03 UTCENISA EUVD ID recordedEUVD-2026-129304 · Source: ENISA EUVD
  8. 2026-11-18 21:28 UTCEchelonGraph re-scored
  9. 2026-11-18 21:13 UTCEchelonGraph re-scoredFirst assessed: 9.1 CRITICAL
  10. 2026-11-18 21:12 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-55171?
CVE-2026-55171 is a critical-severity vulnerability; its CVE record was published on November 18, 2026. Open OnDemand is an open-source high-performance computing portal. Prior to Open OnDemand 4.1.6 and 4.2.3, and prior to ood-ansible 4.2.1, the portal generator defaults OIDCCryptoPassphrase to SHA1(servername), and the templates/ood_portal.yml.j2 role checks a different variable from the documented…
When was the CVE record for CVE-2026-55171 published?
The CVE record for CVE-2026-55171 was published on November 18, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 18, 2026; the record at its source may have been updated since.
Is CVE-2026-55171 actively exploited?
CVE-2026-55171 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (34th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-55171?
CVE-2026-55171 has a CVSS base score of 9.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-55171?
A fix for CVE-2026-55171 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-55171?

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