sigstore/sigstore-python · Security
sigstore CSRF possibility in OIDC authentication during signing
- GHSA ID
- GHSA-hm8f-75xx-w2vr
- CVE ID
- CVE-2026-24408
- Severity
- low
- Published
- Updated
- CVSS
- 0 · CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:N
- CVSS v3
- 0 · CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:N
Description
Summary
The sigstore-python OAuth authentication flow is susceptible to Cross-Site Request Forgery.
Details
_OAuthSession creates a unique "state" and sends it as a parameter in the authentication request but the "state" in the server response seems not not be cross-checked with this value.
Fix should be fairly trivial.
Impact
This should be low impact: A man-in-the middle attacker could trick a sigstore-python user into signing something with an identity controlled by the attacker (by returning the response to an authentication request they created). This would be quite confusing but not dangerous.
CWEs
- CWE-352 · Cross-Site Request Forgery (CSRF)
References
- https://github.com/sigstore/sigstore-python/security/advisories/GHSA-hm8f-75xx-w2vr ↗
- https://github.com/sigstore/sigstore-python/commit/5e77497fe8f0b202bdd118949074ec2f20da69aa ↗
- https://github.com/sigstore/sigstore-python/releases/tag/v4.2.0 ↗
- https://nvd.nist.gov/vuln/detail/CVE-2026-24408 ↗
- https://github.com/advisories/GHSA-hm8f-75xx-w2vr ↗