---
id: CVE-2026-79650
title: "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 …"
summary: "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 …"
severity: medium
cvss: 6.1
cvssVector: 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N'
cwe:
  - CWE-601
vendor: Apache Software Foundation
product: 'org.apache.cxf:cxf-rt-rs-security-sso-oidc'
affected:
  - 'org.apache.cxf:cxf-rt-rs-security-sso-oidc >= 4.2.0 < 4.2.4'
  - 'org.apache.cxf:cxf-rt-rs-security-sso-oidc >= 4.0.0 < 4.1.9'
  - 'org.apache.cxf:cxf-rt-rs-security-sso-oidc < 3.6.13'
published: '2026-10-09'
updated: '2026-10-15'
sourceUpdated: '2026-10-15T17:17:28.753'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-79650'
references:
  - url: 'https://lists.apache.org/thread.html/xj0x1r617j1z8jtyypngvwhckb3o205h'
    label: security@apache.org
  - url: 'http://www.openwall.com/lists/oss-security/2026/10/09/7'
    label: af854a3a-2127-422b-91ae-364da2661108
tags:
  - nvd
  - cve.org
ssvc:
  exploitation: none
  automatable: 'no'
  technicalImpact: partial
  timestamp: '2026-10-15T16:19:27.910552Z'
epss: 0.00361
epssPercentile: 0.2976
ingestedAt: '2026-10-09T12:53:29.301Z'
---

## Overview

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.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.