cve.bz

CVE-2026-50630 apache cxf: HTTP Request Splitting

6.5 mediumEPSS 0.4%Fix available

Medium (6.5) in apache cxf. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in org.apache.cxf:cxf-rt-rs-security-oauth2 4.1.7, 4.2.2.

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

Severity

CVSS 3.1

6.5 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
EPSS
0.4% (unchanged from 0.4% a week ago; 0.6% 30 days ago) estimated probability of exploitation activity in the next 30 days; 32nd 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-06-12. 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-113 Improper Neutralization of CRLF Sequences in HTTP Headers (HTTP Request Splitting)
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-50630 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-50630?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-50630?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-50630 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-50630

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-50630](https://cve.bz/cve/badge/CVE-2026-50630.svg)](https://cve.bz/cve/CVE-2026-50630)

HTML:

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

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Apache Software Foundation Apache CXFfrom 4.2.0 before 4.2.2
Apache Software Foundation Apache CXFfrom 4.0.0 before 4.1.7
Apache Software Foundation Apache CXFbefore 3.6.12

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-xf62-wr5p-5p95Mavenorg.apache.cxf:cxf-rt-rs-security-oauth2>=4.2.0 <4.2.24.2.2
GHSA-xf62-wr5p-5p95Mavenorg.apache.cxf:cxf-rt-rs-security-oauth2<4.1.74.1.7

Red Hat

Red Hat rates this Moderate.

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

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-50630.

Attack patterns (CAPEC)

  • CAPEC-31 Accessing/Intercepting/Modifying HTTP Cookies Likelihood: High · Severity: High
  • CAPEC-34 HTTP Response Splitting Likelihood: Medium · Severity: High
  • CAPEC-85 AJAX Footprinting Likelihood: High · Severity: Low
  • CAPEC-105 HTTP Request Splitting Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON