CVE-2026-68481: Apache CXF: Revocation bypass in DefaultEncryptingOAuthDataProvider
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Apache CXF (DefaultEncryptingOAuthDataProvider)to a version that resolves this vulnerability.Fixed in 4.2.3 - Upgrade
Upgrade
Apache CXF (DefaultEncryptingOAuthDataProvider)to a version that resolves this vulnerability.Fixed in 4.1.8 - Upgrade
Upgrade
Apache CXF (DefaultEncryptingOAuthDataProvider)to a version that resolves this vulnerability.Fixed in 3.6.12
Event History
Frequently Asked Questions
What is the severity of CVE-2026-68481?
CVE-2026-68481 has a risk score of 51, indicating a moderate severity level.
How do I fix CVE-2026-68481?
To fix CVE-2026-68481, ensure that tokens are properly invalidated upon revocation in the DefaultEncryptingOAuthDataProvider.
What systems are affected by CVE-2026-68481?
CVE-2026-68481 affects the Apache CXF framework, specifically the DefaultEncryptingOAuthDataProvider component.
What are the implications of CVE-2026-68481?
CVE-2026-68481 allows revoked access and refresh tokens to still function, leading to potential unauthorized access.
Is there a workaround for CVE-2026-68481 pending a patch?
Currently, disabling the use of revoked tokens in the OAuth implementation may serve as a temporary workaround for CVE-2026-68481.