ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-107597

PIA's token verification ( in ) fetches the OIDC discovery document of an allowlisted issuer and then follows the contained in that response without parsing it as a UR…

Published Oct 20, 2026 · catalog updated Oct 20, 2026 · the affected product

Last checked Nov 1, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2026-107597. EPSS is 0.36%. Act only if a listed version of the affected product is installed.

Gaps on this record

  • No plain product name is stored. The page cannot tell you which product to check.
  • No version range is stored. A customer cannot check an installed version against this record.
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Medium5.1
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.36%
Remediation
Advisory link
Affected products
See sources for product scope

PIA's token verification ( in ) fetches the OIDC discovery document of an allowlisted issuer and then follows the contained in that response without parsing it as a URL, comparing it against the approved issuer's origin, or requiring HTTPS — the only check is that the field is non-empty ( ). An approved identity provider — and every registered per-project Jenkins instance under is a separate such party ( ) — can therefore direct PIA to issue a GET request to an arbitrary host and port, including over plaintext , from PIA's own network position. The fetch happens before any signature is verified, as a side effect of an unauthenticated request that is ultimately rejected with 401.

No affected version ranges are stored yet. Use the vendor advisory before you decide this record does not apply.

How to fix CVE-2026-107597

  • No stored fix

    No vendor fix text is stored. Use the linked advisory before you change production.

  • Version check

    No version range is stored, so an installed version cannot be checked on this page.

  • Advisory

    Open the cve_org record and follow its fix.

  • Official advisories

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-107597. EPSS is 0.36%. Act only if a listed version of the affected product is installed.

Which versions are affected?

Affected version ranges are not on this record. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-918: Server-Side Request Forgery (SSRF). EPSS 0.36%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

Jenkins security

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 20, 2026 · NIST NVD

    Detected

    PIA's token verification ( in ) fetches the OIDC discovery document of an allowlisted issuer and then follows the contained in that response without parsing it as a URL, comparing it against the approved issuer's origin, or requiring HTTPS — the only check is that the field is non-empty ( ). An approved identity provider — and every registered per-project Jenkins instance under is a separate such

  2. Oct 20, 2026 · NIST NVD

    Updated

    PIA's token verification ( in ) fetches the OIDC discovery document of an allowlisted issuer and then follows the contained in that response without parsing it as a URL, comparing it against the approved issuer's origin, or requiring HTTPS — the only check is that the field is non-empty ( ). An approved identity provider — and every registered per-project Jenkins instance under is a separate such

  3. Oct 20, 2026 · NIST NVD

    Updated

    PIA's token verification ( in ) fetches the OIDC discovery document of an allowlisted issuer and then follows the contained in that response without parsing it as a URL, comparing it against the approved issuer's origin, or requiring HTTPS — the only check is that the field is non-empty ( ). An approved identity provider — and every registered per-project Jenkins instance under is a separate such

Sources

  • CVE.orgVulnerability recordCVE-2026-107597

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-107597

    30-day exploitation probability 0.36%

    first.org
  • NIST NVDVulnerability recordCVE-2026-107597

    PIA's token verification ( in ) fetches the OIDC discovery document of an allowlisted issuer and then follows the contained in that response without parsing it as a URL, comparing it against the approved issuer's origin, or requiring HTTPS —

    nvd.nist.gov

References

Freshness

Last verified in this catalog Nov 1, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • FIRST EPSSOct 23, 2026
  • CVE.orgOct 21, 2026
  • NIST NVDOct 21, 2026
CVE-2026-107597: PIA's token verificatio… CVSS 5.1 · ZeroDay Findings