Vulnerability

Apache OFBiz externalLoginKey Replay Flaw (CVE-2026-82907)

An authentication bypass in Apache OFBiz before 24.09.08.

CVE ID
CVE-2026-82907
CVSS
9.8 Critical (CVSS v3.1, CISA enrichment; NVD lists it as a secondary source); Apache as CNA gives no score and rates it important; no CVSS 4.0 score in the record or NVD
Affected product
Apache OFBiz before 24.09.08, per the CVE record
Exploited
Unknown
Published
5 November 2026 (CVE record and NVD); Apache announcement dated 4 November 2026 in the list archive

In short

CVE-2026-82907 is an authentication bypass in Apache OFBiz before 24.09.08. A captured externalLoginKey value works as a reusable login for the user it was issued to. The fix is version 24.09.08, and CISA's enrichment scores the flaw CVSS 3.1 9.8.

Profile MapVulnerability
  1. CVECVE-2026-82907
  2. ProductApache Software Foundation Apache OFBiz before 24.09.08, per the CVE record
  3. Fix Steps5actions listedUpgrade OFBiz to 24.09.08 · Find Every OFBiz Instance

What it allows

CVE-2026-82907 is an authentication flaw in Apache OFBiz, the open source ERP and e-commerce framework. OFBiz can pass a session token called externalLoginKey between its web applications. The CVE record says the server accepts that key from anyone, so a key that an attacker captures works as a login for the user it was issued to.

The record gives three reasons the key is dangerous. It is never bound to a client, it never expires and it is not invalidated after use. A captured key therefore gives a complete, reusable session without any cookie, in every web application that the user can reach.

Why the Check Comes Too Early

According to the record, the function checkExternalLoginKey runs as a global preprocessor. It runs ahead of both the CSRF check and the authentication check, so a valid key short-circuits the controls that would normally apply.

The record also says the framework itself helps spread the keys. OFBiz appends live keys to every cross-webapp link it renders. Separately, WidgetWorker does not validate the target of an inter-app link. An authenticated user's key can then be attached to an attacker-chosen absolute URL and delivered to the attacker's own server.

How the Score Reads

Apache, the CNA, gives no CVSS score in the record. It rates the issue "important" in a textual severity field. CISA's enrichment, listed by NVD as a secondary source, scores it CVSS 3.1 9.8 Critical with vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. There is no CVSS 4.0 score in the record or NVD.

Our reading is that the 9.8 assumes the attacker already holds a live key. The record does not say how likely that is in a given deployment, and the score does not reflect it. NVD shows the entry as undergoing analysis on 5 November 2026.

What Apache, CISA SSVC and KEV Say

The Apache announcement says the release fixes multiple vulnerabilities, "including some critical issues", and tells users to upgrade to 24.09.08. CISA's SSVC record in the CVE entry lists exploitation as none, automatable as yes and technical impact as total, dated 5 November 2026.

As of CISA catalog version 2026.11.04, the CVE is not in the Known Exploited Vulnerabilities catalog. Our KEV glossary entry explains the catalog. The credential at the center of this flaw behaves like the tokens described in our session hijacking entry.

The Other Flaws in the Same Release

The OFBiz security page lists 46 CVEs from 2026 as affecting releases before 24.09.08 and fixed in that release. Apache's announcement gives each a one-line title. Several describe unauthenticated or remote code execution risk, such as CVE-2026-68524 (pre-authentication remote code execution through screen definition loading) and CVE-2026-83542 (unauthenticated remote code execution through login-page widget injection).

Others cover authorization bypasses, path traversal, SQL injection, a hard-coded JWT key (CVE-2026-105330) and a password reset flaw that enables full account takeover (CVE-2026-109928). We have not scored or tested them. One upgrade to 24.09.08 covers the whole list, so the other CVEs are a reason to move quickly, not a separate project.

Who is affected

The CVE record lists Apache OFBiz from version 0 up to but not including 24.09.08, as a semver range, and the description says "24.09 before 24.09.08 on all platforms". Apache's announcement states the affected versions as "all versions prior to 24.09.08". The fix is version 24.09.08.

The sources differ in wording, not in the fix. Because the announcement says "all versions", we recommend treating any OFBiz release older than 24.09.08 as affected, including the 18.12 branch, until Apache says otherwise. The record names no earlier fixed release for this CVE.

The record credits Bartlomiej Dmitruk at striga.ai as the reporter and Krishna Uprit as the remediation developer. Our vulnerability management guide covers how to track a rollout like this, and the patch management entry covers the process.

Timeline

  1. 31 Aug 2026

    Apache reserves CVE-2026-82907 (CVE record).

  2. 4 Nov 2026

    Apache's CVE announcement for OFBiz is posted to the user mailing list, according to the list archive.

  3. 5 Nov 2026

    The CVE record is published and NVD publishes its entry. CISA adds SSVC data to the record.

What to do

  1. Upgrade OFBiz to 24.09.08

    Move every instance to 24.09.08, the fixed release Apache names. The same release fixes the 45 other 2026 CVEs on the security page for that version.

  2. Find Every OFBiz Instance

    List internet-facing and internal OFBiz servers, including ERP, e-commerce and back-office installs, and record the version of each. Treat anything older than 24.09.08 as affected.

  3. Treat externalLoginKey as a Credential

    We recommend checking web server, proxy and application logs for externalLoginKey values in requests from unfamiliar addresses. The key is a bearer credential, so a value in a log or a Referer header is exposed.

  4. Restrict Access While You Patch

    We recommend limiting access to OFBiz web applications to trusted networks or a VPN until the upgrade is done, and ending active sessions after the upgrade.

  5. Review the Wider Release Notes

    Read Apache's list of fixed CVEs for the 24.09.08 release and note the unauthenticated ones, such as the pre-authentication remote code execution entries, when you rank the rollout.

Questions

Which Apache OFBiz versions does CVE-2026-82907 affect?

The record lists versions before 24.09.08. Apache's announcement says all versions prior to 24.09.08 are affected. Version 24.09.08 contains the fix.

What is the externalLoginKey?

It is a token OFBiz uses to carry a login between its web applications. The CVE record says the server accepts it as a bearer credential that never expires and is not bound to a client.

Does the attacker need an account?

The record says a remote unauthenticated attacker is enough, but the attacker must first capture a live key issued to a user.

Is CVE-2026-82907 in the CISA KEV catalog?

It is not in catalog version 2026.11.04. CISA's SSVC entry in the CVE record lists exploitation as none, automatable as yes and technical impact as total.

Why does the score say 9.8 when a key must be captured first?

The CISA-enriched vector sets privileges required to none and user interaction to none. The record does not explain how an attacker obtains the key, so the score assumes it.

In our research

  1. Session cookie Glossary term
  2. Session hijacking Glossary term

Sources

  1. CVE-2026-82907 Record CVE Program / Apache CNA
  2. CVE-2026-82907 NVD
  3. Apache OFBiz: CVE Announcements Apache OFBiz user mailing list
  4. Apache OFBiz Security Apache OFBiz project
  5. Known Exploited Vulnerabilities Catalog CISA