CVE-2026-50627

CRITICALNVD 9.19.1—
EchelonGraph scoreMEDIUM confidence

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-06-12. NVD baseline CVSS 9.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.1Exploit: None knownExposed: 0

A fix is available — apply it.

The JwtAccessTokenValidator class in Apache CXF fails to validate the 'aud' (Audience) claims of incoming JWT access tokens. This allows a JWT issued for one Resource Server to be successfully replayed against a completely different Resource Server, leading to Token Confusion/Routing attacks. Users are recommended to upgrade to versions 4.2.2 or 4.1.7 or 3.6.12, which fixes this issue.

CVSS v3
9.1
EG Score
9.1(medium)
EG Risk
41(Track)
EG Risk 41/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity91% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
38%
KEV
Not listed

Published

June 12, 2026

Last Modified

August 10, 2026

Advisory Details (2)

Auto-updated Sep 16, 2026
No patch confirmed yet.
generic
https://lists.apache.org/thread/0jfzz9q992957b99tw7hodcqjfyxwb1m
generic

oss-security - CVE-2026-50627: Apache CXF: OAuth2: Missing JWT Audience and Issuer Validation in Access Token Validator

http://www.openwall.com/lists/oss-security/2026/06/11/4

Vendor Advisories for CVE-2026-50627(2)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatcxf-rt-rs-security-oauth2-saml2026-07-09redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFixed inDependents
org.apache.cxf:cxf-rt-rs-security-oauth22.6.0 ... 4.1.6 (159 versions)4.1.7—

Weakness Classification(2)

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

Data Freshness Timeline

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

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 563 total refreshes for this CVE.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-16 14:08 UTCEPSS rescore
  3. 2026-09-16 05:15 UTCEPSS rescore
  4. 2026-09-14 07:59 UTCVendor advisory
  5. 2026-09-14 04:04 UTCEG score recompute
  6. 2026-09-14 04:04 UTCVendor advisory
  7. 2026-09-13 16:47 UTCEPSS rescore
  8. 2026-09-11 14:53 UTCEPSS rescore
  9. 2026-09-10 09:35 UTCEPSS rescore
  10. 2026-09-08 22:01 UTCEPSS rescore
  11. 2026-09-07 16:01 UTCEPSS rescore
  12. 2026-09-06 13:47 UTCEPSS rescore
  13. 2026-09-04 05:06 UTCEPSS rescore
  14. 2026-09-02 14:12 UTCEPSS rescore
  15. 2026-09-01 13:54 UTCEPSS rescore
  16. 2026-09-01 04:40 UTCEPSS rescore
  17. 2026-08-30 23:48 UTCEG score recompute
  18. 2026-08-30 23:48 UTCVendor advisory
  19. 2026-08-30 19:17 UTCEPSS rescore
  20. 2026-08-30 01:22 UTCEPSS rescore
  21. 2026-08-28 21:41 UTCEPSS rescore
  22. 2026-08-27 14:25 UTCEPSS rescore
  23. 2026-08-26 14:46 UTCEPSS rescore
  24. 2026-08-25 13:49 UTCEPSS rescore
  25. 2026-08-25 03:43 UTCVendor advisory
Show 75 more
  1. 2026-08-24 23:51 UTCEG score recompute
  2. 2026-08-24 23:51 UTCVendor advisory
  3. 2026-08-23 22:29 UTCVendor advisory
  4. 2026-08-23 18:24 UTCVendor advisory
  5. 2026-08-23 14:31 UTCVendor advisory
  6. 2026-08-23 10:38 UTCEG score recompute
  7. 2026-08-23 10:38 UTCVendor advisory
  8. 2026-08-23 00:19 UTCEPSS rescore
  9. 2026-08-21 23:49 UTCEPSS rescore
  10. 2026-08-21 23:33 UTCVendor advisory
  11. 2026-08-21 19:13 UTCVendor advisory
  12. 2026-08-21 14:32 UTCVendor advisory
  13. 2026-08-21 10:28 UTCVendor advisory
  14. 2026-08-21 06:35 UTCVendor advisory
  15. 2026-08-21 00:50 UTCEG score recompute
  16. 2026-08-21 00:50 UTCVendor advisory
  17. 2026-08-20 22:55 UTCEPSS rescore
  18. 2026-08-20 20:56 UTCVendor advisory
  19. 2026-08-20 17:03 UTCVendor advisory
  20. 2026-08-20 17:03 UTCGHSA enrichment
  21. 2026-08-20 12:41 UTCVendor advisory
  22. 2026-08-20 12:41 UTCGHSA enrichment
  23. 2026-08-20 08:48 UTCEG score recompute
  24. 2026-08-20 08:48 UTCVendor advisory
  25. 2026-08-20 08:48 UTCGHSA enrichment
  26. 2026-08-19 17:04 UTCEPSS rescore
  27. 2026-08-19 13:46 UTCEG score recompute
  28. 2026-08-19 13:46 UTCVendor advisory
  29. 2026-08-19 13:46 UTCGHSA enrichment
  30. 2026-08-18 13:48 UTCEPSS rescore
  31. 2026-08-17 14:29 UTCEG score recompute
  32. 2026-08-17 14:29 UTCVendor advisory
  33. 2026-08-17 14:29 UTCGHSA enrichment
  34. 2026-08-17 13:47 UTCEPSS rescore
  35. 2026-08-17 10:36 UTCVendor advisory
  36. 2026-08-17 10:36 UTCGHSA enrichment
  37. 2026-08-17 06:40 UTCVendor advisory
  38. 2026-08-17 06:40 UTCGHSA enrichment
  39. 2026-08-17 02:48 UTCVendor advisory
  40. 2026-08-17 02:48 UTCGHSA enrichment
  41. 2026-08-16 22:55 UTCVendor advisory
  42. 2026-08-16 22:55 UTCGHSA enrichment
  43. 2026-08-16 15:10 UTCEG score recompute
  44. 2026-08-16 15:10 UTCVendor advisory
  45. 2026-08-16 15:10 UTCGHSA enrichment
  46. 2026-08-16 14:56 UTCEPSS rescore
  47. 2026-08-16 11:18 UTCVendor advisory
  48. 2026-08-16 11:18 UTCGHSA enrichment
  49. 2026-08-16 07:26 UTCVendor advisory
  50. 2026-08-16 07:26 UTCGHSA enrichment
  51. 2026-08-16 03:33 UTCEG score recompute
  52. 2026-08-16 03:33 UTCVendor advisory
  53. 2026-08-16 03:33 UTCGHSA enrichment
  54. 2026-08-16 02:14 UTCEPSS rescore
  55. 2026-08-15 23:41 UTCVendor advisory
  56. 2026-08-15 23:41 UTCGHSA enrichment
  57. 2026-08-15 18:23 UTCVendor advisory
  58. 2026-08-15 18:23 UTCGHSA enrichment
  59. 2026-08-15 14:29 UTCVendor advisory
  60. 2026-08-15 14:29 UTCGHSA enrichment
  61. 2026-08-15 10:36 UTCVendor advisory
  62. 2026-08-15 10:36 UTCGHSA enrichment
  63. 2026-08-15 05:57 UTCVendor advisory
  64. 2026-08-15 05:57 UTCGHSA enrichment
  65. 2026-08-15 01:39 UTCEG score recompute
  66. 2026-08-15 01:39 UTCVendor advisory
  67. 2026-08-15 01:39 UTCGHSA enrichment
  68. 2026-08-15 01:30 UTCEPSS rescore
  69. 2026-08-14 21:47 UTCVendor advisory
  70. 2026-08-14 21:47 UTCGHSA enrichment
  71. 2026-08-14 17:55 UTCVendor advisory
  72. 2026-08-14 17:55 UTCGHSA enrichment
  73. 2026-08-14 13:42 UTCVendor advisory
  74. 2026-08-14 13:42 UTCGHSA enrichment
  75. 2026-08-14 09:50 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-50627?
CVE-2026-50627 is a critical vulnerability published on June 12, 2026. The JwtAccessTokenValidator class in Apache CXF fails to validate the 'aud' (Audience) claims of incoming JWT access tokens. This allows a JWT issued for one Resource Server to be successfully replayed against a completely different Resource Server, leading to Token Confusion/Routing attacks. Users…
When was CVE-2026-50627 disclosed?
CVE-2026-50627 was first published in the National Vulnerability Database on June 12, 2026, with the most recent update on August 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-50627 actively exploited?
CVE-2026-50627 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 61.9% of all scored CVEs.
What is the CVSS score of CVE-2026-50627?
CVE-2026-50627 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-50627?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-50627, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-50627

Explore →

Is Your Infrastructure Affected by CVE-2026-50627?

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

Start Free Scan →Browse All CVEs