dbcve.org
OfbizApplication · Apache

CVE-2026-29220

MEDIUM · 6.5 CVSS v3.1 Published 2026-05-19
Fix available
A fix is available. Upgrade to 24.09.06 or later.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Apache OFBiz. This issue affects Apache OFBiz: before 24.09.06. Users are recommended to upgrade to version 24.09.06, which fixes the issue.

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 · moderate confidence

A path traversal vulnerability in Apache OFBiz allows attackers to escape restricted directories and access sensitive files outside the intended scope by manipulating file paths in HTTP requests.

MitigationUpgrade Apache OFBiz to version 24.09.06 or later to obtain the patched version that properly validates and sanitizes file path inputs.

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
OfbizApplication
Affected:< 24.09.06

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 Apache OFBiz installation
    Locate the OFBiz installation directory and check the version. Common locations include /opt/ofbiz, /home/ofbiz, or the directory where the OFBiz war files are deployed. Look for a VERSION or build file, or check the manifest in the deployed war files.
    Affected if The installed version is any version prior to 24.09.06 (e.g., 24.03.x, 18.12.x, earlier releases).
  2. Determine if OFBiz web services are exposed
    Check if the OFBiz web application is accessible over HTTP/HTTPS. Look at your web server configuration (e.g., Apache HTTP, Nginx, or embedded container) to identify if port 8080 or 8443 (or configured ports) are listening and accessible.
    Affected if The OFBiz web interface is exposed to network access without proper authentication barriers.
  3. Verify the webxml configuration for exposed servlets
    Examine the web.xml deployment descriptor in the OFBiz web application (typically in webapp/ofbiz/WEB-INF/web.xml) to identify which servlets and endpoints are mapped and accessible via HTTP.
    Affected if The web.xml shows exposed endpoints that handle file requests or allow path parameters without additional access controls.
  4. Review access control configuration
    Check the OFBiz security configuration files (such as security.xml or controller.xml in the webapp configuration) to determine if the file-serving components are protected by authentication and authorization constraints.
    Affected if The file-serving or content management components lack proper access control constraints or are configured to allow unauthenticated access.

Your environment is affected if Apache OFBiz version is below 24.09.06 and the web interface or specific file-serving endpoints are accessible to users who can send crafted path traversal requests.

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
Upgrade available Upgrade to 24.09.06 or later
Fixed in 24.09.06
Interim mitigation

Upgrade Apache OFBiz to version 24.09.06 or later to obtain the patched version that properly validates and sanitizes file path inputs.

Recommended fix High confidence

24.09.06

  1. 1. Back up your existing Apache OFBiz installation and database before upgrading.
  2. 2. Download Apache OFBiz version 24.09.06 from the official Apache repository (https://ofbiz.apache.org/download.html).
  3. 3. Stop the currently running OFBiz service.
  4. 4. Replace the existing OFBiz installation files with the new version 24.09.06.
  5. 5. Reapply any custom configurations, themes, or extensions that were used in the previous installation.
  6. 6. Start the OFBiz service and verify it runs without errors.
  7. 7. Test critical functionality to ensure the upgrade was successful and the path traversal vulnerability is resolved.
Caveat Review the release notes for 24.09.06 to check for any breaking changes in functionality or configuration before deploying to production.

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

Fix this in Ofbiz Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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