CVE-2026-50629 Apache CXF: OAuth2: Log Injection via Unsanitized Client Identifier

Medium 5.3 Published Updated

Attackers can inject arbitrary content into Apache CXF OAuth2 server logs via the unsanitized clientId parameter, potentially corrupting audit trails.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2026-50629?

CVE-2026-50629 is a medium-severity vulnerability in Apache Cxf, published on 12 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

The 'clientId' parameter from incoming HTTP requests is directly concatenated into OAuth2 server log warning messages without sanitizing control characters. This allows an attacker to inject arbitrary content, including fake log entries, into the server's log files. Users are recommended to upgrade to versions 4.2.2 or 4.1.7 or 3.6.12, which fixes this issue.

Weakness: CWE-93

Which versions are affected by CVE-2026-50629?

4 open source packages ship an affected version, including org.apache.cxf:cxf-rt-rs-security-oauth2. It affects 1 product.

PackageAffectedFixed in
org.apache.cxf:cxf-rt-rs-security-oauth2 MavenAll versions4.1.7
org.apache.cxf:cxf-rt-rs-security-oauth2 MavenAll versions4.1.7
org.apache.cxf:cxf-rt-rs-security-oauth2 MavenFrom 4.2.04.2.2
org.apache.cxf:cxf-rt-rs-security-oauth2 MavenFrom 4.2.04.2.2

Products include Apache Cxf.

How do I fix CVE-2026-50629?

Upgrade org.apache.cxf:cxf-rt-rs-security-oauth2 to a fixed version for your release line: 4.1.7 or 4.2.2.

Is CVE-2026-50629 being exploited?

There is no known exploitation of CVE-2026-50629 in the wild and no public exploit code.

All Apache Cxf vulnerabilities

Sources

Also known as GHSA-f8p7-h97q-7vx7.

Is CVE-2026-50629 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free