# CVE-2026-50629: Fixed in 4.2.2 (Medium 5.3) | O3 Security ☕ ☕ Maven Not in CISA KEV MEDIUM severity # CVE-2026-50629 — cxf-rt-rs-security-oauth2 MEDIUM CVE-2026-50629 is a medium-severity (CVSS 5.3) CWE-93 vulnerability in org.apache.cxf:cxf-rt-rs-security-oauth2. A fix is available for org.apache.cxf:cxf-rt-rs-security-oauth2 — see the affected versions and patch details below. Apache CXF: OAuth2: Log Injection via Unsanitized Client Identifier Also known as[GHSA-f8p7-h97q-7vx7](/vulnerability/GHSA-f8p7-h97q-7vx7) Published Jun 12, 2026 Updated Aug 20, 2026 Affected 2 pkgs Patched 2 / 2 Exploits None indexed Exploitation data as of Oct 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS) ## Exploitation Status ### No confirmed exploitation observed yet - CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks. - CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment. Exploitation and automatability from CISA’s SSVC triage for CVE-2026-50629. ## EPSS Exploitation Probability [via FIRST.org ↗](https://www.first.org/epss/) 0.7%probability of exploitation in next 30 days Lower Risk0.00% Lower risk than most CVEs52th percentile — riskier than 52% of all scored CVEsHighest risk 0.00%0.40%0.80%1.20%0.4%0.7%0.7%Sep 26Oct 26Oct 26 Probability of exploitation in the next 30 days, from [FIRST.org EPSS](https://www.first.org/epss/). ## How urgent is this, really CVE-2026-50629 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner. ## Where this sits among everything scored Of 383,485 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled. ## Real-World Exposure 2 pkgs affected ☕`org.apache.cxf:cxf-rt-rs-security-oauth2`☕`org.apache.cxf:cxf-rt-rs-security-oauth2` Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems. ## 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. ## Affected Packages 2 total 2 fixed Ecosystem Package Vulnerable range Fix ☕Maven `org.apache.cxf:cxf-rt-rs-security-oauth2` ≥ 4.2.0&&< 4.2.2 4.2.2`org.apache.cxf:cxf-rt-rs-security-oauth2:4.2.2` ☕Maven `org.apache.cxf:cxf-rt-rs-security-oauth2` all versions 4.1.7`org.apache.cxf:cxf-rt-rs-security-oauth2:4.1.7` ## Affected Products 1 product · 2 configurations Application `cxf`apache ≥ 4.2.0 && < 4.2.2 range ## Detection & mitigation playbook Open-source dependency 1. ### Detect Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.cxf:cxf-rt-rs-security-oauth2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version. 2. ### Fix Update org.apache.cxf:cxf-rt-rs-security-oauth2 to 4.2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-50629 is resolved across your whole dependency graph. 3. ### Workarounds If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands. ## Frequently Asked Questions 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. O3 Security · Impact-Aware SCA ### Is CVE-2026-50629 in your dependencies? Find it across Maven, including transitive dependencies. [Scan my dependencies](/book-demo) [How O3 SCA works](/impact-aware-sca)