dbcve.org
OfbizApplication · Apache

CVE-2026-31986

CRITICAL · 9.1 CVSS v3.1 Published 2026-05-19
Fix available
A fix is available. Upgrade to 24.09.06 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Use of Hard-coded Cryptographic Key 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

Use of Hard-coded Cryptographic Key vulnerability in Apache OFBiz. The application contains a fixed encryption key embedded in its source code, which could allow attackers to decrypt sensitive data or communications if the key is discovered through code analysis or other means.

MitigationUpgrade to Apache OFBiz version 24.09.06 or later, which replaces the hard-coded cryptographic key with a properly managed key mechanism.

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
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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. Determine installed OFBiz version
    Locate the version identifier in your OFBiz installation (typically in a version file, build configuration, or the control panel under 'System' > 'Server History' or 'About'). Compare this version number to the affected range: any version below 24.09.06 is potentially vulnerable.
    Affected if Installed version is below 24.09.06
  2. Locate encryption key configuration
    Search the OFBiz configuration directory for files containing cryptographic keys. Common locations include: security configuration files,.properties or.xml files in the framework/security/config area, or any file containing 'encrypt', 'key', or 'crypt' in the filename.
    Affected if A static encryption key file exists and is loaded from the filesystem rather than being dynamically generated or externally managed
  3. Search source code for hard-coded key values
    Use grep or a similar text search tool to scan the OFBiz source code (Java files, configuration files, and Groovy scripts) for suspicious fixed string literals that may function as encryption keys. Look for string constants of approximately 16-32 characters that appear in cryptographic utility classes or security-related code.
    Affected if Fixed-length string literals serving as encryption keys are found directly embedded in source code rather than retrieved from external configuration or a key management system
  4. Verify key persistence across installations
    Deploy a fresh OFBiz instance from the same version and compare the encryption key present in that new installation with the key in your current environment. If they are identical, the key is hard-coded in the codebase.
    Affected if The same encryption key value appears in multiple independent installations of the same OFBiz version, confirming it is hard-coded rather than unique per deployment

Your environment is affected if you are running Apache OFBiz version below 24.09.06 AND a fixed encryption key is embedded in the source code rather than being dynamically managed or stored externally.

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 to Apache OFBiz version 24.09.06 or later, which replaces the hard-coded cryptographic key with a properly managed key mechanism.

Recommended fix High confidence

24.09.06

  1. 1. Backup your current Apache OFBiz installation and database.
  2. 2. Download Apache OFBiz version 24.09.06 from the official Apache repository (e.g., https://ofbiz.apache.org/download.html).
  3. 3. Stop the currently running OFBiz instance.
  4. 4. Replace the existing OFBiz installation files with the new version 24.09.06 files.
  5. 5. Restore any custom configurations, plugins, or data from the backup.
  6. 6. Review and update any custom code that may reference the hardcoded cryptographic key.
  7. 7. Start the OFBiz 24.09.06 instance and verify the application functions correctly.

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

Fix this in Ofbiz Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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