cve.bz

CVE-2026-73179 apache cxf

8.1 highEPSS 0.4%

High (8.1) in apache cxf. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
Improper enforcement of single-use authorization code semantics in the JPA OAuth2 authorization code grant provider in Apache CXFallows a remote attacker to obtain multiple valid access tokens from a single authorization code via concurrent token exchange requests that race the non-atomic find-then-delete operation against a shared relational database under READ_COMMITTED isolation. Users are recommended to upgrade to versions 4.2.4 or 4.1.9 or 3.6.13, which fixes this issue.

Severity

CVSS 3.1

8.1 high
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
0.4% (unchanged from 0.4% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 35th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-15. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-367 Time-of-check Time-of-use (TOCTOU) Race Condition
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-73179 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-73179?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-73179?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-73179 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-73179

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-73179](https://cve.bz/cve/badge/CVE-2026-73179.svg)](https://cve.bz/cve/CVE-2026-73179)

HTML:

<a href="https://cve.bz/cve/CVE-2026-73179"><img src="https://cve.bz/cve/badge/CVE-2026-73179.svg" alt="CVE-2026-73179"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Apache Software Foundation Apache CXFfrom 4.2.0 before 4.2.4
Apache Software Foundation Apache CXFfrom 4.0.0 before 4.1.9
Apache Software Foundation Apache CXFbefore 3.6.13

Red Hat

Red Hat rates this Low.

Red Hat's statement

Red Hat Product Security rates this vulnerability as Low impact because successful exploitation requires precise timing to win a race condition and only yields duplicate tokens for an already-authorized session. The issue only affects environments configuring Apache CXF with the JPA-based OAuth2 persistence layer. Because an attacker must already hold a legitimately issued authorization grant, this flaw does not allow bypassing authentication or escalating privileges beyond the intended scope.

ProductPackageStateAdvisory
Red Hat build of Apache Camel for Spring Boot 4cxf-rt-rs-security-oauth2Fix deferred
Red Hat Fuse 7cxf-rt-rs-security-oauth2Out of support scope
Red Hat JBoss Web Server 5cxf-rt-rs-security-oauth2Out of support scope

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-73179.

Attack patterns (CAPEC)

  • CAPEC-27 Leveraging Race Conditions via Symbolic Links Likelihood: Medium · Severity: High
  • CAPEC-29 Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON