Skip to content
VulniPulse
Advisory severityMedium4.2Red Hat Linux

Medium [CVE-2026-57818] Authorization Code Replay via Race Condition

This medium-severity Red Hat Linux advisory covers CVE-2026-57818 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.

CVE-2026-57818 Source published Source updated

VulniPulse record published Record updated

Affected products & platforms
Red Hat LinuxUnclassified
Open source advisory

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.

Matching phone alertsOptional email delivery

Summary

A race condition in JCacheCodeDataProvider allows an attacker to redeem a single authorization code multiple times via concurrent requests, resulting in the issuance of multiple distinct, valid access tokens. Users are recommended to upgrade to versions 4.2.3, 4.1.8 or 3.6.12, which fix this issue.

A flaw was found in Apache CXF. This can result in the issuance of multiple distinct, valid access tokens, potentially leading to unauthorized access or session hijacking.

Red Hat severity: Moderate — CVSS 4.2 (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N). Weakness: CWE-639.

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

Fixed versions
  • 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.