Medium [CVE-2026-68079] Authorization code replay due to flaw in DefaultEncryptingCodeDataProvider
This medium-severity Red Hat Linux advisory covers CVE-2026-68079 affecting Red Hat build of Apache Camel for Spring Boot 4, Red Hat JBoss Web Server 5.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published Record updated
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.
Summary
In Apache CXF's DefaultEncryptingCodeDataProvider, a captured authorization code can be redeemed an unlimited number of times due to a flaw in the implementation of the removeCodeGrant functionality.
This violates the RFC requirement that "The authorization code MUST NOT be used more than once." Users are recommended to upgrade to versions 4.2.3 or 4.1.8 or 3.6.12, which fix this issue. The flaw exists due to an issue in the `removeCodeGrant` functionality, which fails to properly invalidate used authorization codes.
This can lead to unauthorized access or session hijacking, violating the security principle that authorization codes should only be used once. Red Hat severity: Moderate — CVSS 5.3 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N).
Weakness: CWE-613. Affected Red Hat products: Red Hat build of Apache Camel for Spring Boot 4; Red Hat JBoss Web Server 5.
Will not fix / out of support: Red Hat JBoss Web Server 5. Red Hat does not currently list a fixing RHSA for this CVE.
Affected versions
No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.
Official advisory · high-confidence parse· fetched 26 days ago·verify at source
- 4.2.3
- 4.1.8
- 3.6.12
Official advisory · high-confidence parse· fetched 26 days ago·verify at source
Mitigation
Upgrade to a fixed release: 4.2.3, 4.1.8, 3.6.12. That is the remediation for this advisory.
The vendor advisory may list additional interim mitigations or workarounds not captured here — review it before change work.
Official advisory · high-confidence parse· fetched 26 days ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.