CVE-2026-18353

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 85% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
71(Attend)
EG Risk 71/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity88% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
15%
KEV
Not listed

Published

July 30, 2026

Last Modified

July 30, 2026

Advisory Details (1)

Auto-updated Jul 30, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

Unauthenticated SSRF in PIA via OIDC issuer allowlist bypass · Advisory · eclipse-csi/pia · GitHub

https://github.com/eclipse-csi/pia/security/advisories/GHSA-v249-9xjm-qhgf

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 52× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-30 01:22 UTCEPSS rescore
  2. 2026-08-29 22:38 UTCEG score recompute
  3. 2026-08-28 21:41 UTCEPSS rescore
  4. 2026-08-26 19:19 UTCEG score recompute
  5. 2026-08-26 14:46 UTCEPSS rescore
  6. 2026-08-25 19:02 UTCEG score recompute
  7. 2026-08-25 13:48 UTCEPSS rescore
  8. 2026-08-24 19:31 UTCEG score recompute
  9. 2026-08-23 08:15 UTCEG score recompute
  10. 2026-08-23 00:19 UTCEPSS rescore
  11. 2026-08-22 08:45 UTCEG score recompute
  12. 2026-08-21 23:49 UTCEPSS rescore
  13. 2026-08-21 09:14 UTCEG score recompute
  14. 2026-08-20 22:55 UTCEPSS rescore
  15. 2026-08-19 21:59 UTCEG score recompute
  16. 2026-08-19 17:03 UTCEPSS rescore
  17. 2026-08-18 22:29 UTCEG score recompute
  18. 2026-08-18 13:48 UTCEPSS rescore
  19. 2026-08-17 23:00 UTCEG score recompute
  20. 2026-08-17 13:47 UTCEPSS rescore
  21. 2026-08-16 23:29 UTCEG score recompute
  22. 2026-08-16 14:56 UTCEPSS rescore
  23. 2026-08-16 11:43 UTCEG score recompute
  24. 2026-08-16 02:14 UTCEPSS rescore
  25. 2026-08-15 12:14 UTCEG score recompute
Show 33 more
  1. 2026-08-15 01:30 UTCEPSS rescore
  2. 2026-08-14 00:59 UTCEG score recompute
  3. 2026-08-13 22:00 UTCEPSS rescore
  4. 2026-08-13 01:30 UTCEG score recompute
  5. 2026-08-12 13:50 UTCEPSS rescore
  6. 2026-08-11 14:16 UTCEG score recompute
  7. 2026-08-11 13:42 UTCEPSS rescore
  8. 2026-08-11 02:32 UTCEG score recompute
  9. 2026-08-11 00:00 UTCEPSS rescore
  10. 2026-08-09 15:17 UTCEG score recompute
  11. 2026-08-09 13:46 UTCEPSS rescore
  12. 2026-08-09 03:33 UTCEG score recompute
  13. 2026-08-08 16:37 UTCEPSS rescore
  14. 2026-08-08 04:03 UTCEG score recompute
  15. 2026-08-06 16:48 UTCEG score recompute
  16. 2026-08-06 13:46 UTCEPSS rescore
  17. 2026-08-06 05:03 UTCEG score recompute
  18. 2026-08-05 19:17 UTCEPSS rescore
  19. 2026-08-04 17:34 UTCEG score recompute
  20. 2026-08-04 15:10 UTCEPSS rescore
  21. 2026-08-04 10:38 UTCEPSS rescore
  22. 2026-08-03 18:05 UTCEG score recompute
  23. 2026-08-03 10:35 UTCEPSS rescore
  24. 2026-08-02 06:28 UTCEG score recompute
  25. 2026-08-02 02:26 UTCEPSS rescore
  26. 2026-08-01 06:57 UTCEG score recompute
  27. 2026-08-01 04:15 UTCEPSS rescore
  28. 2026-07-30 19:31 UTCEG score recompute
  29. 2026-07-30 14:30 UTCEG score recompute
  30. 2026-07-30 13:21 UTCEG score recompute
  31. 2026-07-30 08:30 UTCEG score recompute
  32. 2026-07-30 08:03 UTCEG score recompute
  33. 2026-07-30 08:01 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-18353?
CVE-2026-18353 is a high vulnerability published on July 30, 2026. 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.…
When was CVE-2026-18353 disclosed?
CVE-2026-18353 was first published in the National Vulnerability Database on July 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-18353 actively exploited?
CVE-2026-18353 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 85.1% of all scored CVEs.
What is the CVSS score of CVE-2026-18353?
CVE-2026-18353 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-18353?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-18353, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-18353

Explore →

Is Your Infrastructure Affected by CVE-2026-18353?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs