CxfApplication · Apache
CVE-2026-50627
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe JwtAccessTokenValidator class in Apache CXF does not validate the 'aud' (audience) claim in incoming JWT access tokens. This allows attackers to replay tokens issued for one Resource Server against a different Resource Server, enabling Token Confusion/Routing attacks where a compromised or targeted token can be used across multiple services.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
CxfApplication
< 4.1.7>= 4.2.0, < 4.2.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if Apache CXF is in useReview project dependencies (Maven pom.xml, Gradle build.gradle) or scan for cxf*.jar files in the application lib/classpath.Affected if Apache CXF is present as a dependency or library file.
-
Determine the installed CXF versionLocate the CXF JAR file (typically cxf-core-*.jar or cxf-rt-security-*.jar) and read the version from the filename, or query via Maven: mvn dependency:tree | grep cxfAffected if The version is < 4.1.7 OR >= 4.2.0 AND < 4.2.2.
-
Check for JwtAccessTokenValidator usageSearch codebase for imports or references to org.apache.cxf.security.oauth2.jwt.JwtAccessTokenValidator or similar JWT validation configuration classes.Affected if JwtAccessTokenValidator class is being used for token validation.
-
Verify audience claim validation configurationInspect OAuth2/JWT filter or provider configuration files and Java code for audience (aud) claim validation settings. Look for properties like 'validateAudience', 'audienceValidation', or custom validator registration.Affected if Audience claim validation is NOT explicitly enabled or configured, or the code relies on the default JwtAccessTokenValidator behavior.
A user is affected if they run a vulnerable CXF version AND use JwtAccessTokenValidator for JWT validation WITHOUT explicit audience claim validation configured.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped4.1.74.2.2
Upgrade Apache CXF to version 4.2.2 or 4.1.7 which includes proper audience claim validation in the JwtAccessTokenValidator.
4.2.2 or 4.1.7
- 1. Identify all dependencies on Apache CXF in your project by reviewing pom.xml files (Maven) or build.gradle files (Gradle)
- 2. Locate the CXF version declarations (look for cxf.version properties or cxf-* dependencies)
- 3. Update the CXF version to 4.1.7 (for 4.x stable) or 4.2.2 (for 4.2.x current)
- 4. If using Maven, run 'mvn dependency:tree' to verify the CXF version is updated across all modules
- 5. Rebuild your project and run all tests, particularly any JWT/OAuth validation tests
- 6. Deploy to staging and validate JWT token processing still works correctly with audience validation
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Cxf
Scoped from the published advisory
- Consultation3.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,840.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-50627 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-50627 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data