CVE
OnDemand session forgery via predictable OIDC passphrase
Open OnDemand before 4.1.6 and 4.2.0 through 4.2.2 defaults its OIDC passphrase when none is set, and ood-ansible deployments are also affected. Fixed in 4.1.6 and 4.2.3; osc.open_ondemand 4.2.1 is fixed.
- Exploited
- No known exploitation
- Fix
- Fixed in ondemand 4.1.6, 4.2.3 · osc.open_ondemand 4.2.1
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: ondemand 4.1.6, 4.2.3 · osc.open_ondemand 4.2.1.
Summary
Open OnDemand and the ood-ansible role use a predictable default OIDC encryption passphrase, and a passphrase administrators set may not take effect. A remote attacker who can reach the portal without logging in can derive the key and forge a session cookie to act as another user in client-cookie deployments.
Original description
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.
Who should check
Teams running Open OnDemand 4.x portals with OIDC auth, and teams deploying them through the ood-ansible or osc.open_ondemand role
Not fixed by: Setting ood_oidc_crypto_passphrase has no effect on unpatched ood-ansible.
“Open OnDemand 4.x, EL9”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.1/10CVSS 9.1
- No patch0/5No signal
What would change the score
- Would score about 71 if added to CISA KEV
- Would score about 66 if CISA's SSVC rates exploitation active
- Would score about 31 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: ondemand 4.1.6, 4.2.3 · osc.open_ondemand 4.2.1.
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-55171 (Open OnDemand: Predictable OIDCCryptoPassphrase default + ood-ansible variable mismatch enables session forgery), 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-55171 (entry last updated 2026-11-18):
Affected:
- OSC ondemand: fixed in 4.1.6; from 4.2.0, fixed in 4.2.3
- ood-ansible osc.open_ondemand: fixed in 4.2.1
Fixed versions: 4.1.6, 4.2.3, 4.2.1.
Conditions (all must be true for the bug to be hit):
- Open OnDemand portal generator defaults OIDCCryptoPassphrase to SHA1(servername) when no passphrase is configured (source: https://github.com/OSC/ondemand/security/advisories/GHSA-3wm4-r2jj-43pp)
- Deployed via ood-ansible, whose template checks a different variable than the documented passphrase setting (source: https://github.com/OSC/ondemand/security/advisories/GHSA-3wm4-r2jj-43pp)
- OIDCSessionType set to client-cookie for the full session forgery impact (server-cache is the mod_auth_openidc default) (source: https://github.com/OSC/ondemand/security/advisories/GHSA-3wm4-r2jj-43pp)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-55171 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-55171 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://github.com/OSC/ondemand/security/advisories/GHSA-3wm4-r2jj-43pp
- https://github.com/OSC/ondemand/pull/5559
- https://github.com/OSC/ood-ansible/pull/303
- https://github.com/OSC/ondemand/commit/26ff4b4f21a4f5a2ab8eeafe495aee883f763263
- https://github.com/OSC/ondemand/commit/2cf5c2871622acf3a84c1269481c4c0ca6df543c
- https://github.com/OSC/ood-ansible/commit/29dfbc7993cf48ae7553551c13bdf1406fa218ad
- https://github.com/OSC/ondemand/releases/tag/v4.1.6
- https://github.com/OSC/ondemand/releases/tag/v4.2.3
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-55171
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-55171"}.Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
- OSC ondemand
fixed in 4.1.6; From 4.2.0 · fixed in 4.2.3
- ood-ansible osc.open_ondemand
fixed in 4.2.1
Evidence 11
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · OSC/ondemand · Advisory GHSA-3wm4-r2jj-43pp |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-55171 |
| Record | NVD · CVE-2026-55171 |
| Other links 8 | |
| Repository | GitHub · OSC/ondemand · Pull request #5559 |
| Repository | GitHub · OSC/ood-ansible · Pull request #303 |
| Repository | GitHub · OSC/ondemand · Commit 26ff4b4f |
| Repository | GitHub · OSC/ondemand · Commit 2cf5c287 |
| Repository | GitHub · OSC/ood-ansible · Commit 29dfbc79 |
| Repository | GitHub · OSC/ondemand · Release v4.1.6 |
| Repository | GitHub · OSC/ondemand · Release v4.2.3 |
| Repository | GitHub · OSC/ood-ansible · Release v4.2.1 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-55171
Is CVE-2026-55171 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?
When no OIDCCryptoPassphrase is configured, the Open OnDemand portal generator sets it to the SHA1 hash of the server name, which is predictable. In client-cookie session deployments, someone who knows that value can forge a session cookie for any user and bypass authentication. In server-cache deployments, the impact is tampering with OIDC state and nonce cookies, which is less severe.Source: github.com
Which versions are affected by CVE-2026-55171?
ondemand: before 4.1.6; from 4.2.0 before 4.2.3. osc.open_ondemand: before 4.2.1.Source: cve.now feed data
Am I affected, and how do I check?
Affected are ondemand versions before 4.1.6 and 4.2.0 through 4.2.2, plus osc.open_ondemand versions before 4.2.1 deployed through ood-ansible, whose template checks a different variable than the documented passphrase setting. Full session forgery needs OIDCSessionType set to client-cookie, while server-cache is the mod_auth_openidc default. To check, look at the installed ondemand package version and the OIDCSessionType value in the Apache OIDC configuration.Source: github.com
How do I fix CVE-2026-55171?
Upgrade ondemand to 4.1.6 or 4.2.3, depending on the release line in use. If deployed with ood-ansible, upgrade osc.open_ondemand to 4.2.1.Source: github.com