# CVE-2026-14336: Server-side request forgery in Eclipse CSI - PIA

> An attacker can bypass OIDC issuer validation via prefix matching to force server-side requests and forge authentication tokens.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Jul 2026
- **Updated:** 2 Jul 2026

## What is CVE-2026-14336?

CVE-2026-14336 is a high-severity server-side request forgery vulnerability in Eclipse CSI - PIA, published on 2 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

PIA's OIDC issuer allowlist for Jenkins tokens uses a bare string-prefix check (issuer.startswith(' https://ci.eclipse.org ') in is_issuer_known, pia/models.py:139) instead of validating the issuer as a properly host-bounded URL. An attacker can craft an issuer such as  https://ci.eclipse.org@evil.host  (userinfo trick) or  https://ci.eclipse.org.evil.host  (suffix trick) that satisfies the prefix check while pointing the OIDC discovery and JWKS fetches at a server the attacker controls. An unauthenticated caller of POST /v1/upload/sbom can use this to force PIA to make outbound HTTP(S) requests to an arbitrary attacker-chosen host, and to have oidc.verify_token accept a JWT signed with the attacker's own key.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-14336?


## How do I fix CVE-2026-14336?

No fix has been published for CVE-2026-14336 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-14336 being exploited?

There is no known exploitation of CVE-2026-14336 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-14336 and fix it if it is affected.

What it is: CVE-2026-14336 is a high-severity server-side request forgery vulnerability in Eclipse CSI - PIA, published on 2 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-14336 in the wild and no public exploit code.

Affected product: Eclipse CSI - PIA. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-14336/ (Markdown: https://insights.sbomify.com/CVE-2026-14336/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-14336
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-14336
- OSV: https://osv.dev/vulnerability/CVE-2026-14336

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-14336/
Summaries are generated and may contain mistakes; the official description above is the record.