- Exploited
- No known exploitation
- Fix
- Fixed in 24.09.08
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 24.09.08.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 0/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Apache OFBiz contains a hard-coded cryptographic key flaw in its JWT token authentication that lets an unauthenticated attacker gain full administrative access. Over the network, an attacker can forge a JWT signed with the factory-default `security.token.key` value, which affects deployments upgraded from earlier releases that kept their existing `security.properties` with `security.internal.sso.enabled` set to true.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
Use of Hard-coded Cryptographic Key in JWT token authentication in Apache OFBiz 24.09.06 and 24.09.07 on all platforms allows an unauthenticated, network-reachable attacker to obtain full administrative access via a forged JWT signed with the factory-default security.token.key value that CVE-2026-31986 removed from newly generated configurations, on a deployment that upgraded from a release predating that fix while retaining its existing security.properties with security.internal.sso.enabled set to true. Users are recommended to upgrade to version 24.09.08. Upgrading alone does not replace an already-configured key: deployments that carried framework/security/config/security.properties forward from a release predating the CVE-2026-31986 fix must also run './gradlew rotateSecretKeys' after upgrading, since the existing generateSecretKeys task leaves an already-set value untouched.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity?/10Unknown. No CVSS score or vendor rating
- No patch0/5No signal
What would change the score
- Would score about 55 if added to CISA KEV
- Would score about 50 if CISA's SSVC rates exploitation active
- Would score about 22 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 24.09.08.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Apache Software Foundation Apache OFBiz
From 24.09.06 · fixed in 24.09.08
Evidence 1
- Advisory
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-105330
Is CVE-2026-105330 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-105330?
Apache OFBiz: from 24.09.06 before 24.09.08.Source: cve.now feed data
How do I fix CVE-2026-105330?
Upgrade to a fixed version: 24.09.08.Source: cve.now feed data