OfbizApplication · Apache

CVE-2026-35086

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 Control of Generation of Code ('Code Injection') vulnerability in email services of 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 code injection vulnerability exists in the email services component of Apache OFBiz, allowing attackers to inject malicious code through improperly controlled code generation. This affects versions prior to 24.09.06 and could enable arbitrary code execution within the context of the OFBiz application.

MitigationUpgrade Apache OFBiz to version 24.09.06 or later to resolve the vulnerability. Prior to upgrade, restrict access to email-related services and review configurations.

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 installed version
    Locate the OFBiz installation and check the version file or manifest (commonly found in build files, VERSION file, or about page). Compare the version number to 24.09.06 - any version below this is affected.
    Affected if The installed version is Apache OFBiz lower than 24.09.06
  2. Verify email services component is configured
    Inspect the OFBiz configuration for active email-related services. Check for emailWorker or email SMTP/IMAP configurations in the OFBiz XML configuration files or entity definitions.
    Affected if Email services component is enabled or configured in the OFBiz instance
  3. Check for exposed email-related endpoints
    Review the web controller configurations (controller.xml files) and webapp mappings to identify any publicly accessible endpoints related to email services (such as sendMail, emailTemplate, or similar).
    Affected if Email service endpoints are accessible without authentication or via exposed web services
  4. Inspect email template configurations
    Examine the email template storage and generation logic in the OFBiz codebase. Look for any user-controllable input that flows into template rendering or code generation pathways.
    Affected if Email templates or related code generation logic accepts unsanitized input that could be exploited for injection

The environment is affected if running Apache OFBiz version lower than 24.09.06 with the email services component enabled 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 resolve the vulnerability. Prior to upgrade, restrict access to email-related services and review configurations.

Recommended fix High confidence

24.09.06

  1. 1. Back up the current Apache OFBiz installation and database
  2. 2. Stop the running OFBiz service
  3. 3. Download Apache OFBiz version 24.09.06 from the official Apache download repository (https://ofbiz.apache.org/download.html)
  4. 4. Extract the new version to the target installation directory
  5. 5. Copy any custom configurations, data files, or plugins from the backup to the new installation
  6. 6. Start the OFBiz service
  7. 7. Verify the email service functionality is working correctly

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
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-35086 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