Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
CRITICAL severity

CVE-2026-50627 — cxf-rt-rs-security-oauth2

CRITICAL

CVE-2026-50627 is a critical-severity (CVSS 9.1) CWE-289 vulnerability in org.apache.cxf:cxf-rt-rs-security-oauth2. A fix is available for org.apache.cxf:cxf-rt-rs-security-oauth2 — see the affected versions and patch details below.

Apache CXF: OAuth2: Missing JWT Audience and Issuer Validation in Access Token Validator

Also known asGHSA-9mrv-8pvf-hf4m
Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Oct 3, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • A successful exploit gives an attacker total control of the affected component, not partial access.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-50627.

EPSS Exploitation Probability

via FIRST.org ↗
0.8%probability of exploitation in next 30 days
Lower Risk+0.36%
Lower risk than most CVEs54th percentile — riskier than 54% of all scored CVEsHighest risk
0.00%0.43%0.85%1.28%0.4%0.8%Jul 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2026-50627 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 382,621 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

2 pkgs affected
☕org.apache.cxf:cxf-rt-rs-security-oauth2☕org.apache.cxf:cxf-rt-rs-security-oauth2

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.apache.cxf:cxf-rt-rs-security-oauth2≥ 4.2.0&&< 4.2.24.2.2org.apache.cxf:cxf-rt-rs-security-oauth2:4.2.2
☕Mavenorg.apache.cxf:cxf-rt-rs-security-oauth2all versions4.1.7org.apache.cxf:cxf-rt-rs-security-oauth2:4.1.7

Affected Products

1 product · 2 configurations
Application
cxfapache
≥ 4.2.0 && < 4.2.2
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.cxf:cxf-rt-rs-security-oauth2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update org.apache.cxf:cxf-rt-rs-security-oauth2 to 4.2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-50627 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

The Red Hat Product Security team has assessed the severity of this vulnerability as Important. Although authentication is required (the attacker must possess a valid JWT issued for some resource server), the flaw allows unauthorized access to protected resources on any other resource server using Apache CXF's…

Workaround published by Red Hat
Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
Source: Red Hat security advisory for CVE-2026-50627 (CC BY 4.0)
ProductFixed inAdvisory
Red Hat build of Apache Camel 4.18.1.P1 for Spring Boot 3.5.16cxf-rt-rs-security-oauth2RHSA-2026:37390

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is CVE-2026-50627 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2026-50627: Fixed in 4.2.2 (Critical 9.1) | O3 Security