Skip to main content
VulnerabilityPublished

CVE-2026-105330: Apache OFBiz · Use of Hard-coded Cryptographic Key

Affects Apache OFBizSource CVE Database V5

0
Compare

Mentioned vulnerabilities

Not known to be exploited : upgrade to 24.09.08 soon.

Data as of 5 Nov 2026, 14:05 UTC

Severity
High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in 24.09.08

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Upgrade Apache OFBiz to 24.09.08.

Affected software

ProductAffectedFixed in
Apache Software FoundationApache OFBizAffected
  • >=24.09.06 <24.09.08
Fixed in
  • 24.09.08

AI-suggested

Upgrade Apache OFBiz to version 24.09.08 or later. After upgrading, if the deployment was upgraded from a version predating CVE-2026-31986 and retained its original security.properties with security.internal.sso.enabled set to true, run './gradlew rotateSecretKeys' to replace the hard-coded cryptographic key. Simply upgrading without rotating keys does not mitigate the vulnerability.

Description

Apache OFBiz versions 24.09.06 and 24.09.07 contain a hard-coded cryptographic key vulnerability in JWT token authentication. This flaw allows an unauthenticated attacker with network access to gain full administrative privileges by forging a JWT signed with the default security.token.key. The issue affects deployments upgraded from versions before CVE-2026-31986 that retained their original security.properties with security.internal.sso.enabled set to true. The vulnerability is fixed in version 24.09.08. Users must upgrade and run './gradlew rotateSecretKeys' to replace any existing hard-coded keys.

References

Community reviews

Loading reviews…