dbcve.org
OozieApplication · Apache

CVE-2025-26796

MEDIUM · 5.4 CVSS v3.1 Published 2025-03-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
** UNSUPPORTED WHEN ASSIGNED ** Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Apache Oozie. This issue affects Apache Oozie: all versions. As this project is retired, we do not plan to release a version that fixes this issue. Users are recommended to find an alternative or restrict access to the instance to trusted users. NOTE: This vulnerability only affects products that are no longer supported by the maintainer.

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

Apache Oozie contains a Cross-site Scripting (XSS) vulnerability in its web interface where user-supplied input is not properly neutralized before being rendered in generated web pages. This allows authenticated attackers to inject malicious JavaScript code that executes in the browsers of other users viewing the affected pages.

MitigationSince Apache Oozie is retired with no official fix, organizations should either migrate to a supported alternative workflow scheduler or implement strict access controls (network segmentation, strong authentication) to limit exposure to trusted users only.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
OozieApplication
Affected:all versions

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

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 if Apache Oozie is installed
    Search for Oozie processes or services running on the system. Check common process names like 'oozie' or look for the Oozie installation directory. On Linux, you can use commands like 'ps aux | grep -i oozie' or 'systemctl list-units | grep -i oozie'. Check for the Oozie WAR file or installation in directories like /usr/lib/oozie or /opt/oozie.
    Affected if Apache Oozie process or service is found running on the system
  2. Locate the Oozie web interface port
    Examine the Oozie configuration file (oozie-site.xml) for the 'oozie.http.port' property. Default port is 11000. Also check for 'oozie.https.port' if SSL is enabled. The web UI is typically accessible at http://hostname:11000/oozie/.
    Affected if The web interface port is configured and accessible on the network
  3. Verify web interface accessibility
    Attempt to access the Oozie web UI using curl or a browser: curl -I http://localhost:11000/oozie/ (or the configured port). Check if the HTTP response returns a 200 status code, indicating the UI is reachable. Check network binding to determine if it listens on all interfaces (0.0.0.0) or localhost only.
    Affected if The Oozie web interface returns an HTTP 200 response and is reachable over the network
  4. Confirm authentication is required
    Review the Oozie configuration (oozie-site.xml) for security settings. Check if 'oozie.authentication.type' is set to a valid authentication mechanism (like kerberos, simple, or token). Attempt an unauthenticated request to see if the UI is accessible without credentials.
    Affected if The web interface can be accessed without providing valid credentials, meaning any network attacker could potentially inject XSS
  5. Identify user access to the web interface
    Determine which users have network access to the Oozie web UI. Review firewall rules, network segmentation, and ACLs governing who can reach the Oozie host and port. Check if the interface is exposed to untrusted networks or the internet.
    Affected if Users other than trusted administrators can reach the Oozie web interface

If Apache Oozie is running with its web interface accessible to users beyond trusted administrators, the environment is affected by this XSS vulnerability since all Oozie versions are impacted.

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

Since Apache Oozie is retired with no official fix, organizations should either migrate to a supported alternative workflow scheduler or implement strict access controls (network segmentation, strong authentication) to limit exposure to trusted users only.

Recommended fix High confidence
  1. 1. Discontinue use of Apache Oozie as it is a retired, unsupported project.
  2. 2. Evaluate and migrate to a supported workflow orchestration system (e.g., Apache Airflow, Apache NiFi, or cloud-native alternatives).
  3. 3. If migration is not immediately possible, restrict network access to the Oozie instance to trusted users only using firewall rules or network segmentation.
  4. 4. Implement additional web application firewall (WAF) rules to detect and block XSS attack patterns targeting the Oozie interface.

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

Fix this in Oozie Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-26796 — 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-2025-26796 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