CVE-2026-73179

UNRATEDCVSS · not yet scoredTrending — 5 sources updated this week
—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS v2: —Exploit: None knownExposed services: Not assessed

The CVE record names the fixed release — apply it.

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.

CVSS v3
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0.2%
EPSS %ILE
11th
KEV
Not listed

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 9, 2026

Last Modified

October 9, 2026

References (2)

Vendor Advisories for CVE-2026-73179(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 13× in last 7d / 13× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  3. 2026-10-12 15:41 UTCEG score recompute
  4. 2026-10-11 19:26 UTCEG score recompute
  5. 2026-10-11 16:42 UTCEG score recompute
  6. 2026-10-11 14:02 UTCEG score recompute
  7. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  9. 2026-10-09 16:55 UTCGHSA enrichmentGHSA-4856-vwpx-pmq8
  10. 2026-10-09 12:32 UTCGHSA enrichmentGHSA-4856-vwpx-pmq8
  11. 2026-10-09 11:29 UTCNVD update
  12. 2026-10-09 10:28 UTCEG score recompute
  13. 2026-10-09 10:28 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(4)

What is CVE-2026-73179?
CVE-2026-73179 is a vulnerability whose severity is not yet rated; its CVE record was published on October 9, 2026. 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…
When was the CVE record for CVE-2026-73179 published?
The CVE record for CVE-2026-73179 was published on October 9, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 9, 2026; the record at its source may have been updated since.
Is CVE-2026-73179 actively exploited?
CVE-2026-73179 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (11th percentile of EPSS-scored CVEs).
How do I remediate CVE-2026-73179?
The CVE record for CVE-2026-73179 names the fix: "Users are recommended to upgrade to versions 4.2.4 or 4.1.9 or 3.6.13, which fixes this issue." The vendor advisories EchelonGraph has for CVE-2026-73179 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-73179

Explore →

Is Your Infrastructure Affected by CVE-2026-73179?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs