Quick answers
- Is CVE-2026-18353 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-18353 being exploited in the wild.
- How severe is CVE-2026-18353?
- Informational severity, with a CVSS score of 8.8, published 30 July 2026.
- Which products and versions are affected?
- Eclipse Foundation CSI - PIA 0.4.0 to 0.5.0.
- Is there a fix for CVE-2026-18353?
- A patch was published on 2026-07-30. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-18353 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-18353?
- Check whether you run Eclipse Foundation CSI - PIA at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An unauthenticated SSRF vulnerability exists in the `POST /v1/upload/sbom` endpoint of Eclipse CSI - PIA. The application validates the `iss` (issuer) claim of a Bearer JWT against an allowlist using Python's `urlparse`. However, a parsing differential exists between `urlparse` and the `requests`/`urllib3` libraries used for subsequent OIDC discovery. By including a backslash in the authority string (e.g., `https://attacker-host\@ci.eclipse.org/`), an attacker can bypass the allowlist check while forcing the server to perform OIDC discovery and JWKS retrieval from an arbitrary host, port, and scheme. This is a blind SSRF that can be used for internal port scanning or reaching cloud metadata endpoints. The issue is fixed in version 0.6.0.
Affected products
- Eclipse Foundation Eclipse CSI - PIA 0.4.0 to 0.5.0
Timeline
- 2026-07-30: advisory
- 2026-07-30: disclosed
- 2026-07-30: patched