Vulnerability in org.apache.cxf:cxf-rt-rs-security-oauth2 (CVE-2026-50631)
Summary
Vulnerability in org.apache.cxf:cxf-rt-rs-security-oauth2 (CVE-2026-50631). Confidential information can be exposed externally. Mitigation: upgrade to 4.1.7 or later.
Original description
The description as published by the source.
A race condition in AbstractOAuthDataProvider allows concurrent requests using the same Refresh Token to bypass single-use semantics and generate multiple valid Access Tokens, when 'recycleRefreshTokens' is set to false. A leaked refresh token can be replayed concurrently by multiple attackers or threads. Users are recommended to upgrade to versions 4.2.2 or 4.1.7, which fixes this issue.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-50631 has been found in org.apache.cxf:cxf-rt-rs-security-oauth2.
Confidential information can be exposed externally. CVSS score: 7.4/10.
What to do: upgrade org.apache.cxf:cxf-rt-rs-security-oauth2 to 4.1.7 or later.
If unsure, ask your IT team or search "org.apache.cxf:cxf-rt-rs-security-oauth2 CVE-2026-50631" on the vendor's site.
CVE-2026-50631 (org.apache.cxf:cxf-rt-rs-security-oauth2) — CWE-367 / CVSS v3 7.4
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 4.1.7 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-367) exists in org.apache.cxf:cxf-rt-rs-security-oauth2.
Check the vendor advisory for the affected versions of org.apache.cxf:cxf-rt-rs-security-oauth2.
Severity: High (CVSS 7.4/10). Confidential information can be exposed externally.
Update to 4.1.7.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで org.apache.cxf:cxf-rt-rs-security-oauth2 を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade org.apache.cxf:cxf-rt-rs-security-oauth2 to 4.1.7ステージング環境で 4.1.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web lists.apache.org
- web openwall.com
- web github.com