dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-44371

MEDIUM · 5.3 CVSS v4.0 Published 2026-05-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Open OnDemand is an open-source high-performance computing portal. Prior to 4.0.11, 4.1.5, and 4.2.2, specially crafted filenames can execute javascript in the file browser This vulnerability is fixed in 4.0.11, 4.1.5, and 4.2.2.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is a stored Cross-Site Scripting (XSS) vulnerability in Open OnDemand's file browser. Attackers can execute arbitrary JavaScript in victims' browsers by uploading or renaming files with specially crafted filenames containing malicious script content. When other users browse to view these files, the embedded JavaScript executes within their session context.

MitigationUpgrade to version 4.0.11, 4.1.5, or 4.2.2 (or later) to receive the fix. If immediate patching is not feasible, consider restricting or validating file upload/rename permissions in the file browser until the upgrade can be performed.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
P
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Open OnDemand installation and version
    Locate the Open OnDemand installation directory and check the version file (typically found in /opt/ood or the main OOD root directory). Common locations include /opt/ood/VERSION, /etc/ood.version, or check the package manager (rpm -q ondemand or gem list ondemand).
    Affected if The installed version is below 4.0.11, 4.1.5, or 4.2.2 (for example, any 4.0.x below 4.0.11, any 4.1.x below 4.1.5, or any 4.2.x below 4.2.2)
  2. Confirm the file browser module is enabled
    Inspect the Open OnDemand configuration file (ood_portal.yml or /etc/ood/config/ood.conf) to verify that the file browser app (typically named 'files' or 'ood-file-manager' in the nav_bar configuration) is listed in the enabled apps or nav_bar section.
    Affected if The file browser appears in the active navigation and is accessible to users
  3. Verify user access to file upload or rename capabilities
    Check the Open OnDemand authentication and authorization configuration to determine which users or groups have permission to use the file browser and upload or rename files. Review the /etc/ood/config/nginx_stage.yml or related authorization files.
    Affected if Regular users (non-admin) have file upload or rename permissions in the file browser

If the installed Open OnDemand version is below 4.0.11/4.1.5/4.2.2 AND the file browser is accessible to users with upload/rename permissions, the environment is vulnerable to stored XSS via malicious filenames.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to version 4.0.11, 4.1.5, or 4.2.2 (or later) to receive the fix. If immediate patching is not feasible, consider restricting or validating file upload/rename permissions in the file browser until the upgrade can be performed.

Recommended fix High confidence

4.0.11, 4.1.5, or 4.2.2 (depending on your current release branch)

  1. 1. Identify the current installed version of Open OnDemand by checking the package manager or application version
  2. 2. Determine which release branch you are on (e.g., 4.0.x, 4.1.x, or 4.2.x)
  3. 3. For 4.0.x branch: upgrade to version 4.0.11
  4. 4. For 4.1.x branch: upgrade to version 4.1.5
  5. 5. For 4.2.x branch: upgrade to version 4.2.2
  6. 6. Use the package manager or follow the official upgrade instructions for your deployment method (e.g., yum/apt for RPM/DEB packages, or source compilation)
  7. 7. After upgrade, verify the file browser functionality works correctly with various filename types
  8. 8. Test that the XSS vulnerability is remediated by attempting to use a specially crafted filename containing javascript code
Caveat Review release notes for your specific version upgrade path to check for any breaking changes or required configuration updates

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-44371 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-44371 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data