OfbizApplication · Apache
CVE-2026-46586
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 · uneditedImproper Control of Generation of Code ('Code Injection'), Improper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection') 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 · high confidenceThis is a code injection/eval injection vulnerability in Apache OFBiz that allows improper control of code generation through dynamically evaluated code paths. The vulnerability enables execution of malicious code through unsanitized user input being directly evaluated, potentially leading to remote code execution.
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
< 24.09.06CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Apache OFBiz versionCheck the version file in the OFBiz installation directory (typically at ./framework/base/src/main/java/org/apache/ofbiz/base/version/Version.java or in the startup logs), or run the OFBiz startup command and review the initial console output for the version numberAffected if The installed version is any version prior to 24.09.06 (e.g., 24.09.05, older releases)
-
Review custom scripts in the hot-deploy directoryExamine any custom scripts or plugins located in the hot-deploy directory for use of dynamic code evaluation functions (such as Groovy.evaluate(), ScriptEngine.eval(), or similar runtime execution methods) that process user-supplied inputAffected if Custom scripts in hot-deploy use eval-like functions with unsanitized user input
-
Check for Groovy or scripting engine usageSearch the OFBiz installation for files containing Groovy scripting or JavaScript engine calls (look for .groovy files or Java code using ScriptEngine) and verify whether request parameters are passed directly to these evaluation methodsAffected if The system uses Groovy or other scripting engines where request parameters flow into eval calls without sanitization
-
Inspect Form Widgets and Controller XML for dynamic expressionsReview the webapp controller configuration files (controller.xml) and form widget definitions for any 'field-type' entries or service definitions that use runtime expression evaluation with user-accessible fieldsAffected if Form widgets or controller actions execute dynamic expressions derived from user input
-
Check web.xml and security configurationExamine the WEB-INF/web.xml and security settings to determine if the scripting engine is enabled and whether external input sources can reach evaluation endpointsAffected if Scripting is enabled and user-accessible endpoints can reach eval-capable code paths
The environment is affected if running any Apache OFBiz version prior to 24.09.06 and the system has custom code or configurations that pass user input to dynamic code evaluation functions such as Groovy or other scripting engines.
Generated from the published advisory. Verify against your own configuration.
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 · scoped24.09.06
Upgrade Apache OFBiz to version 24.09.06 or later to remediate this code injection vulnerability.
24.09.06
- 1. Backup the existing OFBiz installation directory and database before proceeding with any upgrade
- 2. Download Apache OFBiz version 24.09.06 from the official Apache download site (https://ofbiz.apache.org/download.html)
- 3. Stop all running OFBiz services and processes
- 4. Replace the existing OFBiz installation with the new version 24.09.06 files, preserving custom configurations and data
- 5. Review and update any custom configurations, plugins, or component files as needed for compatibility
- 6. Start the OFBiz services
- 7. Verify the upgrade was successful by checking that the application functions normally and the vulnerability is resolved
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
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-46586 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-46586 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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