CVE-2026-24408 json
sigstore has CSRF possibility in OIDC authentication during signing
published 9mo ago modified 4mo ago also GHSA-hm8f-75xx-w2vr , PYSEC-2026-1924 , EUVD-2026-4729
- cvss
- 0.0
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 7%
- public exploits
- 0
- none known
Summary
sigstore-python is a Python tool for generating and verifying Sigstore signatures. Prior to version 4.2.0, the sigstore-python OAuth authentication flow is susceptible to Cross-Site Request Forgery. `_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. Version 4.2.0 contains a patch for the issue.
Patch / fix
- pypi sigstore 4.2.0
- linuxfoundation sigstore-python 4.2.0
- python-sigstore openSUSE Tumbleweed 4.2.0-1.1
opensuse advisories openSUSE-SU-2026:10104-1
Is CVE-2026-24408 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 9mo ago
Exploit prediction
0.18% chance of exploitation in the next 30 days, higher than 7% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 0.0 | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:N |
| NVD | 3.1 | 5.0 | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L |
| OSV | 3.1 | 0.0 | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:N |
| GitHub | 3.1 | 0.0 | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | sigstore | <4.2.0 |
4.2.0 |
Affected products
- sigstore sigstore-python
Classification
- Weakness
-
- CWE-352 Cross-Site Request Forgery
References
-
github.com
/sigstore/sigstore-python/commit/5e77497fe8f0b202bdd118949074ec2f20da69aa
web, patch
-
github.com
/sigstore/sigstore-python/security/advisories/GHSA-hm8f-75xx-w2vr
web, vendor-advisory
-
github.com
/sigstore/sigstore-python/releases/tag/v4.2.0
web, product, release-notes
-
nvd.nist.gov
/vuln/detail/CVE-2026-24408
advisory
-
github.com
/sigstore/sigstore-python
package
-
pypi.org
/project/sigstore
package
-
github.com
/advisories/GHSA-hm8f-75xx-w2vr
advisory
Sources
- CVE List CVE-2026-24408
- GitHub Advisory GHSA-hm8f-75xx-w2vr
- NVD CVE-2026-24408
- OSV PYSEC-2026-1924
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.