SSRF (Server-Side Request Forgery) in PIA (CVE-2026-18353)
Summary
SSRF in PIA (CVE-2026-18353). Risk of unauthorized operations or information disclosure. Exploitable via POST /v1/upload/sbom.
Original description
The description as published by the source.
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.
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-18353 has been found in PIA.
Attackers can target a specific entry point like POST /v1/upload/sbom over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "PIA CVE-2026-18353" on the vendor's site.
CVE-2026-18353 (PIA) — CWE-918
Attack surface: POST /v1/upload/sbom / iss / urlparse / requests
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.
SSRF (CWE-918) exists in PIA. Attackers reach the vulnerable code path via POST /v1/upload/sbom.
Check the vendor advisory for the affected versions of PIA. Attack surface: POST /v1/upload/sbom / iss / urlparse / requests.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual POST /v1/upload/sbom requests with malformed payloads or SQL meta-characters. Run grep -r 'PIA' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'PIA' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
PIAを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'POST /v1/upload/sbom' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /v1/upload/sbomへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Post-deployment verification verify
Replay attack against POST /v1/upload/sbom on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com