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 — 4 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
37%
KEV
Not listed

Published

June 12, 2026

Last Modified

August 10, 2026

Advisory Details (2)

Auto-updated Aug 1, 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-oauth24.2.0, 4.2.14.2.2—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 31× in last 7d / 290× 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 540 total refreshes for this CVE.

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