CVE-2026-50628
CRITICALCVE-2026-50628 is a critical-severity (CVSS 9.8) Improper Input Validation vulnerability in org.apache.cxf:cxf-rt-rs-security-oauth2. O3 Security confirms whether CVE-2026-50628 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Apache CXF: OAuth2: Inverted IP Binding Check Defeats Security Control
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.
- A successful exploit gives an attacker total control of the affected component, not partial access.
- 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-50628.
Real-World Exposure
org.apache.cxf:cxf-rt-rs-security-oauth2☕org.apache.cxf:cxf-rt-rs-security-oauth2Real-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
A logic error in OAuthRequestFilter rejects legitimate requests originating from the bound IP address, while blindly allowing requests from any other IP address. Enabling this
security feature inadvertently creates an inverse security check. Users are recommended to upgrade to versions 4.2.2 or 4.1.7 or 3.6.12, which fixes this issue.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.cxf:cxf-rt-rs-security-oauth2 | ≥ 4.2.0&&< 4.2.2 | 4.2.2 |
| ☕Maven | org.apache.cxf:cxf-rt-rs-security-oauth2 | all versions | 4.1.7 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.cxf:cxf-rt-rs-security-oauth2. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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-50628 is resolved across your whole dependency graph.
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.
How O3 protects you
O3 pinpoints whether CVE-2026-50628 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2026-50628. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
The Red Hat Product Security team has assessed the severity of this vulnerability as Important, given that it requires the attacker to first obtain a valid OAuth2 access token through a separate attack vector (such as token leakage, network interception, or log exposure) before exploitation is possible. Successful…
Frequently Asked Questions
Is CVE-2026-50628 in your dependencies?
O3 detects CVE-2026-50628 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.