Skip to main content

Eclipse CSI PIA EUVDEUVD-2026-41259

| CVE-2026-14336 HIGH
Server-Side Request Forgery (SSRF) (CWE-918)
2026-07-02 eclipse
8.2
CVSS 3.1 · Vendor: eclipse
Share

Severity by source

Vendor (eclipse) PRIMARY
8.2 HIGH
AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N
vuln.today AI
8.2 HIGH

Unauthenticated network endpoint (PR:N/AV:N) exploited via a trivial string trick (AC:L); accepting attacker-signed JWTs breaks authentication (I:H) and SSRF exposes internal responses (C:L), with no availability impact.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (eclipse).

CVSS VectorVendor: eclipse

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N
Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
High
Availability
None

Lifecycle Timeline

2
Analysis Generated
Jul 02, 2026 - 10:15 vuln.today
CVE Published
Jul 02, 2026 - 08:29 cve.org
HIGH 8.2

DescriptionCVE.org

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.

AnalysisAI

Server-side request forgery and OIDC token forgery in Eclipse CSI PIA lets an unauthenticated attacker abuse a flawed Jenkins issuer allowlist (a bare startswith('https://ci.eclipse.org') check in is_issuer_known, pia/models.py:139) to redirect OIDC discovery and JWKS fetches to an attacker-controlled host. By posting a crafted issuer such as https://ci.eclipse.org@evil.host or https://ci.eclipse.org.evil.host to POST /v1/upload/sbom, an attacker forces PIA to make outbound requests to arbitrary hosts and to accept a JWT signed with the attacker's own key, effectively bypassing token verification. …

Unlock full vulnerability intelligence

  • Risk assessment & exploitation conditions
  • Attack chain visualization
  • Remediation with exact patch versions
  • Threat intelligence from 22 sources
  • Personal watchlist & email alerts

Free forever · No credit card required

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata

Access
Reach unauthenticated /v1/upload/sbom endpoint
Delivery
Submit token with spoofed ci.eclipse.org issuer
Exploit
Bypass prefix allowlist via userinfo/suffix trick
Execution
PIA fetches attacker OIDC discovery and JWKS
Persist
PIA accepts attacker-signed JWT
Impact
Forged authentication and outbound SSRF

Vulnerability AssessmentAI

Exploitation Exploitation requires network reachability to PIA's unauthenticated POST /v1/upload/sbom endpoint and that PIA use the vulnerable Jenkins OIDC issuer allowlist (the `is_issuer_known` prefix check in pia/models.py:139), which is the shipped/default logic. … Additional conditions and limiting factors are described in the full assessment.
Risk Assessment The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N, score 8.2) is internally consistent with the description: the vulnerable endpoint POST /v1/upload/sbom is explicitly unauthenticated (PR:N), network-reachable (AV:N), needs no user interaction (UI:N), and the exploitation technique is a simple string trick (AC:L). … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in.
Exploit Scenario An unauthenticated attacker sends a crafted SBOM upload to POST /v1/upload/sbom with a token whose issuer is `https://ci.eclipse.org@attacker.example` or `https://ci.eclipse.org.attacker.example`, which passes PIA's prefix allowlist. PIA then fetches OIDC discovery and JWKS documents from the attacker's server and accepts a JWT the attacker signed with their own key, granting forged token acceptance and forcing outbound SSRF requests. …
Remediation No vendor-released patch identified at time of analysis; the provided references point only to the Eclipse GitLab CVE-assignment work item (https://gitlab.eclipse.org/security/cve-assignment/-/work_items/154) and do not name a fixed version, so operators should consult the Eclipse Foundation security team for a patched release before deploying. … Detailed patch versions, workarounds, and compensating controls in full report.

Recommended ActionAI

Within 24 hours: Determine whether Eclipse CSI PIA is deployed in your environment and whether the POST /v1/upload/sbom endpoint is internet-accessible or reachable from untrusted networks. …

Sign in for detailed remediation steps and compensating controls.

Threat intelligence, references, and detailed analysis are available after sign-in.

Share

EUVD-2026-41259 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy