CVE-2026-18353: CWE-918 Server-Side Request Forgery (SSRF) in Eclipse Foundation Eclipse CSI - PIA
CVE-2026-18353 is a high-severity server-side request forgery (SSRF) vulnerability in Eclipse Foundation's Eclipse CSI - PIA version 0.4.0. The vulnerability arises from improper validation of the unverified 'iss' claim in a JWT token at the /v1/upload/sbom endpoint. Due to inconsistent parsing of URLs containing backslashes by Python's urlparse and the requests library, an attacker can bypass issuer allowlist checks and cause the server to make arbitrary network requests to attacker-controlled hosts.
AI Analysis
Technical Summary
The vulnerability in Eclipse CSI - PIA (version 0.4.0) involves the /v1/upload/sbom endpoint accepting a Bearer JWT token and checking its unverified 'iss' claim against an issuer allowlist using Python's urlparse. However, urlparse and the requests/urllib3 libraries parse authority strings containing backslashes differently. This discrepancy allows an attacker to craft an issuer string that passes the allowlist check but causes the requests library to connect to an arbitrary host, port, and scheme controlled by the attacker. This leads to server-side request forgery (CWE-918), enabling the attacker to make the server perform unintended network requests during OIDC discovery and JWKS retrieval.
Potential Impact
An attacker can exploit this vulnerability to make the vulnerable server initiate network connections to arbitrary hosts, potentially leading to unauthorized internal network access, information disclosure, or interaction with internal services. The vulnerability does not require authentication or user interaction and has a high impact on confidentiality and integrity due to the ability to influence server-side requests.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, avoid exposing the vulnerable endpoint to untrusted users or networks. Monitor for unusual outbound network activity from the affected service. Do not rely solely on issuer allowlist checks that use urlparse for validation of JWT claims containing URLs with backslashes.
CVE-2026-18353: CWE-918 Server-Side Request Forgery (SSRF) in Eclipse Foundation Eclipse CSI - PIA
Description
CVE-2026-18353 is a high-severity server-side request forgery (SSRF) vulnerability in Eclipse Foundation's Eclipse CSI - PIA version 0.4.0. The vulnerability arises from improper validation of the unverified 'iss' claim in a JWT token at the /v1/upload/sbom endpoint. Due to inconsistent parsing of URLs containing backslashes by Python's urlparse and the requests library, an attacker can bypass issuer allowlist checks and cause the server to make arbitrary network requests to attacker-controlled hosts.
CVSS v4.0
Score 8.8high
Affected software
Eclipse Foundation
Eclipse CSI - PIA
pkg:github/Eclipse CSI - PIARun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in Eclipse CSI - PIA (version 0.4.0) involves the /v1/upload/sbom endpoint accepting a Bearer JWT token and checking its unverified 'iss' claim against an issuer allowlist using Python's urlparse. However, urlparse and the requests/urllib3 libraries parse authority strings containing backslashes differently. This discrepancy allows an attacker to craft an issuer string that passes the allowlist check but causes the requests library to connect to an arbitrary host, port, and scheme controlled by the attacker. This leads to server-side request forgery (CWE-918), enabling the attacker to make the server perform unintended network requests during OIDC discovery and JWKS retrieval.
Potential Impact
An attacker can exploit this vulnerability to make the vulnerable server initiate network connections to arbitrary hosts, potentially leading to unauthorized internal network access, information disclosure, or interaction with internal services. The vulnerability does not require authentication or user interaction and has a high impact on confidentiality and integrity due to the ability to influence server-side requests.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, avoid exposing the vulnerable endpoint to untrusted users or networks. Monitor for unusual outbound network activity from the affected service. Do not rely solely on issuer allowlist checks that use urlparse for validation of JWT claims containing URLs with backslashes.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- eclipse
- Date Reserved
- 2026-07-30T07:10:40.527Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6a6b06679c2644c7f8c3e6d7
Added to database: 07/30/2026, 08:08:07 UTC
Last enriched: 08/06/2026, 17:59:47 UTC
Last updated: 09/13/2026, 22:01:32 UTC
Views: 79
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.