dbcve.org
OfbizApplication · Apache

CVE-2026-29226

HIGH · 7.3 CVSS v3.1 Published 2026-05-19
Fix available
A fix is available. Upgrade to 24.09.06 or later.
See remediation →
82/100
Remediation priority · High
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
Server-Side Request Forgery (SSRF) vulnerability in Apache OFBiz via Content component operations. 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 · high confidence

A Server-Side Request Forgery (SSRF) vulnerability exists in Apache OFBiz's Content component operations, allowing attackers to induce the server to make arbitrary requests to internal or external resources. This can lead to exposure of internal services, cloud metadata, or network infrastructure.

MitigationUpgrade Apache OFBiz to version 24.09.06 or later to remediate this vulnerability.

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
Low

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

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. Determine the installed Apache OFBiz version
    Check the OFBiz version file or framework/build ReleaseVersion file, typically found in the OFBiz installation root directory under 'framework/' or via the admin interface version display
    Affected if The installed version is any version prior to 24.09.06 (e.g., 24.03.x, 18.12.x, earlier releases)
  2. Identify if the Content component is deployed
    Check the OFBiz component registry or look for the 'content' component directory in the applications/ or framework/ folder of the OFBiz installation
    Affected if The Content component directory exists and is deployed in the OFBiz instance
  3. Verify the Content component is accessible via web
    Attempt to access or verify the Content management endpoints (e.g., /content/control/) are available and not disabled in the OFBiz web configuration
    Affected if The Content web controller and its operations are accessible without authentication restrictions or the vulnerability is reachable through permitted access paths

You are affected if your Apache OFBiz installation is version 24.09.05 or earlier and the Content component is deployed and accessible.

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 remediate this vulnerability.

Recommended fix High confidence

24.09.06

  1. 1. Back up your existing Apache OFBiz installation, database, and all configuration/customization files.
  2. 2. Stop the currently running OFBiz service.
  3. 3. Download Apache OFBiz version 24.09.06 from the official Apache download mirrors (https://ofbiz.apache.org/download.html).
  4. 4. Extract the new version to your installation directory, preserving your configuration files from the backup.
  5. 5. Review and migrate any custom configurations, plugins, or extensions to be compatible with the new version.
  6. 6. Start the OFBiz service and verify the application is running correctly.
  7. 7. Test the Content component functionality to confirm the SSRF vulnerability is resolved.
Caveat Minor version upgrade within 24.x - should have minimal breaking changes, but test custom components against new version before production deployment

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

Fix this in Ofbiz Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing16.0 h
  • Review / QA6.0 h
40.0 hours of engineering $6,840
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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