CVE-2026-105330
Awaiting Analysis Awaiting Analysis - Queue

Hard-coded Cryptographic Key in Apache OFBiz JWT Authentication

Publication date: 2026-11-05

Last updated on: 2026-11-05

Assigner: Apache Software Foundation

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-05
Last Modified
2026-11-05
Generated
2026-11-05
AI Q&A
2026-11-05
EPSS Evaluated
N/A
NVD
CVE-2026-105330
EUVD
EUVD-2026-117524

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
Apache Software Foundation Apache OFBiz 24.09.06

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-321 The product uses a hard-coded, unchangeable cryptographic key.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability involves a hard-coded cryptographic key in JWT token authentication in Apache OFBiz versions 24.09.06 and 24.09.07. An unauthenticated attacker can exploit this to forge JWT tokens and gain full administrative access. The issue arises when upgrading from older versions that retained a default security token key after a previous fix (CVE-2026-31986) was applied.

Detection Guidance

Detecting this vulnerability requires checking for the presence of a hard-coded cryptographic key in JWT token authentication. Inspect the security.properties file for security.token.key values and verify if security.internal.sso.enabled is set to true. Use commands like grep to search for these configurations in Apache OFBiz directories.

Impact Analysis

An attacker could exploit this to gain unauthorized administrative access to your Apache OFBiz system, potentially leading to data breaches, unauthorized modifications, or complete system compromise. This is especially critical if the system handles sensitive data.

Compliance Impact

This vulnerability could lead to unauthorized access and data breaches, violating compliance requirements under GDPR, HIPAA, and other regulations. It may result in legal penalties, loss of trust, and reputational damage due to compromised sensitive data.

Mitigation Strategies

Upgrade to Apache OFBiz version 24.09.08. After upgrading, run ./gradlew rotateSecretKeys to replace any existing hard-coded keys. Ensure the security.properties file does not retain old configurations from pre-CVE-2026-31986 releases.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-105330. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...