Apache CXF: OAuth2: HTTP Response Splitting via WWW-Authenticate Realm Injection
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- —
- Confidentiality · integrity · availability
- Low · Low · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CISA ADP. Fix status from CNA and GitHub.
Summary
A CRLF injection vulnerability exists in the OAuth2 AuthorizationUtils class. When constructing the WWW-Authenticate response header, the 'realm' parameter is concatenated without sanitizing Carriage Return (CR) and Line Feed (LF) characters. If an attacker can control the realm value, they can inject arbitrary HTTP headers or split the HTTP response entirely. Users are recommended to upgrade to versions 4.2.2 or 4.1.7 or 3.6.12, which fixes this issue.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- Yes
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| Apache | Apache CXF | 4.2.0 to before 4.2.2; 4.0.0 to before 4.1.7; before 3.6.12 | 4.2.2, 4.1.7, 3.6.12 | Patch available | CNA |
| — | org.apache.cxf:cxf-rt-rs-security-oauth2 (Maven) | 4.2.0 to before 4.2.2 | 4.2.2 | Patch available | GHSA-xf62-wr5p-5p95 |
| — | org.apache.cxf:cxf-rt-rs-security-oauth2 (Maven) | before 4.1.7 | 4.1.7 | Patch available | GHSA-xf62-wr5p-5p95 |
- Apache CXF VendorApache Affected 4.2.0 to before 4.2.2; 4.0.0 to before 4.1.7; before 3.6.12 Fixed in 4.2.2, 4.1.7, 3.6.12 Patch available CNA
- org.apache.cxf:cxf-rt-rs-security-oauth2 (Maven) Vendor— Affected 4.2.0 to before 4.2.2 Fixed in 4.2.2 Patch available GHSA-xf62-wr5p-5p95
- org.apache.cxf:cxf-rt-rs-security-oauth2 (Maven) Vendor— Affected before 4.1.7 Fixed in 4.1.7 Patch available GHSA-xf62-wr5p-5p95
Remediation
- Fix · CNA Apache CXF (Apache Software Foundation) Fixed in 4.2.2, 4.1.7, 3.6.12
- Fix · GHSA-xf62-wr5p-5p95 org.apache.cxf:cxf-rt-rs-security-oauth2 (Maven) Fixed in 4.2.2 Advisory →
- Fix · GHSA-xf62-wr5p-5p95 org.apache.cxf:cxf-rt-rs-security-oauth2 (Maven) Fixed in 4.1.7 Advisory →
Fixed in the same release
Records fixed by the same vendor advisory or release, as the CNA lists them.
- Release ·
Apache CXF 3.6.12, 4.1.7, 4.2.2
11 records Highest priority Priority MEDIUM 3 MEDIUM, 8 LOW
Other records, highest priority first
- TI-2026-37318 Apache CXF: OAuth2: Inverted IP Binding Check Defeats Security ControlPriority MEDIUM 50
- TI-2026-37317 Apache CXF: OAuth2: Missing JWT Audience and Issuer Validation in Access Token ValidatorPriority MEDIUM 48
- TI-2026-36773 Apache CXF: XML External Entity (XXE) Injection in W3CMultiSchemaFactory and EndpointReferenceUtilsPriority MEDIUM 43
Vendor assessments
Red Hat
Red Hat rating: Moderate. Red Hat's page for this CVE →
Not affected: 4 products
- Red Hat Fuse 7
- Red Hat JBoss Enterprise Application Platform Expansion Pack
- Red Hat JBoss Web Server 5
- Red Hat build of Apache Camel for Spring Boot 4
Timeline
- 2026-10-02 Threatist record created from CVE-2026-50630
- 2026-10-03 Alias added: GHSA-xf62-wr5p-5p95
References
More Apache Cxf vulnerabilities
- TI-2019-09264 Incorrect authorization in Apache CXF CVSS 3.1CRITICAL 9.8
- TI-2020-10930 Apache CXF Reflected XSS in the services listing page via the styleSheetPath CVSS 3.1MEDIUM 6.1
- TI-2010-01990 Apache CXF 2.0.x before 2.0.13, 2.1.x before 2.1.10, and 2.2.x before 2.2.9, as used in… CVSS 3.1CRITICAL 9.8
- TI-2022-22907 Apache CXF SSRF Vulnerability CVSS 3.1CRITICAL 9.8
- TI-2026-47481 Apache CXF: Unsafe deserialization of inbound JMS ObjectMessage CVSS 3.1CRITICAL 9.8
- TI-2025-31053 Apache CXF: Untrusted JMS configuration can lead to RCE CVSS 3.1CRITICAL 9.8
Sources
- CVE-2026-50630 · CVE Program
- CVE-2026-50630 · NVD
- FIRST EPSS
- GHSA-xf62-wr5p-5p95 · GitHub Advisory Database · CC BY 4.0
- CVE-2026-50630 · Red Hat security data · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences