Skip to main content
VulnerabilityPublished

CVE-2026-55172: OSC ondemand · DEPRECATED: Insecure Temporary File

Affects OSC ondemandSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.4 Medium : upgrade to 4.2.3 or 4.1.6 when convenient.

Data as of 18 Nov 2026, 21:34 UTC

CVSS 4.0 base score
5.4Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 4.05.4
Patch
Available – fixed in 4.2.3, 4.1.6
CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 18 Nov 2026.

What to do

Upgrade ondemand and osc/ondemand to 4.2.3 or 4.1.6.

Affected software

ProductAffectedFixed in
OSCondemandAffected
  • >=4.2.0 <4.2.3
Fixed in
  • 4.2.3
OSCondemandAffected
  • <4.1.6
Fixed in
  • 4.1.6
GitHubosc/ondemandpkg:github/osc/ondemandOther threatsAffected
  • <4.1.6
  • >=4.2.0 <4.2.3
Fixed in
  • 4.1.6
  • 4.2.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Open OnDemand to version 4.1.6 or later, or 4.2.3 or later, where this vulnerability has been fixed. These versions enforce proper user directory ownership and permissions for session storage, mitigating the risk of session hijacking and code execution. No additional mitigation steps are indicated by the vendor advisory.

Description

Open OnDemand versions prior to 4.1.6 and between 4.2.0 and before 4.2.3 have an insecure temporary file handling vulnerability in the session storage mechanism. The dashboard sessions are stored in a predictable directory without proper ownership and permission validation, allowing a local attacker to pre-create directories, read session identifiers and CSRF tokens, or stage session identifiers. This can lead to file modification or code execution with the victim's privileges. The issue is fixed in versions 4.1.6 and 4.2.3.

References

Community reviews

Loading reviews…