Cyber Resilience

CVE-2026-68481

Apache Cxf ≤ 3.6.12

Published
06 August 2026
Modified
07 August 2026
Patch / advisory
CVSS Score v3.1 7.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS Score 0.0043 35th percentile
Risk Priority 57 floored blend · peak EPSS

Summary

CVE-2026-68481 is a high-severity Operation on a Resource after Expiration or Release (CWE-672) vulnerability in Apache Cxf. Its CVSS base score is 7.5 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 35th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and IA-5 (Authenticator Management) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

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…

more

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.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-57817Same product: Apache Cxf
CVE-2026-50632Same product: Apache Cxf
CVE-2026-50633Same product: Apache Cxf
CVE-2025-48913Same product: Apache Cxf
CVE-2026-66909Same product: Apache Cxf
CVE-2026-50628Same product: Apache Cxf
CVE-2024-32007Same product: Apache Cxf
CVE-2024-29736Same product: Apache Cxf
CVE-2026-61466Same product: Apache Cxf
CVE-2026-44930Same product: Apache Cxf

Affected Assets

apache
cxf
≤ 3.6.12 · 4.0.0 — 4.1.8 · 4.2.0 — 4.2.3

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)
  • 1 hardening rule · 1 OS baseline
Validate
Prove the fix (OWASP ASVS)

Mitigating Controls (NIST 800-53 r5) AI

Access enforcement applies current authorizations to every request, directly blocking operations once a resource has been revoked or released.

Authenticator management mandates revocation and replacement procedures that render expired credentials unusable.

Account lifecycle management includes explicit revocation and disabling steps that stop subsequent operations on released accounts or identifiers.

Identifier management requires deallocation and reuse controls that prevent continued use of released identifiers.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.AA-05 mostly match
prevents

Enforcing managed authorizations and revocations directly prevents post-release operations on credentials or entitlements.

PR.PS-06 mostly match
prevents

Secure development practices eliminate the root coding flaw that permits use-after-release.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing can detect use-after-release but does not prevent it at runtime.

degrades

Enforces timely deletion of resources so they cannot be used after release.

prevents

Secure-coding rules require checks that prevent operations on freed or expired objects.

prevents

Change-management processes can introduce or remove resource-lifetime controls.

References