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.
Published: 2026-11-05
Score: n/a
EPSS: n/a
KEV: No
Impact: Unrestricted Administrative Access
Action: Immediate Patch
AI Analysis

Impact

Apache OFBiz 24.09.06 and 24.09.07 contain a hard‑coded cryptographic key that is used to sign JSON Web Tokens. An attacker can construct a forged JWT signed with this factory‑default key, bypassing authentication and gaining unrestricted administrative access to the system. The weakness is a static key configuration flaw. This falls under the input validation and cryptographic misuse class identified by CWE‑321.

Affected Systems

The vulnerability applies to deployments of Apache OFBiz released before 24.09.08 that use the security.token.key value set to the default factory key. It specifically affects 24.09.06 and 24.09.07 on all operating platforms, and any upgrade from a release older than CVE‑2026‑31986 that preserves the old security.properties file with security.internal.sso.enabled set to true. Versions 24.09.08 and newer have the hard‑coded key removed, but upgrades of existing installations must run the rotateSecretKeys task to replace the persistent key.

Risk and Exploitability

The attacker must be able to send requests to the OFBiz application over the network; no local privilege escalation is required. Because the key is known, forging a JWT is trivial and does not require any interaction beyond possessing network connectivity. The lack of an EPSS score means the exploitation probability is unknown, but the presence of a full administrative bypass implies a severe impact. The vulnerability is not listed in CISA KEV, yet the potential for high‑privilege account takeover makes it a high‑priority issue.

Generated by OpenCVE AI on November 5, 2026 at 14:20 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Apache OFBiz to version 24.09.08 or later.
  • If the installation retained the old security.properties file, run './gradlew rotateSecretKeys' to generate a new, unique secret key.
  • Verify that the security.token.key is no longer set to the factory default and that security.internal.sso.enabled is correctly configured or disabled if SSO is not required.

Generated by OpenCVE AI on November 5, 2026 at 14:20 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Thu, 05 Nov 2026 13:45:00 +0000

Type Values Removed Values Added
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.
Title Apache OFBiz: Use of Hard-coded Cryptographic Key in JWT Token Authentication Enables Unauthenticated Administrative Access
Weaknesses CWE-321
References

Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: apache

Published:

Updated: 2026-11-05T13:40:03.111Z

Reserved: 2026-10-05T09:58:43.565Z

Link: CVE-2026-105330

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Awaiting Analysis

Published: 2026-11-05T14:16:59.423

Modified: 2026-11-05T14:48:26.210

Link: CVE-2026-105330

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-11-05T14:30:08Z

Weaknesses
  • CWE-321

    Use of Hard-coded Cryptographic Key