CVE-2026-68481

Modified Modified - Updated After Analysis

OAuth Token Introspection Flaw in Apache CXF

Publication date: 2026-08-06

Last updated on: 2026-10-24

Assigner: Apache Software Foundation

Description

In Apache CXF's DefaultEncryptingOAuthDataProvider, revoked access tokens still decrypt successfully, and TokenIntrospectionService reports active:true. The same applies to refresh tokens. This violates the RFC stipulations that 'The authorization server MUST invalidate the token.' and 'introspection of a revoked token MUST return {"active":false}'. Users are recommended to upgrade to versions 4.2.3 or 4.1.8 or 3.6.12, which fix this issue.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-08-06

Last Modified

2026-10-24

Generated

2026-11-08

AI Q&A

2026-08-06

EPSS Evaluated

2026-11-07

NVD

CVE-2026-68481

EUVD

EUVD-2026-53857

Affected Vendors & Products

Vendor	Product	Version / Range
apache	cxf	to 3.6.12 (exc)
apache	cxf	From 4.0.0 (inc) to 4.1.8 (exc)
apache	cxf	From 4.2.0 (inc) to 4.2.3 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-672	The product uses, accesses, or otherwise operates on a resource after that resource has been expired, released, or revoked.

Attack-Flow Graph

Executive Summary

This vulnerability in Apache CXF's DefaultEncryptingOAuthDataProvider allows revoked access and refresh tokens to still decrypt successfully. The TokenIntrospectionService incorrectly reports these revoked tokens as active:true, violating RFC requirements that revoked tokens must be invalidated and return active:false during introspection.

Detection Guidance

Check Apache CXF version using commands like 'cxf --version' or inspect application logs for OAuth token introspection responses. Look for revoked tokens still showing 'active:true' in responses.

Impact Analysis

This vulnerability could allow unauthorized access to resources even after tokens are revoked. Attackers might exploit revoked tokens to maintain access to systems or data, bypassing intended security controls and potentially leading to data breaches or unauthorized actions.

Compliance Impact

This vulnerability likely violates compliance requirements for GDPR and HIPAA, which mandate proper token revocation and access control. It could result in unauthorized data access, failing audits and potentially leading to legal penalties or loss of certification.

Mitigation Strategies

Upgrade Apache CXF to versions 4.2.3, 4.1.8, or 3.6.12 immediately. If upgrading is not possible, disable OAuth token introspection endpoints or revoke all existing tokens as a temporary workaround.

Hi! I’m here to help you understand CVE-2026-68481. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70

EPSS Chart

Security Radar

News mentioning this vulnerability

Loading related security news...