Categories
CVE-2026-50623 medium CVSS 4.8

Authentication Bypass in org.apache.cxf:cxf-rt-rs-security-oauth2 (CVE-2026-50623)

Summary

Authentication bypass in org.apache.cxf:cxf-rt-rs-security-oauth2 (CVE-2026-50623). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 4.1.7 or later.

Original description

The description as published by the source.

An authentication bypass vulnerability exists in the OAuth2 TokenIntrospectionService in Apache CXF. Due to a missing 'throw' keyword in the security context check, the introspection endpoint (/services/oauth2/introspect) can be accessed by any unauthenticated network attacker. However note that this is a safeguard only in the case that someone forgot to enable authentication on the service. Users are recommended to upgrade to version 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-50623 has been found in org.apache.cxf:cxf-rt-rs-security-oauth2.
Risk of unauthorized operations or information disclosure. CVSS score: 4.8/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-50623" on the vendor's site.

CVE-2026-50623 (org.apache.cxf:cxf-rt-rs-security-oauth2) — CWE-287 / CVSS v3 4.8
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.

❓ What is the problem

Authentication bypass (CWE-287) exists in org.apache.cxf:cxf-rt-rs-security-oauth2.

📍 Affected scope

Check the vendor advisory for the affected versions of org.apache.cxf:cxf-rt-rs-security-oauth2.

🔥 Severity

Severity: Medium (CVSS 4.8/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 4.1.7.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

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

  1. 1
    Identify exposure identify
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで org.apache.cxf:cxf-rt-rs-security-oauth2 を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch
    Upgrade org.apache.cxf:cxf-rt-rs-security-oauth2 to 4.1.7

    ステージング環境で 4.1.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

maven org.apache.cxf:cxf-rt-rs-security-oauth2
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.1.7"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details