External risk intelligence

Apache OFBiz JWT Authentication Hard-coded Key Vulnerability Allows Full Administrative Access

CVE advisorySeverity: CRITICAL (CVSS 9.8)

CVE-2026-105330

Apache OFBiz is an enterprise resource planning system typically deployed as an internet-facing web application. Since this vulnerability affects authentication mechanisms for the application, the vulnerable surface is commonly accessible via public web interfaces in standard enterprise deployments.

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A critical vulnerability exists in Apache OFBiz, an enterprise resource planning system, that could allow an unauthenticated attacker to gain full administrative control. This is due to a hard-coded cryptographic key used in token authentication, potentially enabling unauthorized access if specific upgrade paths were followed.

  • Attackers could gain full administrative access.
  • It affects authentication in an enterprise resource planning system.
  • Confirm relevance and exposure to ERP systems.

Attack Path

How an attacker could exploit the issue

An attacker could start with network access to a vulnerable Apache OFBiz deployment. If the deployment was upgraded from an older version without properly rotating cryptographic keys, the attacker could forge a JSON Web Token (JWT) using a default, hard-coded key. This forged token could grant the attacker full administrative access to the system.

  • Network access required.
  • Forged JWT with default key.
  • Full administrative access gained.

Live Threat

Current exploitation, exposure, and threat context

An unauthenticated attacker could gain full administrative access to Apache OFBiz deployments by exploiting a hard-coded cryptographic key in the JWT token authentication. This risk is present when a deployment upgraded from an older release, retaining an existing security properties file with a specific setting enabled, and has not subsequently rotated its security keys.

  • Administrative access to the system.
  • Forged JWT signed with a default key.
  • Full administrative control of OFBiz.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability in Apache OFBiz's JWT token authentication likely impacts application owners and infrastructure teams responsible for its deployment and maintenance. The first practical step is to identify all instances of OFBiz, assess their exposure and criticality, and locate the accountable system owner. Remediation planning should then be risk-based, considering the need to rotate secret keys in addition to upgrading.

  • Application and infrastructure teams own this.
  • Verify OFBiz instances and their reachability.
  • Upgrade and rotate secret keys as needed.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is Apache OFBiz?

Apache OFBiz is an open-source enterprise resource planning (ERP) system. Organizations use it to automate complex business processes like accounting, manufacturing, human resources, and e-commerce through a suite of integrated enterprise applications.

What does CVE-2026-105330 mean?

This vulnerability is classified as CWE-321: Use of Hard-coded Cryptographic Key. In this context, it means the software uses a default, predictable secret value to sign JSON Web Tokens (JWTs) used for authentication. An attacker who knows this default value can forge their own identity, allowing them to bypass login controls and impersonate a full administrator.

How can an attacker trigger this bug?

An attacker needs network access to the target deployment. The vulnerability is triggered if the system carries over an old security configuration file from a version predating previous security patches while single sign-on remains enabled. Crucially, simply running the software in a modern, freshly installed state without these legacy configuration files does not inherently trigger this specific vulnerability.

Is my Apache OFBiz deployment at risk?

Halo Surface Signal indicates that Apache OFBiz is frequently deployed as an internet-facing web application. If your instance is reachable over the public internet, the potential for unauthorized administrative access is significantly higher. Organizations using OFBiz for internal business operations should still review their configurations to determine if they meet the specific criteria involving legacy security files.

How do I fix this security flaw?

You must first upgrade to version 24.09.08. However, upgrading alone is insufficient because it does not automatically overwrite existing, insecure secret keys in your configuration files. After the upgrade, you must manually run the './gradlew rotateSecretKeys' command to generate and apply a new, secure key to your environment.

References