Skip to main content
Menu
CVEs

CVE

OnDemand noVNC session credentials leaked to access logs

CVE-2026-55169Published Updated Summary written by a model

8.4HighCNA
Exploited
No known exploitation
Fix
Fixed in 4.1.6, 4.2.3
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. A noVNC desktop session is launched through Open OnDemand. Per-user PUN access log directories are not locked down, so other users can read them.

Summary

Open OnDemand, an open-source HPC portal, can leak noVNC session passwords into per-user access logs. A local user with low privileges who can read insufficiently protected log directories could recover a launch URL and replay it to take over a running remote desktop, gaining the access of that desktop's owner.

Original description

Open OnDemand is an open-source high-performance computing portal. Prior to 4.1.6 and 4.2.3, the Open OnDemand dashboard includes noVNC passwords in query parameters generated by apps/dashboard/app/helpers/batch_connect/sessions_helper.rb and apps/dashboard/app/views/batch_connect/sessions/connections/_novnc.html.erb. The server records those query strings in per-user PUN access logs, and insufficiently protected log directories can allow another local user to recover and replay a launch URL. Replaying the credential grants access to the running remote desktop and can result in horizontal or vertical privilege escalation according to the privileges of the desktop owner. This issue is fixed in versions 4.1.6 and 4.2.3.

Who should check

Sites running Open OnDemand dashboard before 4.1.6 or 4.2.3 that offer noVNC desktop sessions and have per-user PUN access logs.

“Server side plaintext authentication logs when NoVNC session are launched”

github.com

cve.now Index

13Pcve.now Index 13 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure5/25Specific setups only
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity8.4/10CVSS 8.4
  • No patch0/5No signal

What would change the score

  • Would score about 63 if added to CISA KEV
  • Would score about 58 if CISA's SSVC rates exploitation active
  • Would score about 23 if CISA's SSVC rates it automatable

What to do

  • Check whether your setup matches what the bug needs.

    A noVNC desktop session is launched through Open OnDemand. Per-user PUN access log directories are not locked down, so other users can read them.
  • Upgrade to a fixed version: 4.1.6, 4.2.3.

  • Workaround: Restrict permissions on the per-user log directories to 0700 as a short-term measure.

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-55169 (Open OnDemand: Plaintext user authentication stored in access.logs for NoVNC access), 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-55169 (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.
Conditions (all must be true for the bug to be hit):
- A noVNC desktop session is launched through Open OnDemand. (source: https://github.com/OSC/ondemand/security/advisories/GHSA-pj66-qf5q-g7g5)
- Per-user PUN access log directories are not locked down, so other users can read them. (source: https://github.com/OSC/ondemand/security/advisories/GHSA-pj66-qf5q-g7g5)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: local access, low-privilege login, no user action.
Workaround: Restrict permissions on the per-user log directories to 0700 as a short-term measure. (source: https://github.com/OSC/ondemand/security/advisories/GHSA-pj66-qf5q-g7g5)
CISA KEV: CVE-2026-55169 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-55169 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-pj66-qf5q-g7g5
- https://github.com/OSC/ondemand/pull/5562
- https://github.com/OSC/ondemand/commit/3ade99c529d8244a1411a58da3628631fd06c5f1
- https://github.com/OSC/ondemand/commit/efdc06a8deed9be010e04c6ab4e9bcc55e3b8474
- 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-55169
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-55169"}.

Timeline

  1. CVE published
  2. 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

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · OSC/ondemand · Advisory GHSA-pj66-qf5q-g7g5
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-55169
RecordNVD · CVE-2026-55169
Other links 5
RepositoryGitHub · OSC/ondemand · Pull request #5562
RepositoryGitHub · OSC/ondemand · Commit 3ade99c5
RepositoryGitHub · OSC/ondemand · Commit efdc06a8
RepositoryGitHub · OSC/ondemand · Release v4.1.6
RepositoryGitHub · 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-55169

Is CVE-2026-55169 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?

Open OnDemand writes the plaintext login credentials of a noVNC desktop launch into its access logs. Anyone who reads a logged launch URL can replay it to reach another user's running remote desktop, which can mean moving sideways to a peer's session or upward to a more privileged user's desktop.Source: github.com

Which versions are affected by CVE-2026-55169?

ondemand: before 4.1.6; from 4.2.0 before 4.2.3.Source: cve.now feed data

Am I affected, and how do I check?

Versions from 4.2.0 up to but not including 4.2.3, and versions before 4.1.6, are affected. The per-user PUN access log directories must also be readable by other users, which is the default setup. To check, run the Open OnDemand version command on the server and compare it with 4.1.6 and 4.2.3.Source: github.com

How do I fix CVE-2026-55169?

Upgrade to 4.1.6 if you are on the 4.1 line, or to 4.2.3 if you are on the 4.2 line. The advisory names no patch identifiers. Until upgrading, restrict the per-user log directories to mode 0700.Source: github.com

More CVEs