CVE
OnDemand session hijacking via unowned session store directory
- Exploited
- No known exploitation
- Fix
- Fixed in 4.1.6, 4.2.3
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 4.1.6, 4.2.3.
Summary
Open OnDemand stores dashboard session data in a predictable directory without checking who owns it, so a local user with low privileges can pre-create another user's directory. From there, they can read the victim's session identifier and CSRF token after login, or plant a chosen session identifier, and the attack requires the victim to take an action. Attacker-controlled cache data may also be deserialized in the victim's context, which could allow file modification or code execution with the victim's privileges.
Original description
Open OnDemand is an open-source high-performance computing portal. Prior to 4.1.6 and 4.2.3, apps/dashboard/config/initializers/session_store.rb stores dashboard sessions by default in a predictable /var/tmp/<username> directory, or in another location configured by an administrator, but omits PUN user directory ownership and mode 0700 validation. A local attacker can pre-create another user's directory, read the victim's session identifier and CSRF token after login, or stage a predetermined session identifier. ActiveSupport file-store deserialization of attacker-controlled cache data may also occur in the victim's context, enabling file modification or code execution with the victim's privileges. This issue is fixed in versions 4.1.6 and 4.2.3.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity5.4/10CVSS 5.4
- No patch0/5No signal
What would change the score
- Would score about 60 if added to CISA KEV
- Would score about 55 if CISA's SSVC rates exploitation active
- Would score about 27 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 4.1.6, 4.2.3.
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-55172 (Open OnDemand: Session_store directory ownership), 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-55172 (entry last updated 2026-11-18):
Affected:
- OSC ondemand: fixed in 4.1.6; from 4.2.0, fixed in 4.2.3
Fixed versions: 4.1.6, 4.2.3.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-55172 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-55172 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-wqv4-4vj3-rgh5
- https://github.com/OSC/ondemand/pull/5558
- https://github.com/OSC/ondemand/commit/1b0c550921edeb40beaf6c7dcbe2b0fc3a40ec3c
- https://github.com/OSC/ondemand/commit/79265f593aac10ef797cd3293ec3c8b7a2572339
- 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-55172
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-55172"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- OSC ondemand
fixed in 4.1.6; From 4.2.0 · fixed in 4.2.3
Evidence 8
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · OSC/ondemand · Advisory GHSA-wqv4-4vj3-rgh5 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-55172 |
| Record | NVD · CVE-2026-55172 |
| Other links 5 | |
| Repository | GitHub · OSC/ondemand · Pull request #5558 |
| Repository | GitHub · OSC/ondemand · Commit 1b0c5509 |
| Repository | GitHub · OSC/ondemand · Commit 79265f59 |
| Repository | GitHub · OSC/ondemand · Release v4.1.6 |
| Repository | GitHub · OSC/ondemand · Release v4.2.3 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-55172
Is CVE-2026-55172 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
Which versions are affected by CVE-2026-55172?
ondemand: before 4.1.6; from 4.2.0 before 4.2.3.Source: cve.now feed data
How do I fix CVE-2026-55172?
Upgrade to a fixed version: 4.1.6, 4.2.3.Source: cve.now feed data