What is CVE-2026-105330?
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.
The record classifies CVE-2026-105330 under weakness class CWE-321. 1 affected-product entry is recorded, across 1 vendor, listed below.
Severity and exploitation probability
- CISA KEV
- Not listed in the CISA Known Exploited Vulnerabilities catalog
- Published
- 2026-11-05
Is CVE-2026-105330 being exploited?
It currently carries a trending score of 35 in the Threadlinqs vulnerability feed.
Affected products and versions
- Apache Software Foundation: Apache OFBiz
How to fix CVE-2026-105330
Vendor advisory: https://lists.apache.org/thread.html/7b2syzksp7klt9fvhdg0olldvs2g83lz. Apply the vendor fix referenced above to every affected product listed in this record, then confirm the running version against the vendor advisory.
Threat activity tracking CVE-2026-105330
1 tracked threat in the Threadlinqs corpus references CVE-2026-105330, either in the campaign’s CVE list or as an indicator on the campaign record.
Sources
Enriched from CVE.org, NVD, GitHub Security Advisories. Last verified by Threadlinqs on . This product uses the NVD API but is not endorsed or certified by the NVD.