{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-18353 exists.","fix":"No fix has been published for CVE-2026-18353 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-18353 is a high-severity server-side request forgery vulnerability in Eclipse CSI - PIA, published on 30 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-18353 and fix it if it is affected.\n\nWhat it is: CVE-2026-18353 is a high-severity server-side request forgery vulnerability in Eclipse CSI - PIA, published on 30 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-18353 exists.\n\nAffected product: Eclipse CSI - PIA. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-18353/ (Markdown: https://insights.sbomify.com/CVE-2026-18353/index.md)","id":"CVE-2026-18353","markdown":"https://insights.sbomify.com/CVE-2026-18353/index.md","name":"CVE-2026-18353","record":{"aliases":["GHSA-v249-9xjm-qhgf"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Eclipse PIA","requires_auth":"none","summary":"An unauthenticated attacker can bypass issuer allowlists via URL parsing discrepancies to perform Server-Side Request Forgery against arbitrary hosts.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"eclipse","cpe":[],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Unauthenticated SSRF in PIA via OIDC issuer allowlist bypass","id":"CVE-2026-18353","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in Red Hat Directory Server 11.5 E4S for RHEL 8","id":"CVE-2026-18355"},"packages":[],"prev":{"headline":"User Access Manager \u003c= 2.3.15 - Unauthenticated Arbitrary File Read via 'uamgetfile' Parameter","id":"CVE-2026-18352"},"products":["Eclipse CSI - PIA"],"published":"2026-07-30","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-30","vendors":["Eclipse Foundation"]},"summary":"An unauthenticated attacker can bypass issuer allowlists via URL parsing discrepancies to perform Server-Side Request Forgery against arbitrary hosts.","url":"https://insights.sbomify.com/CVE-2026-18353/"}