cve.bz

CVE-2026-68481 apache cxf

7.5 highEPSS 0.7%

High (7.5) in apache cxf. EPSS 0.7% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS
0.7% (unchanged from 0.7% a week ago; 0.7% 30 days ago) estimated probability of exploitation activity in the next 30 days; 52nd percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-08-06. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-672 Operation on a Resource after Expiration or Release
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-68481 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-68481?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-68481?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-68481 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-68481

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-68481](https://cve.bz/cve/badge/CVE-2026-68481.svg)](https://cve.bz/cve/CVE-2026-68481)

HTML:

<a href="https://cve.bz/cve/CVE-2026-68481"><img src="https://cve.bz/cve/badge/CVE-2026-68481.svg" alt="CVE-2026-68481"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Apache Software Foundation Apache CXFfrom 4.2.0 before 4.2.3
Apache Software Foundation Apache CXFfrom 4.0.0 before 4.1.8
Apache Software Foundation Apache CXFbefore 3.6.12

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

Moderate: This flaw in Apache CXF's OAuth2 token handling allows previously revoked access and refresh tokens to remain valid. This bypasses intended revocation mechanisms, potentially enabling unauthorized access to resources in applications deployed on affected Red Hat platforms that utilize the DefaultEncryptingOAuthDataProvider.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

ProductPackageStateAdvisory
Red Hat build of Apache Camel for Spring Boot 4cxf-rt-rs-security-oauth2Fix deferred
Red Hat JBoss Enterprise Application Platform Expansion Packcxf-rt-rs-security-oauth2Fix deferred
Red Hat JBoss Web Server 5cxf-rt-rs-security-oauth2Fix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-68481.

References

Check your stackJSON