Bug 2509192 (CVE-2026-18353)

Summary: CVE-2026-18353 PIA: python: requests: urllib3: PIA: Unauthenticated Server-Side Request Forgery via OIDC issuer allowlist bypass
Product: [Other] Security Response Reporter: OSIDB Bzimport <bzimport>
Component: vulnerabilityAssignee: Product Security <prodsec-ir-bot>
Status: NEW --- QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: unspecifiedKeywords: Security
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
A flaw was found in PIA. An unauthenticated attacker can exploit a Server-Side Request Forgery (SSRF) vulnerability by crafting a malicious OpenID Connect (OIDC) issuer URL. This bypasses an internal allowlist due to inconsistent URL parsing between Python's `urlparse` and the `requests`/`urllib3` libraries. Successful exploitation allows the attacker to force the application to connect to arbitrary external hosts, potentially leading to information disclosure or further attacks.
 Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description OSIDB Bzimport 2026-07-30 08:01:29 UTC 
PIA's `POST /v1/upload/sbom` endpoint accepts a Bearer JWT and checks its **unverified** `iss` claim against an issuer allowlist using Python's `urlparse` before performing OIDC discovery with `requests`. Because `urlparse` and `requests`/`urllib3` parse an authority string containing a backslash (e.g. `https://attacker-host\@ci.eclipse.org/`) into *different* hostnames, an attacker can craft an issuer that passes the allowlist check yet drives `requests` — and subsequently `urllib.request.urlopen` for JWKS retrieval — to connect to an arbitrary attacker-chosen host, port, and scheme.