Skip to content
NewA calmer, faster ZeroHour
Vulnerability3 · 1 read

CVE-2026-79650

Open Redirect in Apache CXF OIDC Relying Party

CVSS 3.1
6.1 medium
EPSS
—
Published
·
Modified
Analyze CVE-2026-79650 with Vani AIImpact, affected versions, exploitation status, mitigations and detection

Apache CXF’s OpenID Connect relying-party component can redirect a user to an attacker-controlled URL after successful authentication. Attacker-controlled state parameters are preserved and later used as redirect targets without checking that the final decoded URI belongs to the relying party’s origin; both directly encoded and double-encoded external URLs can trigger the issue depending on the validation path. An attacker can abuse this open redirect (CWE-601) to send authenticated users to a malicious site for phishing or token theft. Any deployment using the vulnerable OIDC RP component is affected; the vendor fixes are 4.2.4, 4.1.9, and 3.6.13. There is no known public proof of concept, CVSS is not yet scored, and the issue is not on the CISA KEV list.

What to do: Upgrade Apache CXF to 4.2.4, 4.1.9, or 3.6.13 on the release line you use. Until then, treat post-authentication redirects from the OIDC relying party as untrusted and confirm the final decoded target stays on the RP origin, especially where login is reachable by untrusted users.

ProductAffected
Apache Software Foundation Apache CXF (OIDC relying-party component)Fixed in 4.2.4, 4.1.9, and 3.6.13; earlier releases in those lines are affected (exact lower bounds not stated)
Estimated exposure
No basis for an estimate.

Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.

Description · NVD

Apache CXF’s OIDC relying-party component could redirect users to an attacker-controlled URL after successful authentication. The issue occurs because attacker-controlled state parameters are preserved and later used as redirect targets without validating that the final decoded URI belongs to the RP’s origin. Both directly encoded and double-encoded external URLs can trigger the issue, depending on which validation path is used. Users are recommended to upgrade to versions 4.2.4 or 4.1.9 or 3.6.13, which fix this issue.

Vendors
apache
Products
cxf
Weakness
CWE-601
Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

In the news

1 story