OAuth2 authorization bypass via inverted IP comparison
Published Jun 12, 2026 · Updated Jun 12, 2026
IP-binding bypass in Apache CXF before 3.6.12, 4.0.0 through 4.1.6, and 4.2.0 through 4.2.1 allows remote attackers to reuse bound tokens. OAuthRequestFilter reverses the intended address comparison, rejecting the token's bound IP address while accepting every nonmatching source address. The flaw is reachable when token IP binding is enabled and a bound token is presented, granting that token's access to protected resources from another address.
Summary
What happened
IP-binding bypass in Apache CXF before 3.6.12, 4.0.0 through 4.1.6, and 4.2.0 through 4.2.1 allows remote attackers to reuse bound tokens. OAuthRequestFilter reverses the intended address comparison, rejecting the token's bound IP address while accepting every nonmatching source address. The flaw is reachable when token IP binding is enabled and a bound token is presented, granting that token's access to protected resources from another address.
The record
- CVE
- CVE-2026-50628
- Published
- Jun 12, 2026
- Updated
- Jun 12, 2026
- Vendor
- The Apache Software Foundation
- Product
- Apache CXF
- Classifications
- CWE-20, CWE-358, T1550.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 12, 2026CVE publishedPublication date reported by the CVE source.
- Jun 12, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <4.1.7
- Affected versionversion=4.2.0 <4.2.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo