sigstore
A tool for signing Python package distributions
View on Github
Activity
- Latest release
- 1mo ago
- Total releases
- 66
- Cadence
- ~19 days
- Last 12 months
- 8
Reach
- Stars
- —
Details
- License
- Apache-2.0
- First release
- Apr 28, 2022
| Version | Released | |
|---|---|---|
4.5.0
minor
| ||
4.4.0
minor
| ||
4.3.0
minor
| ||
3.6.7
patch
1 CVE
CVE-2026-24408
PYSEC-2026-1924
GHSA-hm8f-75xx-w2vr
Jul 07, 2026
sigstore CSRF possibility in OIDC authentication during signing
0.0
/ 10
None
Network
High
None
Required
Unchanged
None
None
None
SummaryThe sigstore-python OAuth authentication flow is susceptible to Cross-Site Request Forgery. Details
Fix should be fairly trivial. ImpactThis 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. Affected versions
0.0.1rc1
0.0.1rc2
0.0.1rc3
0.1.0
0.10.0
0.2.0
0.3.1
0.4.0
0.4.1
0.4.2
0.5.0
0.5.1
+ 50 more Show less
0.5.1rc1
0.5.1rc2
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.8.3
0.9.0
1.0.0
1.0.0rc1
1.1.0
1.1.1
1.1.1rc1
1.1.2
1.1.2rc1
2.0.0
2.0.0rc1
2.0.0rc2
2.0.0rc3
2.0.1
2.1.0
2.1.2
2.1.3
2.1.5
3.0.0
3.0.0rc1
3.0.0rc2
3.1.0
3.2.0
3.3.0
3.4.0
3.5.0
3.5.1
3.5.3
3.5.6
3.6.0
3.6.1
3.6.2
3.6.3
3.6.4
3.6.5
3.6.6
3.6.7
4.0.0
4.1.0
Fixed in
4.2.0
References
Updated Jul 07, 2026 · Source: OSV.dev | ||
4.2.0
minor
| ||
3.5.6
patch
2 CVEs
CVE-2026-24408
PYSEC-2026-1924
GHSA-hm8f-75xx-w2vr
Jul 07, 2026
sigstore CSRF possibility in OIDC authentication during signing
0.0
/ 10
None
Network
High
None
Required
Unchanged
None
None
None
SummaryThe sigstore-python OAuth authentication flow is susceptible to Cross-Site Request Forgery. Details
Fix should be fairly trivial. ImpactThis 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. Affected versions
0.0.1rc1
0.0.1rc2
0.0.1rc3
0.1.0
0.10.0
0.2.0
0.3.1
0.4.0
0.4.1
0.4.2
0.5.0
0.5.1
+ 50 more Show less
0.5.1rc1
0.5.1rc2
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.8.3
0.9.0
1.0.0
1.0.0rc1
1.1.0
1.1.1
1.1.1rc1
1.1.2
1.1.2rc1
2.0.0
2.0.0rc1
2.0.0rc2
2.0.0rc3
2.0.1
2.1.0
2.1.2
2.1.3
2.1.5
3.0.0
3.0.0rc1
3.0.0rc2
3.1.0
3.2.0
3.3.0
3.4.0
3.5.0
3.5.1
3.5.3
3.5.6
3.6.0
3.6.1
3.6.2
3.6.3
3.6.4
3.6.5
3.6.6
3.6.7
4.0.0
4.1.0
Fixed in
4.2.0
References
Updated Jul 07, 2026 · Source: OSV.dev
CVE-2024-55655
PYSEC-2026-1923
GHSA-hhfg-fwrw-87w7
Jul 07, 2026
sigstore has insufficient validation of integration timestamp during verification
Medium
Network
Low
None
None
SummaryVersions of sigstore-python newer than 2.0.0 but prior to 3.6.0 perform insufficient validation of the "integration time" present in "v2" and "v3" bundles during the verification flow: the "integration time" is verified if a source of signed time (such as an inclusion promise) is present, but is otherwise trusted if no source of signed time is present. This does not affect "v1" bundles, as the "v1" bundle format always requires an inclusion promise. DetailsSigstore uses signed time to support verification of signatures made against short-lived signing keys. ImpactThe impact and severity of this weakness is low, as Sigstore contains multiple other enforcing components that prevent an attacker who modifies the integration timestamp within a bundle from impersonating a valid signature. In particular, an attacker who modifies the integration timestamp can induce a Denial of Service, but in no different manner than already possible with bundle access (e.g. modifying the signature itself such that it fails to verify). Separately, an attacker could upload a new entry to the transparency service, and substitute their new entry's time. However, this would still be rejected at validation time, as the new entry's (valid) signed time would be outside the validity window of the original signing certificate and would nonetheless render the attacker auditable. Affected versions
2.0.0
2.0.1
2.1.0
2.1.2
2.1.3
2.1.5
3.0.0
3.0.0rc1
3.0.0rc2
3.1.0
3.2.0
3.3.0
+ 5 more Show less
3.4.0
3.5.0
3.5.1
3.5.3
3.5.6
Fixed in
3.6.0
References
Updated Jul 07, 2026 · Source: OSV.dev | ||
4.1.0
minor
1 CVE
CVE-2026-24408
PYSEC-2026-1924
GHSA-hm8f-75xx-w2vr
Jul 07, 2026
sigstore CSRF possibility in OIDC authentication during signing
0.0
/ 10
None
Network
High
None
Required
Unchanged
None
None
None
SummaryThe sigstore-python OAuth authentication flow is susceptible to Cross-Site Request Forgery. Details
Fix should be fairly trivial. ImpactThis 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. Affected versions
0.0.1rc1
0.0.1rc2
0.0.1rc3
0.1.0
0.10.0
0.2.0
0.3.1
0.4.0
0.4.1
0.4.2
0.5.0
0.5.1
+ 50 more Show less
0.5.1rc1
0.5.1rc2
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.8.3
0.9.0
1.0.0
1.0.0rc1
1.1.0
1.1.1
1.1.1rc1
1.1.2
1.1.2rc1
2.0.0
2.0.0rc1
2.0.0rc2
2.0.0rc3
2.0.1
2.1.0
2.1.2
2.1.3
2.1.5
3.0.0
3.0.0rc1
3.0.0rc2
3.1.0
3.2.0
3.3.0
3.4.0
3.5.0
3.5.1
3.5.3
3.5.6
3.6.0
3.6.1
3.6.2
3.6.3
3.6.4
3.6.5
3.6.6
3.6.7
4.0.0
4.1.0
Fixed in
4.2.0
References
Updated Jul 07, 2026 · Source: OSV.dev | ||
3.6.6
patch
1 CVE
CVE-2026-24408
PYSEC-2026-1924
GHSA-hm8f-75xx-w2vr
Jul 07, 2026
sigstore CSRF possibility in OIDC authentication during signing
0.0
/ 10
None
Network
High
None
Required
Unchanged
None
None
None
SummaryThe sigstore-python OAuth authentication flow is susceptible to Cross-Site Request Forgery. Details
Fix should be fairly trivial. ImpactThis 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. Affected versions
0.0.1rc1
0.0.1rc2
0.0.1rc3
0.1.0
0.10.0
0.2.0
0.3.1
0.4.0
0.4.1
0.4.2
0.5.0
0.5.1
+ 50 more Show less
0.5.1rc1
0.5.1rc2
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.8.3
0.9.0
1.0.0
1.0.0rc1
1.1.0
1.1.1
1.1.1rc1
1.1.2
1.1.2rc1
2.0.0
2.0.0rc1
2.0.0rc2
2.0.0rc3
2.0.1
2.1.0
2.1.2
2.1.3
2.1.5
3.0.0
3.0.0rc1
3.0.0rc2
3.1.0
3.2.0
3.3.0
3.4.0
3.5.0
3.5.1
3.5.3
3.5.6
3.6.0
3.6.1
3.6.2
3.6.3
3.6.4
3.6.5
3.6.6
3.6.7
4.0.0
4.1.0
Fixed in
4.2.0
References
Updated Jul 07, 2026 · Source: OSV.dev | ||
4.0.0
major
1 CVE
CVE-2026-24408
PYSEC-2026-1924
GHSA-hm8f-75xx-w2vr
Jul 07, 2026
sigstore CSRF possibility in OIDC authentication during signing
0.0
/ 10
None
Network
High
None
Required
Unchanged
None
None
None
SummaryThe sigstore-python OAuth authentication flow is susceptible to Cross-Site Request Forgery. Details
Fix should be fairly trivial. ImpactThis 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. Affected versions
0.0.1rc1
0.0.1rc2
0.0.1rc3
0.1.0
0.10.0
0.2.0
0.3.1
0.4.0
0.4.1
0.4.2
0.5.0
0.5.1
+ 50 more Show less
0.5.1rc1
0.5.1rc2
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.8.3
0.9.0
1.0.0
1.0.0rc1
1.1.0
1.1.1
1.1.1rc1
1.1.2
1.1.2rc1
2.0.0
2.0.0rc1
2.0.0rc2
2.0.0rc3
2.0.1
2.1.0
2.1.2
2.1.3
2.1.5
3.0.0
3.0.0rc1
3.0.0rc2
3.1.0
3.2.0
3.3.0
3.4.0
3.5.0
3.5.1
3.5.3
3.5.6
3.6.0
3.6.1
3.6.2
3.6.3
3.6.4
3.6.5
3.6.6
3.6.7
4.0.0
4.1.0
Fixed in
4.2.0
References
Updated Jul 07, 2026 · Source: OSV.dev | ||
3.6.5
patch
1 CVE
CVE-2026-24408
PYSEC-2026-1924
GHSA-hm8f-75xx-w2vr
Jul 07, 2026
sigstore CSRF possibility in OIDC authentication during signing
0.0
/ 10
None
Network
High
None
Required
Unchanged
None
None
None
SummaryThe sigstore-python OAuth authentication flow is susceptible to Cross-Site Request Forgery. Details
Fix should be fairly trivial. ImpactThis 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. Affected versions
0.0.1rc1
0.0.1rc2
0.0.1rc3
0.1.0
0.10.0
0.2.0
0.3.1
0.4.0
0.4.1
0.4.2
0.5.0
0.5.1
+ 50 more Show less
0.5.1rc1
0.5.1rc2
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.8.3
0.9.0
1.0.0
1.0.0rc1
1.1.0
1.1.1
1.1.1rc1
1.1.2
1.1.2rc1
2.0.0
2.0.0rc1
2.0.0rc2
2.0.0rc3
2.0.1
2.1.0
2.1.2
2.1.3
2.1.5
3.0.0
3.0.0rc1
3.0.0rc2
3.1.0
3.2.0
3.3.0
3.4.0
3.5.0
3.5.1
3.5.3
3.5.6
3.6.0
3.6.1
3.6.2
3.6.3
3.6.4
3.6.5
3.6.6
3.6.7
4.0.0
4.1.0
Fixed in
4.2.0
References
Updated Jul 07, 2026 · Source: OSV.dev | ||
3.6.4
patch
1 CVE
CVE-2026-24408
PYSEC-2026-1924
GHSA-hm8f-75xx-w2vr
Jul 07, 2026
sigstore CSRF possibility in OIDC authentication during signing
0.0
/ 10
None
Network
High
None
Required
Unchanged
None
None
None
SummaryThe sigstore-python OAuth authentication flow is susceptible to Cross-Site Request Forgery. Details
Fix should be fairly trivial. ImpactThis 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. Affected versions
0.0.1rc1
0.0.1rc2
0.0.1rc3
0.1.0
0.10.0
0.2.0
0.3.1
0.4.0
0.4.1
0.4.2
0.5.0
0.5.1
+ 50 more Show less
0.5.1rc1
0.5.1rc2
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.8.3
0.9.0
1.0.0
1.0.0rc1
1.1.0
1.1.1
1.1.1rc1
1.1.2
1.1.2rc1
2.0.0
2.0.0rc1
2.0.0rc2
2.0.0rc3
2.0.1
2.1.0
2.1.2
2.1.3
2.1.5
3.0.0
3.0.0rc1
3.0.0rc2
3.1.0
3.2.0
3.3.0
3.4.0
3.5.0
3.5.1
3.5.3
3.5.6
3.6.0
3.6.1
3.6.2
3.6.3
3.6.4
3.6.5
3.6.6
3.6.7
4.0.0
4.1.0
Fixed in
4.2.0
References
Updated Jul 07, 2026 · Source: OSV.dev | ||
3.6.3
patch
1 CVE
CVE-2026-24408
PYSEC-2026-1924
GHSA-hm8f-75xx-w2vr
Jul 07, 2026
sigstore CSRF possibility in OIDC authentication during signing
0.0
/ 10
None
Network
High
None
Required
Unchanged
None
None
None
SummaryThe sigstore-python OAuth authentication flow is susceptible to Cross-Site Request Forgery. Details
Fix should be fairly trivial. ImpactThis 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. Affected versions
0.0.1rc1
0.0.1rc2
0.0.1rc3
0.1.0
0.10.0
0.2.0
0.3.1
0.4.0
0.4.1
0.4.2
0.5.0
0.5.1
+ 50 more Show less
0.5.1rc1
0.5.1rc2
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.8.3
0.9.0
1.0.0
1.0.0rc1
1.1.0
1.1.1
1.1.1rc1
1.1.2
1.1.2rc1
2.0.0
2.0.0rc1
2.0.0rc2
2.0.0rc3
2.0.1
2.1.0
2.1.2
2.1.3
2.1.5
3.0.0
3.0.0rc1
3.0.0rc2
3.1.0
3.2.0
3.3.0
3.4.0
3.5.0
3.5.1
3.5.3
3.5.6
3.6.0
3.6.1
3.6.2
3.6.3
3.6.4
3.6.5
3.6.6
3.6.7
4.0.0
4.1.0
Fixed in
4.2.0
References
Updated Jul 07, 2026 · Source: OSV.dev | ||
3.6.2
patch
1 CVE
CVE-2026-24408
PYSEC-2026-1924
GHSA-hm8f-75xx-w2vr
Jul 07, 2026
sigstore CSRF possibility in OIDC authentication during signing
0.0
/ 10
None
Network
High
None
Required
Unchanged
None
None
None
SummaryThe sigstore-python OAuth authentication flow is susceptible to Cross-Site Request Forgery. Details
Fix should be fairly trivial. ImpactThis 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. Affected versions
0.0.1rc1
0.0.1rc2
0.0.1rc3
0.1.0
0.10.0
0.2.0
0.3.1
0.4.0
0.4.1
0.4.2
0.5.0
0.5.1
+ 50 more Show less
0.5.1rc1
0.5.1rc2
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.8.3
0.9.0
1.0.0
1.0.0rc1
1.1.0
1.1.1
1.1.1rc1
1.1.2
1.1.2rc1
2.0.0
2.0.0rc1
2.0.0rc2
2.0.0rc3
2.0.1
2.1.0
2.1.2
2.1.3
2.1.5
3.0.0
3.0.0rc1
3.0.0rc2
3.1.0
3.2.0
3.3.0
3.4.0
3.5.0
3.5.1
3.5.3
3.5.6
3.6.0
3.6.1
3.6.2
3.6.3
3.6.4
3.6.5
3.6.6
3.6.7
4.0.0
4.1.0
Fixed in
4.2.0
References
Updated Jul 07, 2026 · Source: OSV.dev | ||
3.6.1
patch
1 CVE
CVE-2026-24408
PYSEC-2026-1924
GHSA-hm8f-75xx-w2vr
Jul 07, 2026
sigstore CSRF possibility in OIDC authentication during signing
0.0
/ 10
None
Network
High
None
Required
Unchanged
None
None
None
SummaryThe sigstore-python OAuth authentication flow is susceptible to Cross-Site Request Forgery. Details
Fix should be fairly trivial. ImpactThis 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. Affected versions
0.0.1rc1
0.0.1rc2
0.0.1rc3
0.1.0
0.10.0
0.2.0
0.3.1
0.4.0
0.4.1
0.4.2
0.5.0
0.5.1
+ 50 more Show less
0.5.1rc1
0.5.1rc2
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.8.3
0.9.0
1.0.0
1.0.0rc1
1.1.0
1.1.1
1.1.1rc1
1.1.2
1.1.2rc1
2.0.0
2.0.0rc1
2.0.0rc2
2.0.0rc3
2.0.1
2.1.0
2.1.2
2.1.3
2.1.5
3.0.0
3.0.0rc1
3.0.0rc2
3.1.0
3.2.0
3.3.0
3.4.0
3.5.0
3.5.1
3.5.3
3.5.6
3.6.0
3.6.1
3.6.2
3.6.3
3.6.4
3.6.5
3.6.6
3.6.7
4.0.0
4.1.0
Fixed in
4.2.0
References
Updated Jul 07, 2026 · Source: OSV.dev | ||
3.6.0
minor
1 CVE
CVE-2026-24408
PYSEC-2026-1924
GHSA-hm8f-75xx-w2vr
Jul 07, 2026
sigstore CSRF possibility in OIDC authentication during signing
0.0
/ 10
None
Network
High
None
Required
Unchanged
None
None
None
SummaryThe sigstore-python OAuth authentication flow is susceptible to Cross-Site Request Forgery. Details
Fix should be fairly trivial. ImpactThis 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. Affected versions
0.0.1rc1
0.0.1rc2
0.0.1rc3
0.1.0
0.10.0
0.2.0
0.3.1
0.4.0
0.4.1
0.4.2
0.5.0
0.5.1
+ 50 more Show less
0.5.1rc1
0.5.1rc2
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.8.3
0.9.0
1.0.0
1.0.0rc1
1.1.0
1.1.1
1.1.1rc1
1.1.2
1.1.2rc1
2.0.0
2.0.0rc1
2.0.0rc2
2.0.0rc3
2.0.1
2.1.0
2.1.2
2.1.3
2.1.5
3.0.0
3.0.0rc1
3.0.0rc2
3.1.0
3.2.0
3.3.0
3.4.0
3.5.0
3.5.1
3.5.3
3.5.6
3.6.0
3.6.1
3.6.2
3.6.3
3.6.4
3.6.5
3.6.6
3.6.7
4.0.0
4.1.0
Fixed in
4.2.0
References
Updated Jul 07, 2026 · Source: OSV.dev | ||
3.5.3
patch
2 CVEs
CVE-2026-24408
PYSEC-2026-1924
GHSA-hm8f-75xx-w2vr
Jul 07, 2026
sigstore CSRF possibility in OIDC authentication during signing
0.0
/ 10
None
Network
High
None
Required
Unchanged
None
None
None
SummaryThe sigstore-python OAuth authentication flow is susceptible to Cross-Site Request Forgery. Details
Fix should be fairly trivial. ImpactThis 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. Affected versions
0.0.1rc1
0.0.1rc2
0.0.1rc3
0.1.0
0.10.0
0.2.0
0.3.1
0.4.0
0.4.1
0.4.2
0.5.0
0.5.1
+ 50 more Show less
0.5.1rc1
0.5.1rc2
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.8.3
0.9.0
1.0.0
1.0.0rc1
1.1.0
1.1.1
1.1.1rc1
1.1.2
1.1.2rc1
2.0.0
2.0.0rc1
2.0.0rc2
2.0.0rc3
2.0.1
2.1.0
2.1.2
2.1.3
2.1.5
3.0.0
3.0.0rc1
3.0.0rc2
3.1.0
3.2.0
3.3.0
3.4.0
3.5.0
3.5.1
3.5.3
3.5.6
3.6.0
3.6.1
3.6.2
3.6.3
3.6.4
3.6.5
3.6.6
3.6.7
4.0.0
4.1.0
Fixed in
4.2.0
References
Updated Jul 07, 2026 · Source: OSV.dev
CVE-2024-55655
PYSEC-2026-1923
GHSA-hhfg-fwrw-87w7
Jul 07, 2026
sigstore has insufficient validation of integration timestamp during verification
Medium
Network
Low
None
None
SummaryVersions of sigstore-python newer than 2.0.0 but prior to 3.6.0 perform insufficient validation of the "integration time" present in "v2" and "v3" bundles during the verification flow: the "integration time" is verified if a source of signed time (such as an inclusion promise) is present, but is otherwise trusted if no source of signed time is present. This does not affect "v1" bundles, as the "v1" bundle format always requires an inclusion promise. DetailsSigstore uses signed time to support verification of signatures made against short-lived signing keys. ImpactThe impact and severity of this weakness is low, as Sigstore contains multiple other enforcing components that prevent an attacker who modifies the integration timestamp within a bundle from impersonating a valid signature. In particular, an attacker who modifies the integration timestamp can induce a Denial of Service, but in no different manner than already possible with bundle access (e.g. modifying the signature itself such that it fails to verify). Separately, an attacker could upload a new entry to the transparency service, and substitute their new entry's time. However, this would still be rejected at validation time, as the new entry's (valid) signed time would be outside the validity window of the original signing certificate and would nonetheless render the attacker auditable. Affected versions
2.0.0
2.0.1
2.1.0
2.1.2
2.1.3
2.1.5
3.0.0
3.0.0rc1
3.0.0rc2
3.1.0
3.2.0
3.3.0
+ 5 more Show less
3.4.0
3.5.0
3.5.1
3.5.3
3.5.6
Fixed in
3.6.0
References
Updated Jul 07, 2026 · Source: OSV.dev | ||
3.5.1
patch
2 CVEs
CVE-2026-24408
PYSEC-2026-1924
GHSA-hm8f-75xx-w2vr
Jul 07, 2026
sigstore CSRF possibility in OIDC authentication during signing
0.0
/ 10
None
Network
High
None
Required
Unchanged
None
None
None
SummaryThe sigstore-python OAuth authentication flow is susceptible to Cross-Site Request Forgery. Details
Fix should be fairly trivial. ImpactThis 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. Affected versions
0.0.1rc1
0.0.1rc2
0.0.1rc3
0.1.0
0.10.0
0.2.0
0.3.1
0.4.0
0.4.1
0.4.2
0.5.0
0.5.1
+ 50 more Show less
0.5.1rc1
0.5.1rc2
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.8.3
0.9.0
1.0.0
1.0.0rc1
1.1.0
1.1.1
1.1.1rc1
1.1.2
1.1.2rc1
2.0.0
2.0.0rc1
2.0.0rc2
2.0.0rc3
2.0.1
2.1.0
2.1.2
2.1.3
2.1.5
3.0.0
3.0.0rc1
3.0.0rc2
3.1.0
3.2.0
3.3.0
3.4.0
3.5.0
3.5.1
3.5.3
3.5.6
3.6.0
3.6.1
3.6.2
3.6.3
3.6.4
3.6.5
3.6.6
3.6.7
4.0.0
4.1.0
Fixed in
4.2.0
References
Updated Jul 07, 2026 · Source: OSV.dev
CVE-2024-55655
PYSEC-2026-1923
GHSA-hhfg-fwrw-87w7
Jul 07, 2026
sigstore has insufficient validation of integration timestamp during verification
Medium
Network
Low
None
None
SummaryVersions of sigstore-python newer than 2.0.0 but prior to 3.6.0 perform insufficient validation of the "integration time" present in "v2" and "v3" bundles during the verification flow: the "integration time" is verified if a source of signed time (such as an inclusion promise) is present, but is otherwise trusted if no source of signed time is present. This does not affect "v1" bundles, as the "v1" bundle format always requires an inclusion promise. DetailsSigstore uses signed time to support verification of signatures made against short-lived signing keys. ImpactThe impact and severity of this weakness is low, as Sigstore contains multiple other enforcing components that prevent an attacker who modifies the integration timestamp within a bundle from impersonating a valid signature. In particular, an attacker who modifies the integration timestamp can induce a Denial of Service, but in no different manner than already possible with bundle access (e.g. modifying the signature itself such that it fails to verify). Separately, an attacker could upload a new entry to the transparency service, and substitute their new entry's time. However, this would still be rejected at validation time, as the new entry's (valid) signed time would be outside the validity window of the original signing certificate and would nonetheless render the attacker auditable. Affected versions
2.0.0
2.0.1
2.1.0
2.1.2
2.1.3
2.1.5
3.0.0
3.0.0rc1
3.0.0rc2
3.1.0
3.2.0
3.3.0
+ 5 more Show less
3.4.0
3.5.0
3.5.1
3.5.3
3.5.6
Fixed in
3.6.0
References
Updated Jul 07, 2026 · Source: OSV.dev | ||
3.5.0
minor
2 CVEs
CVE-2026-24408
PYSEC-2026-1924
GHSA-hm8f-75xx-w2vr
Jul 07, 2026
sigstore CSRF possibility in OIDC authentication during signing
0.0
/ 10
None
Network
High
None
Required
Unchanged
None
None
None
SummaryThe sigstore-python OAuth authentication flow is susceptible to Cross-Site Request Forgery. Details
Fix should be fairly trivial. ImpactThis 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. Affected versions
0.0.1rc1
0.0.1rc2
0.0.1rc3
0.1.0
0.10.0
0.2.0
0.3.1
0.4.0
0.4.1
0.4.2
0.5.0
0.5.1
+ 50 more Show less
0.5.1rc1
0.5.1rc2
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.8.3
0.9.0
1.0.0
1.0.0rc1
1.1.0
1.1.1
1.1.1rc1
1.1.2
1.1.2rc1
2.0.0
2.0.0rc1
2.0.0rc2
2.0.0rc3
2.0.1
2.1.0
2.1.2
2.1.3
2.1.5
3.0.0
3.0.0rc1
3.0.0rc2
3.1.0
3.2.0
3.3.0
3.4.0
3.5.0
3.5.1
3.5.3
3.5.6
3.6.0
3.6.1
3.6.2
3.6.3
3.6.4
3.6.5
3.6.6
3.6.7
4.0.0
4.1.0
Fixed in
4.2.0
References
Updated Jul 07, 2026 · Source: OSV.dev
CVE-2024-55655
PYSEC-2026-1923
GHSA-hhfg-fwrw-87w7
Jul 07, 2026
sigstore has insufficient validation of integration timestamp during verification
Medium
Network
Low
None
None
SummaryVersions of sigstore-python newer than 2.0.0 but prior to 3.6.0 perform insufficient validation of the "integration time" present in "v2" and "v3" bundles during the verification flow: the "integration time" is verified if a source of signed time (such as an inclusion promise) is present, but is otherwise trusted if no source of signed time is present. This does not affect "v1" bundles, as the "v1" bundle format always requires an inclusion promise. DetailsSigstore uses signed time to support verification of signatures made against short-lived signing keys. ImpactThe impact and severity of this weakness is low, as Sigstore contains multiple other enforcing components that prevent an attacker who modifies the integration timestamp within a bundle from impersonating a valid signature. In particular, an attacker who modifies the integration timestamp can induce a Denial of Service, but in no different manner than already possible with bundle access (e.g. modifying the signature itself such that it fails to verify). Separately, an attacker could upload a new entry to the transparency service, and substitute their new entry's time. However, this would still be rejected at validation time, as the new entry's (valid) signed time would be outside the validity window of the original signing certificate and would nonetheless render the attacker auditable. Affected versions
2.0.0
2.0.1
2.1.0
2.1.2
2.1.3
2.1.5
3.0.0
3.0.0rc1
3.0.0rc2
3.1.0
3.2.0
3.3.0
+ 5 more Show less
3.4.0
3.5.0
3.5.1
3.5.3
3.5.6
Fixed in
3.6.0
References
Updated Jul 07, 2026 · Source: OSV.dev | ||
3.4.0
minor
2 CVEs
CVE-2026-24408
PYSEC-2026-1924
GHSA-hm8f-75xx-w2vr
Jul 07, 2026
sigstore CSRF possibility in OIDC authentication during signing
0.0
/ 10
None
Network
High
None
Required
Unchanged
None
None
None
SummaryThe sigstore-python OAuth authentication flow is susceptible to Cross-Site Request Forgery. Details
Fix should be fairly trivial. ImpactThis 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. Affected versions
0.0.1rc1
0.0.1rc2
0.0.1rc3
0.1.0
0.10.0
0.2.0
0.3.1
0.4.0
0.4.1
0.4.2
0.5.0
0.5.1
+ 50 more Show less
0.5.1rc1
0.5.1rc2
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.8.3
0.9.0
1.0.0
1.0.0rc1
1.1.0
1.1.1
1.1.1rc1
1.1.2
1.1.2rc1
2.0.0
2.0.0rc1
2.0.0rc2
2.0.0rc3
2.0.1
2.1.0
2.1.2
2.1.3
2.1.5
3.0.0
3.0.0rc1
3.0.0rc2
3.1.0
3.2.0
3.3.0
3.4.0
3.5.0
3.5.1
3.5.3
3.5.6
3.6.0
3.6.1
3.6.2
3.6.3
3.6.4
3.6.5
3.6.6
3.6.7
4.0.0
4.1.0
Fixed in
4.2.0
References
Updated Jul 07, 2026 · Source: OSV.dev
CVE-2024-55655
PYSEC-2026-1923
GHSA-hhfg-fwrw-87w7
Jul 07, 2026
sigstore has insufficient validation of integration timestamp during verification
Medium
Network
Low
None
None
SummaryVersions of sigstore-python newer than 2.0.0 but prior to 3.6.0 perform insufficient validation of the "integration time" present in "v2" and "v3" bundles during the verification flow: the "integration time" is verified if a source of signed time (such as an inclusion promise) is present, but is otherwise trusted if no source of signed time is present. This does not affect "v1" bundles, as the "v1" bundle format always requires an inclusion promise. DetailsSigstore uses signed time to support verification of signatures made against short-lived signing keys. ImpactThe impact and severity of this weakness is low, as Sigstore contains multiple other enforcing components that prevent an attacker who modifies the integration timestamp within a bundle from impersonating a valid signature. In particular, an attacker who modifies the integration timestamp can induce a Denial of Service, but in no different manner than already possible with bundle access (e.g. modifying the signature itself such that it fails to verify). Separately, an attacker could upload a new entry to the transparency service, and substitute their new entry's time. However, this would still be rejected at validation time, as the new entry's (valid) signed time would be outside the validity window of the original signing certificate and would nonetheless render the attacker auditable. Affected versions
2.0.0
2.0.1
2.1.0
2.1.2
2.1.3
2.1.5
3.0.0
3.0.0rc1
3.0.0rc2
3.1.0
3.2.0
3.3.0
+ 5 more Show less
3.4.0
3.5.0
3.5.1
3.5.3
3.5.6
Fixed in
3.6.0
References
Updated Jul 07, 2026 · Source: OSV.dev | ||
3.3.0
minor
2 CVEs
CVE-2026-24408
PYSEC-2026-1924
GHSA-hm8f-75xx-w2vr
Jul 07, 2026
sigstore CSRF possibility in OIDC authentication during signing
0.0
/ 10
None
Network
High
None
Required
Unchanged
None
None
None
SummaryThe sigstore-python OAuth authentication flow is susceptible to Cross-Site Request Forgery. Details
Fix should be fairly trivial. ImpactThis 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. Affected versions
0.0.1rc1
0.0.1rc2
0.0.1rc3
0.1.0
0.10.0
0.2.0
0.3.1
0.4.0
0.4.1
0.4.2
0.5.0
0.5.1
+ 50 more Show less
0.5.1rc1
0.5.1rc2
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.8.3
0.9.0
1.0.0
1.0.0rc1
1.1.0
1.1.1
1.1.1rc1
1.1.2
1.1.2rc1
2.0.0
2.0.0rc1
2.0.0rc2
2.0.0rc3
2.0.1
2.1.0
2.1.2
2.1.3
2.1.5
3.0.0
3.0.0rc1
3.0.0rc2
3.1.0
3.2.0
3.3.0
3.4.0
3.5.0
3.5.1
3.5.3
3.5.6
3.6.0
3.6.1
3.6.2
3.6.3
3.6.4
3.6.5
3.6.6
3.6.7
4.0.0
4.1.0
Fixed in
4.2.0
References
Updated Jul 07, 2026 · Source: OSV.dev
CVE-2024-55655
PYSEC-2026-1923
GHSA-hhfg-fwrw-87w7
Jul 07, 2026
sigstore has insufficient validation of integration timestamp during verification
Medium
Network
Low
None
None
SummaryVersions of sigstore-python newer than 2.0.0 but prior to 3.6.0 perform insufficient validation of the "integration time" present in "v2" and "v3" bundles during the verification flow: the "integration time" is verified if a source of signed time (such as an inclusion promise) is present, but is otherwise trusted if no source of signed time is present. This does not affect "v1" bundles, as the "v1" bundle format always requires an inclusion promise. DetailsSigstore uses signed time to support verification of signatures made against short-lived signing keys. ImpactThe impact and severity of this weakness is low, as Sigstore contains multiple other enforcing components that prevent an attacker who modifies the integration timestamp within a bundle from impersonating a valid signature. In particular, an attacker who modifies the integration timestamp can induce a Denial of Service, but in no different manner than already possible with bundle access (e.g. modifying the signature itself such that it fails to verify). Separately, an attacker could upload a new entry to the transparency service, and substitute their new entry's time. However, this would still be rejected at validation time, as the new entry's (valid) signed time would be outside the validity window of the original signing certificate and would nonetheless render the attacker auditable. Affected versions
2.0.0
2.0.1
2.1.0
2.1.2
2.1.3
2.1.5
3.0.0
3.0.0rc1
3.0.0rc2
3.1.0
3.2.0
3.3.0
+ 5 more Show less
3.4.0
3.5.0
3.5.1
3.5.3
3.5.6
Fixed in
3.6.0
References
Updated Jul 07, 2026 · Source: OSV.dev | ||
3.2.0
minor
2 CVEs
CVE-2026-24408
PYSEC-2026-1924
GHSA-hm8f-75xx-w2vr
Jul 07, 2026
sigstore CSRF possibility in OIDC authentication during signing
0.0
/ 10
None
Network
High
None
Required
Unchanged
None
None
None
SummaryThe sigstore-python OAuth authentication flow is susceptible to Cross-Site Request Forgery. Details
Fix should be fairly trivial. ImpactThis 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. Affected versions
0.0.1rc1
0.0.1rc2
0.0.1rc3
0.1.0
0.10.0
0.2.0
0.3.1
0.4.0
0.4.1
0.4.2
0.5.0
0.5.1
+ 50 more Show less
0.5.1rc1
0.5.1rc2
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.8.3
0.9.0
1.0.0
1.0.0rc1
1.1.0
1.1.1
1.1.1rc1
1.1.2
1.1.2rc1
2.0.0
2.0.0rc1
2.0.0rc2
2.0.0rc3
2.0.1
2.1.0
2.1.2
2.1.3
2.1.5
3.0.0
3.0.0rc1
3.0.0rc2
3.1.0
3.2.0
3.3.0
3.4.0
3.5.0
3.5.1
3.5.3
3.5.6
3.6.0
3.6.1
3.6.2
3.6.3
3.6.4
3.6.5
3.6.6
3.6.7
4.0.0
4.1.0
Fixed in
4.2.0
References
Updated Jul 07, 2026 · Source: OSV.dev
CVE-2024-55655
PYSEC-2026-1923
GHSA-hhfg-fwrw-87w7
Jul 07, 2026
sigstore has insufficient validation of integration timestamp during verification
Medium
Network
Low
None
None
SummaryVersions of sigstore-python newer than 2.0.0 but prior to 3.6.0 perform insufficient validation of the "integration time" present in "v2" and "v3" bundles during the verification flow: the "integration time" is verified if a source of signed time (such as an inclusion promise) is present, but is otherwise trusted if no source of signed time is present. This does not affect "v1" bundles, as the "v1" bundle format always requires an inclusion promise. DetailsSigstore uses signed time to support verification of signatures made against short-lived signing keys. ImpactThe impact and severity of this weakness is low, as Sigstore contains multiple other enforcing components that prevent an attacker who modifies the integration timestamp within a bundle from impersonating a valid signature. In particular, an attacker who modifies the integration timestamp can induce a Denial of Service, but in no different manner than already possible with bundle access (e.g. modifying the signature itself such that it fails to verify). Separately, an attacker could upload a new entry to the transparency service, and substitute their new entry's time. However, this would still be rejected at validation time, as the new entry's (valid) signed time would be outside the validity window of the original signing certificate and would nonetheless render the attacker auditable. Affected versions
2.0.0
2.0.1
2.1.0
2.1.2
2.1.3
2.1.5
3.0.0
3.0.0rc1
3.0.0rc2
3.1.0
3.2.0
3.3.0
+ 5 more Show less
3.4.0
3.5.0
3.5.1
3.5.3
3.5.6
Fixed in
3.6.0
References
Updated Jul 07, 2026 · Source: OSV.dev | ||
3.1.0
minor
2 CVEs
CVE-2026-24408
PYSEC-2026-1924
GHSA-hm8f-75xx-w2vr
Jul 07, 2026
sigstore CSRF possibility in OIDC authentication during signing
0.0
/ 10
None
Network
High
None
Required
Unchanged
None
None
None
SummaryThe sigstore-python OAuth authentication flow is susceptible to Cross-Site Request Forgery. Details
Fix should be fairly trivial. ImpactThis 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. Affected versions
0.0.1rc1
0.0.1rc2
0.0.1rc3
0.1.0
0.10.0
0.2.0
0.3.1
0.4.0
0.4.1
0.4.2
0.5.0
0.5.1
+ 50 more Show less
0.5.1rc1
0.5.1rc2
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.8.3
0.9.0
1.0.0
1.0.0rc1
1.1.0
1.1.1
1.1.1rc1
1.1.2
1.1.2rc1
2.0.0
2.0.0rc1
2.0.0rc2
2.0.0rc3
2.0.1
2.1.0
2.1.2
2.1.3
2.1.5
3.0.0
3.0.0rc1
3.0.0rc2
3.1.0
3.2.0
3.3.0
3.4.0
3.5.0
3.5.1
3.5.3
3.5.6
3.6.0
3.6.1
3.6.2
3.6.3
3.6.4
3.6.5
3.6.6
3.6.7
4.0.0
4.1.0
Fixed in
4.2.0
References
Updated Jul 07, 2026 · Source: OSV.dev
CVE-2024-55655
PYSEC-2026-1923
GHSA-hhfg-fwrw-87w7
Jul 07, 2026
sigstore has insufficient validation of integration timestamp during verification
Medium
Network
Low
None
None
SummaryVersions of sigstore-python newer than 2.0.0 but prior to 3.6.0 perform insufficient validation of the "integration time" present in "v2" and "v3" bundles during the verification flow: the "integration time" is verified if a source of signed time (such as an inclusion promise) is present, but is otherwise trusted if no source of signed time is present. This does not affect "v1" bundles, as the "v1" bundle format always requires an inclusion promise. DetailsSigstore uses signed time to support verification of signatures made against short-lived signing keys. ImpactThe impact and severity of this weakness is low, as Sigstore contains multiple other enforcing components that prevent an attacker who modifies the integration timestamp within a bundle from impersonating a valid signature. In particular, an attacker who modifies the integration timestamp can induce a Denial of Service, but in no different manner than already possible with bundle access (e.g. modifying the signature itself such that it fails to verify). Separately, an attacker could upload a new entry to the transparency service, and substitute their new entry's time. However, this would still be rejected at validation time, as the new entry's (valid) signed time would be outside the validity window of the original signing certificate and would nonetheless render the attacker auditable. Affected versions
2.0.0
2.0.1
2.1.0
2.1.2
2.1.3
2.1.5
3.0.0
3.0.0rc1
3.0.0rc2
3.1.0
3.2.0
3.3.0
+ 5 more Show less
3.4.0
3.5.0
3.5.1
3.5.3
3.5.6
Fixed in
3.6.0
References
Updated Jul 07, 2026 · Source: OSV.dev | ||
3.0.0
major
2 CVEs
CVE-2026-24408
PYSEC-2026-1924
GHSA-hm8f-75xx-w2vr
Jul 07, 2026
sigstore CSRF possibility in OIDC authentication during signing
0.0
/ 10
None
Network
High
None
Required
Unchanged
None
None
None
SummaryThe sigstore-python OAuth authentication flow is susceptible to Cross-Site Request Forgery. Details
Fix should be fairly trivial. ImpactThis 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. Affected versions
0.0.1rc1
0.0.1rc2
0.0.1rc3
0.1.0
0.10.0
0.2.0
0.3.1
0.4.0
0.4.1
0.4.2
0.5.0
0.5.1
+ 50 more Show less
0.5.1rc1
0.5.1rc2
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.8.3
0.9.0
1.0.0
1.0.0rc1
1.1.0
1.1.1
1.1.1rc1
1.1.2
1.1.2rc1
2.0.0
2.0.0rc1
2.0.0rc2
2.0.0rc3
2.0.1
2.1.0
2.1.2
2.1.3
2.1.5
3.0.0
3.0.0rc1
3.0.0rc2
3.1.0
3.2.0
3.3.0
3.4.0
3.5.0
3.5.1
3.5.3
3.5.6
3.6.0
3.6.1
3.6.2
3.6.3
3.6.4
3.6.5
3.6.6
3.6.7
4.0.0
4.1.0
Fixed in
4.2.0
References
Updated Jul 07, 2026 · Source: OSV.dev
CVE-2024-55655
PYSEC-2026-1923
GHSA-hhfg-fwrw-87w7
Jul 07, 2026
sigstore has insufficient validation of integration timestamp during verification
Medium
Network
Low
None
None
SummaryVersions of sigstore-python newer than 2.0.0 but prior to 3.6.0 perform insufficient validation of the "integration time" present in "v2" and "v3" bundles during the verification flow: the "integration time" is verified if a source of signed time (such as an inclusion promise) is present, but is otherwise trusted if no source of signed time is present. This does not affect "v1" bundles, as the "v1" bundle format always requires an inclusion promise. DetailsSigstore uses signed time to support verification of signatures made against short-lived signing keys. ImpactThe impact and severity of this weakness is low, as Sigstore contains multiple other enforcing components that prevent an attacker who modifies the integration timestamp within a bundle from impersonating a valid signature. In particular, an attacker who modifies the integration timestamp can induce a Denial of Service, but in no different manner than already possible with bundle access (e.g. modifying the signature itself such that it fails to verify). Separately, an attacker could upload a new entry to the transparency service, and substitute their new entry's time. However, this would still be rejected at validation time, as the new entry's (valid) signed time would be outside the validity window of the original signing certificate and would nonetheless render the attacker auditable. Affected versions
2.0.0
2.0.1
2.1.0
2.1.2
2.1.3
2.1.5
3.0.0
3.0.0rc1
3.0.0rc2
3.1.0
3.2.0
3.3.0
+ 5 more Show less
3.4.0
3.5.0
3.5.1
3.5.3
3.5.6
Fixed in
3.6.0
References
Updated Jul 07, 2026 · Source: OSV.dev | ||
3.0.0rc2
pre
2 CVEs
CVE-2026-24408
PYSEC-2026-1924
GHSA-hm8f-75xx-w2vr
Jul 07, 2026
sigstore CSRF possibility in OIDC authentication during signing
0.0
/ 10
None
Network
High
None
Required
Unchanged
None
None
None
SummaryThe sigstore-python OAuth authentication flow is susceptible to Cross-Site Request Forgery. Details
Fix should be fairly trivial. ImpactThis 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. Affected versions
0.0.1rc1
0.0.1rc2
0.0.1rc3
0.1.0
0.10.0
0.2.0
0.3.1
0.4.0
0.4.1
0.4.2
0.5.0
0.5.1
+ 50 more Show less
0.5.1rc1
0.5.1rc2
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.8.3
0.9.0
1.0.0
1.0.0rc1
1.1.0
1.1.1
1.1.1rc1
1.1.2
1.1.2rc1
2.0.0
2.0.0rc1
2.0.0rc2
2.0.0rc3
2.0.1
2.1.0
2.1.2
2.1.3
2.1.5
3.0.0
3.0.0rc1
3.0.0rc2
3.1.0
3.2.0
3.3.0
3.4.0
3.5.0
3.5.1
3.5.3
3.5.6
3.6.0
3.6.1
3.6.2
3.6.3
3.6.4
3.6.5
3.6.6
3.6.7
4.0.0
4.1.0
Fixed in
4.2.0
References
Updated Jul 07, 2026 · Source: OSV.dev
CVE-2024-55655
PYSEC-2026-1923
GHSA-hhfg-fwrw-87w7
Jul 07, 2026
sigstore has insufficient validation of integration timestamp during verification
Medium
Network
Low
None
None
SummaryVersions of sigstore-python newer than 2.0.0 but prior to 3.6.0 perform insufficient validation of the "integration time" present in "v2" and "v3" bundles during the verification flow: the "integration time" is verified if a source of signed time (such as an inclusion promise) is present, but is otherwise trusted if no source of signed time is present. This does not affect "v1" bundles, as the "v1" bundle format always requires an inclusion promise. DetailsSigstore uses signed time to support verification of signatures made against short-lived signing keys. ImpactThe impact and severity of this weakness is low, as Sigstore contains multiple other enforcing components that prevent an attacker who modifies the integration timestamp within a bundle from impersonating a valid signature. In particular, an attacker who modifies the integration timestamp can induce a Denial of Service, but in no different manner than already possible with bundle access (e.g. modifying the signature itself such that it fails to verify). Separately, an attacker could upload a new entry to the transparency service, and substitute their new entry's time. However, this would still be rejected at validation time, as the new entry's (valid) signed time would be outside the validity window of the original signing certificate and would nonetheless render the attacker auditable. Affected versions
2.0.0
2.0.1
2.1.0
2.1.2
2.1.3
2.1.5
3.0.0
3.0.0rc1
3.0.0rc2
3.1.0
3.2.0
3.3.0
+ 5 more Show less
3.4.0
3.5.0
3.5.1
3.5.3
3.5.6
Fixed in
3.6.0
References
Updated Jul 07, 2026 · Source: OSV.dev | ||
3.0.0rc1
pre
2 CVEs
CVE-2026-24408
PYSEC-2026-1924
GHSA-hm8f-75xx-w2vr
Jul 07, 2026
sigstore CSRF possibility in OIDC authentication during signing
0.0
/ 10
None
Network
High
None
Required
Unchanged
None
None
None
SummaryThe sigstore-python OAuth authentication flow is susceptible to Cross-Site Request Forgery. Details
Fix should be fairly trivial. ImpactThis 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. Affected versions
0.0.1rc1
0.0.1rc2
0.0.1rc3
0.1.0
0.10.0
0.2.0
0.3.1
0.4.0
0.4.1
0.4.2
0.5.0
0.5.1
+ 50 more Show less
0.5.1rc1
0.5.1rc2
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.8.3
0.9.0
1.0.0
1.0.0rc1
1.1.0
1.1.1
1.1.1rc1
1.1.2
1.1.2rc1
2.0.0
2.0.0rc1
2.0.0rc2
2.0.0rc3
2.0.1
2.1.0
2.1.2
2.1.3
2.1.5
3.0.0
3.0.0rc1
3.0.0rc2
3.1.0
3.2.0
3.3.0
3.4.0
3.5.0
3.5.1
3.5.3
3.5.6
3.6.0
3.6.1
3.6.2
3.6.3
3.6.4
3.6.5
3.6.6
3.6.7
4.0.0
4.1.0
Fixed in
4.2.0
References
Updated Jul 07, 2026 · Source: OSV.dev
CVE-2024-55655
PYSEC-2026-1923
GHSA-hhfg-fwrw-87w7
Jul 07, 2026
sigstore has insufficient validation of integration timestamp during verification
Medium
Network
Low
None
None
SummaryVersions of sigstore-python newer than 2.0.0 but prior to 3.6.0 perform insufficient validation of the "integration time" present in "v2" and "v3" bundles during the verification flow: the "integration time" is verified if a source of signed time (such as an inclusion promise) is present, but is otherwise trusted if no source of signed time is present. This does not affect "v1" bundles, as the "v1" bundle format always requires an inclusion promise. DetailsSigstore uses signed time to support verification of signatures made against short-lived signing keys. ImpactThe impact and severity of this weakness is low, as Sigstore contains multiple other enforcing components that prevent an attacker who modifies the integration timestamp within a bundle from impersonating a valid signature. In particular, an attacker who modifies the integration timestamp can induce a Denial of Service, but in no different manner than already possible with bundle access (e.g. modifying the signature itself such that it fails to verify). Separately, an attacker could upload a new entry to the transparency service, and substitute their new entry's time. However, this would still be rejected at validation time, as the new entry's (valid) signed time would be outside the validity window of the original signing certificate and would nonetheless render the attacker auditable. Affected versions
2.0.0
2.0.1
2.1.0
2.1.2
2.1.3
2.1.5
3.0.0
3.0.0rc1
3.0.0rc2
3.1.0
3.2.0
3.3.0
+ 5 more Show less
3.4.0
3.5.0
3.5.1
3.5.3
3.5.6
Fixed in
3.6.0
References
Updated Jul 07, 2026 · Source: OSV.dev | ||
2.1.5
patch
2 CVEs
CVE-2026-24408
PYSEC-2026-1924
GHSA-hm8f-75xx-w2vr
Jul 07, 2026
sigstore CSRF possibility in OIDC authentication during signing
0.0
/ 10
None
Network
High
None
Required
Unchanged
None
None
None
SummaryThe sigstore-python OAuth authentication flow is susceptible to Cross-Site Request Forgery. Details
Fix should be fairly trivial. ImpactThis 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. Affected versions
0.0.1rc1
0.0.1rc2
0.0.1rc3
0.1.0
0.10.0
0.2.0
0.3.1
0.4.0
0.4.1
0.4.2
0.5.0
0.5.1
+ 50 more Show less
0.5.1rc1
0.5.1rc2
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.8.3
0.9.0
1.0.0
1.0.0rc1
1.1.0
1.1.1
1.1.1rc1
1.1.2
1.1.2rc1
2.0.0
2.0.0rc1
2.0.0rc2
2.0.0rc3
2.0.1
2.1.0
2.1.2
2.1.3
2.1.5
3.0.0
3.0.0rc1
3.0.0rc2
3.1.0
3.2.0
3.3.0
3.4.0
3.5.0
3.5.1
3.5.3
3.5.6
3.6.0
3.6.1
3.6.2
3.6.3
3.6.4
3.6.5
3.6.6
3.6.7
4.0.0
4.1.0
Fixed in
4.2.0
References
Updated Jul 07, 2026 · Source: OSV.dev
CVE-2024-55655
PYSEC-2026-1923
GHSA-hhfg-fwrw-87w7
Jul 07, 2026
sigstore has insufficient validation of integration timestamp during verification
Medium
Network
Low
None
None
SummaryVersions of sigstore-python newer than 2.0.0 but prior to 3.6.0 perform insufficient validation of the "integration time" present in "v2" and "v3" bundles during the verification flow: the "integration time" is verified if a source of signed time (such as an inclusion promise) is present, but is otherwise trusted if no source of signed time is present. This does not affect "v1" bundles, as the "v1" bundle format always requires an inclusion promise. DetailsSigstore uses signed time to support verification of signatures made against short-lived signing keys. ImpactThe impact and severity of this weakness is low, as Sigstore contains multiple other enforcing components that prevent an attacker who modifies the integration timestamp within a bundle from impersonating a valid signature. In particular, an attacker who modifies the integration timestamp can induce a Denial of Service, but in no different manner than already possible with bundle access (e.g. modifying the signature itself such that it fails to verify). Separately, an attacker could upload a new entry to the transparency service, and substitute their new entry's time. However, this would still be rejected at validation time, as the new entry's (valid) signed time would be outside the validity window of the original signing certificate and would nonetheless render the attacker auditable. Affected versions
2.0.0
2.0.1
2.1.0
2.1.2
2.1.3
2.1.5
3.0.0
3.0.0rc1
3.0.0rc2
3.1.0
3.2.0
3.3.0
+ 5 more Show less
3.4.0
3.5.0
3.5.1
3.5.3
3.5.6
Fixed in
3.6.0
References
Updated Jul 07, 2026 · Source: OSV.dev | ||
2.1.3
patch
2 CVEs
CVE-2026-24408
PYSEC-2026-1924
GHSA-hm8f-75xx-w2vr
Jul 07, 2026
sigstore CSRF possibility in OIDC authentication during signing
0.0
/ 10
None
Network
High
None
Required
Unchanged
None
None
None
SummaryThe sigstore-python OAuth authentication flow is susceptible to Cross-Site Request Forgery. Details
Fix should be fairly trivial. ImpactThis 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. Affected versions
0.0.1rc1
0.0.1rc2
0.0.1rc3
0.1.0
0.10.0
0.2.0
0.3.1
0.4.0
0.4.1
0.4.2
0.5.0
0.5.1
+ 50 more Show less
0.5.1rc1
0.5.1rc2
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.8.3
0.9.0
1.0.0
1.0.0rc1
1.1.0
1.1.1
1.1.1rc1
1.1.2
1.1.2rc1
2.0.0
2.0.0rc1
2.0.0rc2
2.0.0rc3
2.0.1
2.1.0
2.1.2
2.1.3
2.1.5
3.0.0
3.0.0rc1
3.0.0rc2
3.1.0
3.2.0
3.3.0
3.4.0
3.5.0
3.5.1
3.5.3
3.5.6
3.6.0
3.6.1
3.6.2
3.6.3
3.6.4
3.6.5
3.6.6
3.6.7
4.0.0
4.1.0
Fixed in
4.2.0
References
Updated Jul 07, 2026 · Source: OSV.dev
CVE-2024-55655
PYSEC-2026-1923
GHSA-hhfg-fwrw-87w7
Jul 07, 2026
sigstore has insufficient validation of integration timestamp during verification
Medium
Network
Low
None
None
SummaryVersions of sigstore-python newer than 2.0.0 but prior to 3.6.0 perform insufficient validation of the "integration time" present in "v2" and "v3" bundles during the verification flow: the "integration time" is verified if a source of signed time (such as an inclusion promise) is present, but is otherwise trusted if no source of signed time is present. This does not affect "v1" bundles, as the "v1" bundle format always requires an inclusion promise. DetailsSigstore uses signed time to support verification of signatures made against short-lived signing keys. ImpactThe impact and severity of this weakness is low, as Sigstore contains multiple other enforcing components that prevent an attacker who modifies the integration timestamp within a bundle from impersonating a valid signature. In particular, an attacker who modifies the integration timestamp can induce a Denial of Service, but in no different manner than already possible with bundle access (e.g. modifying the signature itself such that it fails to verify). Separately, an attacker could upload a new entry to the transparency service, and substitute their new entry's time. However, this would still be rejected at validation time, as the new entry's (valid) signed time would be outside the validity window of the original signing certificate and would nonetheless render the attacker auditable. Affected versions
2.0.0
2.0.1
2.1.0
2.1.2
2.1.3
2.1.5
3.0.0
3.0.0rc1
3.0.0rc2
3.1.0
3.2.0
3.3.0
+ 5 more Show less
3.4.0
3.5.0
3.5.1
3.5.3
3.5.6
Fixed in
3.6.0
References
Updated Jul 07, 2026 · Source: OSV.dev | ||
2.1.2
patch
2 CVEs
CVE-2026-24408
PYSEC-2026-1924
GHSA-hm8f-75xx-w2vr
Jul 07, 2026
sigstore CSRF possibility in OIDC authentication during signing
0.0
/ 10
None
Network
High
None
Required
Unchanged
None
None
None
SummaryThe sigstore-python OAuth authentication flow is susceptible to Cross-Site Request Forgery. Details
Fix should be fairly trivial. ImpactThis 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. Affected versions
0.0.1rc1
0.0.1rc2
0.0.1rc3
0.1.0
0.10.0
0.2.0
0.3.1
0.4.0
0.4.1
0.4.2
0.5.0
0.5.1
+ 50 more Show less
0.5.1rc1
0.5.1rc2
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.8.3
0.9.0
1.0.0
1.0.0rc1
1.1.0
1.1.1
1.1.1rc1
1.1.2
1.1.2rc1
2.0.0
2.0.0rc1
2.0.0rc2
2.0.0rc3
2.0.1
2.1.0
2.1.2
2.1.3
2.1.5
3.0.0
3.0.0rc1
3.0.0rc2
3.1.0
3.2.0
3.3.0
3.4.0
3.5.0
3.5.1
3.5.3
3.5.6
3.6.0
3.6.1
3.6.2
3.6.3
3.6.4
3.6.5
3.6.6
3.6.7
4.0.0
4.1.0
Fixed in
4.2.0
References
Updated Jul 07, 2026 · Source: OSV.dev
CVE-2024-55655
PYSEC-2026-1923
GHSA-hhfg-fwrw-87w7
Jul 07, 2026
sigstore has insufficient validation of integration timestamp during verification
Medium
Network
Low
None
None
SummaryVersions of sigstore-python newer than 2.0.0 but prior to 3.6.0 perform insufficient validation of the "integration time" present in "v2" and "v3" bundles during the verification flow: the "integration time" is verified if a source of signed time (such as an inclusion promise) is present, but is otherwise trusted if no source of signed time is present. This does not affect "v1" bundles, as the "v1" bundle format always requires an inclusion promise. DetailsSigstore uses signed time to support verification of signatures made against short-lived signing keys. ImpactThe impact and severity of this weakness is low, as Sigstore contains multiple other enforcing components that prevent an attacker who modifies the integration timestamp within a bundle from impersonating a valid signature. In particular, an attacker who modifies the integration timestamp can induce a Denial of Service, but in no different manner than already possible with bundle access (e.g. modifying the signature itself such that it fails to verify). Separately, an attacker could upload a new entry to the transparency service, and substitute their new entry's time. However, this would still be rejected at validation time, as the new entry's (valid) signed time would be outside the validity window of the original signing certificate and would nonetheless render the attacker auditable. Affected versions
2.0.0
2.0.1
2.1.0
2.1.2
2.1.3
2.1.5
3.0.0
3.0.0rc1
3.0.0rc2
3.1.0
3.2.0
3.3.0
+ 5 more Show less
3.4.0
3.5.0
3.5.1
3.5.3
3.5.6
Fixed in
3.6.0
References
Updated Jul 07, 2026 · Source: OSV.dev | ||
2.1.0
minor
2 CVEs
CVE-2026-24408
PYSEC-2026-1924
GHSA-hm8f-75xx-w2vr
Jul 07, 2026
sigstore CSRF possibility in OIDC authentication during signing
0.0
/ 10
None
Network
High
None
Required
Unchanged
None
None
None
SummaryThe sigstore-python OAuth authentication flow is susceptible to Cross-Site Request Forgery. Details
Fix should be fairly trivial. ImpactThis 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. Affected versions
0.0.1rc1
0.0.1rc2
0.0.1rc3
0.1.0
0.10.0
0.2.0
0.3.1
0.4.0
0.4.1
0.4.2
0.5.0
0.5.1
+ 50 more Show less
0.5.1rc1
0.5.1rc2
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.8.3
0.9.0
1.0.0
1.0.0rc1
1.1.0
1.1.1
1.1.1rc1
1.1.2
1.1.2rc1
2.0.0
2.0.0rc1
2.0.0rc2
2.0.0rc3
2.0.1
2.1.0
2.1.2
2.1.3
2.1.5
3.0.0
3.0.0rc1
3.0.0rc2
3.1.0
3.2.0
3.3.0
3.4.0
3.5.0
3.5.1
3.5.3
3.5.6
3.6.0
3.6.1
3.6.2
3.6.3
3.6.4
3.6.5
3.6.6
3.6.7
4.0.0
4.1.0
Fixed in
4.2.0
References
Updated Jul 07, 2026 · Source: OSV.dev
CVE-2024-55655
PYSEC-2026-1923
GHSA-hhfg-fwrw-87w7
Jul 07, 2026
sigstore has insufficient validation of integration timestamp during verification
Medium
Network
Low
None
None
SummaryVersions of sigstore-python newer than 2.0.0 but prior to 3.6.0 perform insufficient validation of the "integration time" present in "v2" and "v3" bundles during the verification flow: the "integration time" is verified if a source of signed time (such as an inclusion promise) is present, but is otherwise trusted if no source of signed time is present. This does not affect "v1" bundles, as the "v1" bundle format always requires an inclusion promise. DetailsSigstore uses signed time to support verification of signatures made against short-lived signing keys. ImpactThe impact and severity of this weakness is low, as Sigstore contains multiple other enforcing components that prevent an attacker who modifies the integration timestamp within a bundle from impersonating a valid signature. In particular, an attacker who modifies the integration timestamp can induce a Denial of Service, but in no different manner than already possible with bundle access (e.g. modifying the signature itself such that it fails to verify). Separately, an attacker could upload a new entry to the transparency service, and substitute their new entry's time. However, this would still be rejected at validation time, as the new entry's (valid) signed time would be outside the validity window of the original signing certificate and would nonetheless render the attacker auditable. Affected versions
2.0.0
2.0.1
2.1.0
2.1.2
2.1.3
2.1.5
3.0.0
3.0.0rc1
3.0.0rc2
3.1.0
3.2.0
3.3.0
+ 5 more Show less
3.4.0
3.5.0
3.5.1
3.5.3
3.5.6
Fixed in
3.6.0
References
Updated Jul 07, 2026 · Source: OSV.dev | ||
2.0.1
patch
2 CVEs
CVE-2026-24408
PYSEC-2026-1924
GHSA-hm8f-75xx-w2vr
Jul 07, 2026
sigstore CSRF possibility in OIDC authentication during signing
0.0
/ 10
None
Network
High
None
Required
Unchanged
None
None
None
SummaryThe sigstore-python OAuth authentication flow is susceptible to Cross-Site Request Forgery. Details
Fix should be fairly trivial. ImpactThis 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. Affected versions
0.0.1rc1
0.0.1rc2
0.0.1rc3
0.1.0
0.10.0
0.2.0
0.3.1
0.4.0
0.4.1
0.4.2
0.5.0
0.5.1
+ 50 more Show less
0.5.1rc1
0.5.1rc2
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.8.3
0.9.0
1.0.0
1.0.0rc1
1.1.0
1.1.1
1.1.1rc1
1.1.2
1.1.2rc1
2.0.0
2.0.0rc1
2.0.0rc2
2.0.0rc3
2.0.1
2.1.0
2.1.2
2.1.3
2.1.5
3.0.0
3.0.0rc1
3.0.0rc2
3.1.0
3.2.0
3.3.0
3.4.0
3.5.0
3.5.1
3.5.3
3.5.6
3.6.0
3.6.1
3.6.2
3.6.3
3.6.4
3.6.5
3.6.6
3.6.7
4.0.0
4.1.0
Fixed in
4.2.0
References
Updated Jul 07, 2026 · Source: OSV.dev
CVE-2024-55655
PYSEC-2026-1923
GHSA-hhfg-fwrw-87w7
Jul 07, 2026
sigstore has insufficient validation of integration timestamp during verification
Medium
Network
Low
None
None
SummaryVersions of sigstore-python newer than 2.0.0 but prior to 3.6.0 perform insufficient validation of the "integration time" present in "v2" and "v3" bundles during the verification flow: the "integration time" is verified if a source of signed time (such as an inclusion promise) is present, but is otherwise trusted if no source of signed time is present. This does not affect "v1" bundles, as the "v1" bundle format always requires an inclusion promise. DetailsSigstore uses signed time to support verification of signatures made against short-lived signing keys. ImpactThe impact and severity of this weakness is low, as Sigstore contains multiple other enforcing components that prevent an attacker who modifies the integration timestamp within a bundle from impersonating a valid signature. In particular, an attacker who modifies the integration timestamp can induce a Denial of Service, but in no different manner than already possible with bundle access (e.g. modifying the signature itself such that it fails to verify). Separately, an attacker could upload a new entry to the transparency service, and substitute their new entry's time. However, this would still be rejected at validation time, as the new entry's (valid) signed time would be outside the validity window of the original signing certificate and would nonetheless render the attacker auditable. Affected versions
2.0.0
2.0.1
2.1.0
2.1.2
2.1.3
2.1.5
3.0.0
3.0.0rc1
3.0.0rc2
3.1.0
3.2.0
3.3.0
+ 5 more Show less
3.4.0
3.5.0
3.5.1
3.5.3
3.5.6
Fixed in
3.6.0
References
Updated Jul 07, 2026 · Source: OSV.dev | ||
2.0.0
major
2 CVEs
CVE-2026-24408
PYSEC-2026-1924
GHSA-hm8f-75xx-w2vr
Jul 07, 2026
sigstore CSRF possibility in OIDC authentication during signing
0.0
/ 10
None
Network
High
None
Required
Unchanged
None
None
None
SummaryThe sigstore-python OAuth authentication flow is susceptible to Cross-Site Request Forgery. Details
Fix should be fairly trivial. ImpactThis 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. Affected versions
0.0.1rc1
0.0.1rc2
0.0.1rc3
0.1.0
0.10.0
0.2.0
0.3.1
0.4.0
0.4.1
0.4.2
0.5.0
0.5.1
+ 50 more Show less
0.5.1rc1
0.5.1rc2
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.8.3
0.9.0
1.0.0
1.0.0rc1
1.1.0
1.1.1
1.1.1rc1
1.1.2
1.1.2rc1
2.0.0
2.0.0rc1
2.0.0rc2
2.0.0rc3
2.0.1
2.1.0
2.1.2
2.1.3
2.1.5
3.0.0
3.0.0rc1
3.0.0rc2
3.1.0
3.2.0
3.3.0
3.4.0
3.5.0
3.5.1
3.5.3
3.5.6
3.6.0
3.6.1
3.6.2
3.6.3
3.6.4
3.6.5
3.6.6
3.6.7
4.0.0
4.1.0
Fixed in
4.2.0
References
Updated Jul 07, 2026 · Source: OSV.dev
CVE-2024-55655
PYSEC-2026-1923
GHSA-hhfg-fwrw-87w7
Jul 07, 2026
sigstore has insufficient validation of integration timestamp during verification
Medium
Network
Low
None
None
SummaryVersions of sigstore-python newer than 2.0.0 but prior to 3.6.0 perform insufficient validation of the "integration time" present in "v2" and "v3" bundles during the verification flow: the "integration time" is verified if a source of signed time (such as an inclusion promise) is present, but is otherwise trusted if no source of signed time is present. This does not affect "v1" bundles, as the "v1" bundle format always requires an inclusion promise. DetailsSigstore uses signed time to support verification of signatures made against short-lived signing keys. ImpactThe impact and severity of this weakness is low, as Sigstore contains multiple other enforcing components that prevent an attacker who modifies the integration timestamp within a bundle from impersonating a valid signature. In particular, an attacker who modifies the integration timestamp can induce a Denial of Service, but in no different manner than already possible with bundle access (e.g. modifying the signature itself such that it fails to verify). Separately, an attacker could upload a new entry to the transparency service, and substitute their new entry's time. However, this would still be rejected at validation time, as the new entry's (valid) signed time would be outside the validity window of the original signing certificate and would nonetheless render the attacker auditable. Affected versions
2.0.0
2.0.1
2.1.0
2.1.2
2.1.3
2.1.5
3.0.0
3.0.0rc1
3.0.0rc2
3.1.0
3.2.0
3.3.0
+ 5 more Show less
3.4.0
3.5.0
3.5.1
3.5.3
3.5.6
Fixed in
3.6.0
References
Updated Jul 07, 2026 · Source: OSV.dev | ||
2.0.0rc3
pre
1 CVE
CVE-2026-24408
PYSEC-2026-1924
GHSA-hm8f-75xx-w2vr
Jul 07, 2026
sigstore CSRF possibility in OIDC authentication during signing
0.0
/ 10
None
Network
High
None
Required
Unchanged
None
None
None
SummaryThe sigstore-python OAuth authentication flow is susceptible to Cross-Site Request Forgery. Details
Fix should be fairly trivial. ImpactThis 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. Affected versions
0.0.1rc1
0.0.1rc2
0.0.1rc3
0.1.0
0.10.0
0.2.0
0.3.1
0.4.0
0.4.1
0.4.2
0.5.0
0.5.1
+ 50 more Show less
0.5.1rc1
0.5.1rc2
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.8.3
0.9.0
1.0.0
1.0.0rc1
1.1.0
1.1.1
1.1.1rc1
1.1.2
1.1.2rc1
2.0.0
2.0.0rc1
2.0.0rc2
2.0.0rc3
2.0.1
2.1.0
2.1.2
2.1.3
2.1.5
3.0.0
3.0.0rc1
3.0.0rc2
3.1.0
3.2.0
3.3.0
3.4.0
3.5.0
3.5.1
3.5.3
3.5.6
3.6.0
3.6.1
3.6.2
3.6.3
3.6.4
3.6.5
3.6.6
3.6.7
4.0.0
4.1.0
Fixed in
4.2.0
References
Updated Jul 07, 2026 · Source: OSV.dev | ||
2.0.0rc2
pre
1 CVE
CVE-2026-24408
PYSEC-2026-1924
GHSA-hm8f-75xx-w2vr
Jul 07, 2026
sigstore CSRF possibility in OIDC authentication during signing
0.0
/ 10
None
Network
High
None
Required
Unchanged
None
None
None
SummaryThe sigstore-python OAuth authentication flow is susceptible to Cross-Site Request Forgery. Details
Fix should be fairly trivial. ImpactThis 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. Affected versions
0.0.1rc1
0.0.1rc2
0.0.1rc3
0.1.0
0.10.0
0.2.0
0.3.1
0.4.0
0.4.1
0.4.2
0.5.0
0.5.1
+ 50 more Show less
0.5.1rc1
0.5.1rc2
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.8.3
0.9.0
1.0.0
1.0.0rc1
1.1.0
1.1.1
1.1.1rc1
1.1.2
1.1.2rc1
2.0.0
2.0.0rc1
2.0.0rc2
2.0.0rc3
2.0.1
2.1.0
2.1.2
2.1.3
2.1.5
3.0.0
3.0.0rc1
3.0.0rc2
3.1.0
3.2.0
3.3.0
3.4.0
3.5.0
3.5.1
3.5.3
3.5.6
3.6.0
3.6.1
3.6.2
3.6.3
3.6.4
3.6.5
3.6.6
3.6.7
4.0.0
4.1.0
Fixed in
4.2.0
References
Updated Jul 07, 2026 · Source: OSV.dev | ||
2.0.0rc1
pre
1 CVE
CVE-2026-24408
PYSEC-2026-1924
GHSA-hm8f-75xx-w2vr
Jul 07, 2026
sigstore CSRF possibility in OIDC authentication during signing
0.0
/ 10
None
Network
High
None
Required
Unchanged
None
None
None
SummaryThe sigstore-python OAuth authentication flow is susceptible to Cross-Site Request Forgery. Details
Fix should be fairly trivial. ImpactThis 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. Affected versions
0.0.1rc1
0.0.1rc2
0.0.1rc3
0.1.0
0.10.0
0.2.0
0.3.1
0.4.0
0.4.1
0.4.2
0.5.0
0.5.1
+ 50 more Show less
0.5.1rc1
0.5.1rc2
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.8.3
0.9.0
1.0.0
1.0.0rc1
1.1.0
1.1.1
1.1.1rc1
1.1.2
1.1.2rc1
2.0.0
2.0.0rc1
2.0.0rc2
2.0.0rc3
2.0.1
2.1.0
2.1.2
2.1.3
2.1.5
3.0.0
3.0.0rc1
3.0.0rc2
3.1.0
3.2.0
3.3.0
3.4.0
3.5.0
3.5.1
3.5.3
3.5.6
3.6.0
3.6.1
3.6.2
3.6.3
3.6.4
3.6.5
3.6.6
3.6.7
4.0.0
4.1.0
Fixed in
4.2.0
References
Updated Jul 07, 2026 · Source: OSV.dev | ||
1.1.2
patch
1 CVE
CVE-2026-24408
PYSEC-2026-1924
GHSA-hm8f-75xx-w2vr
Jul 07, 2026
sigstore CSRF possibility in OIDC authentication during signing
0.0
/ 10
None
Network
High
None
Required
Unchanged
None
None
None
SummaryThe sigstore-python OAuth authentication flow is susceptible to Cross-Site Request Forgery. Details
Fix should be fairly trivial. ImpactThis 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. Affected versions
0.0.1rc1
0.0.1rc2
0.0.1rc3
0.1.0
0.10.0
0.2.0
0.3.1
0.4.0
0.4.1
0.4.2
0.5.0
0.5.1
+ 50 more Show less
0.5.1rc1
0.5.1rc2
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.8.3
0.9.0
1.0.0
1.0.0rc1
1.1.0
1.1.1
1.1.1rc1
1.1.2
1.1.2rc1
2.0.0
2.0.0rc1
2.0.0rc2
2.0.0rc3
2.0.1
2.1.0
2.1.2
2.1.3
2.1.5
3.0.0
3.0.0rc1
3.0.0rc2
3.1.0
3.2.0
3.3.0
3.4.0
3.5.0
3.5.1
3.5.3
3.5.6
3.6.0
3.6.1
3.6.2
3.6.3
3.6.4
3.6.5
3.6.6
3.6.7
4.0.0
4.1.0
Fixed in
4.2.0
References
Updated Jul 07, 2026 · Source: OSV.dev | ||
1.1.2rc1
pre
1 CVE
CVE-2026-24408
PYSEC-2026-1924
GHSA-hm8f-75xx-w2vr
Jul 07, 2026
sigstore CSRF possibility in OIDC authentication during signing
0.0
/ 10
None
Network
High
None
Required
Unchanged
None
None
None
SummaryThe sigstore-python OAuth authentication flow is susceptible to Cross-Site Request Forgery. Details
Fix should be fairly trivial. ImpactThis 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. Affected versions
0.0.1rc1
0.0.1rc2
0.0.1rc3
0.1.0
0.10.0
0.2.0
0.3.1
0.4.0
0.4.1
0.4.2
0.5.0
0.5.1
+ 50 more Show less
0.5.1rc1
0.5.1rc2
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.8.3
0.9.0
1.0.0
1.0.0rc1
1.1.0
1.1.1
1.1.1rc1
1.1.2
1.1.2rc1
2.0.0
2.0.0rc1
2.0.0rc2
2.0.0rc3
2.0.1
2.1.0
2.1.2
2.1.3
2.1.5
3.0.0
3.0.0rc1
3.0.0rc2
3.1.0
3.2.0
3.3.0
3.4.0
3.5.0
3.5.1
3.5.3
3.5.6
3.6.0
3.6.1
3.6.2
3.6.3
3.6.4
3.6.5
3.6.6
3.6.7
4.0.0
4.1.0
Fixed in
4.2.0
References
Updated Jul 07, 2026 · Source: OSV.dev | ||
1.1.1
patch
1 CVE
CVE-2026-24408
PYSEC-2026-1924
GHSA-hm8f-75xx-w2vr
Jul 07, 2026
sigstore CSRF possibility in OIDC authentication during signing
0.0
/ 10
None
Network
High
None
Required
Unchanged
None
None
None
SummaryThe sigstore-python OAuth authentication flow is susceptible to Cross-Site Request Forgery. Details
Fix should be fairly trivial. ImpactThis 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. Affected versions
0.0.1rc1
0.0.1rc2
0.0.1rc3
0.1.0
0.10.0
0.2.0
0.3.1
0.4.0
0.4.1
0.4.2
0.5.0
0.5.1
+ 50 more Show less
0.5.1rc1
0.5.1rc2
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.8.3
0.9.0
1.0.0
1.0.0rc1
1.1.0
1.1.1
1.1.1rc1
1.1.2
1.1.2rc1
2.0.0
2.0.0rc1
2.0.0rc2
2.0.0rc3
2.0.1
2.1.0
2.1.2
2.1.3
2.1.5
3.0.0
3.0.0rc1
3.0.0rc2
3.1.0
3.2.0
3.3.0
3.4.0
3.5.0
3.5.1
3.5.3
3.5.6
3.6.0
3.6.1
3.6.2
3.6.3
3.6.4
3.6.5
3.6.6
3.6.7
4.0.0
4.1.0
Fixed in
4.2.0
References
Updated Jul 07, 2026 · Source: OSV.dev | ||
1.1.1rc1
pre
1 CVE
CVE-2026-24408
PYSEC-2026-1924
GHSA-hm8f-75xx-w2vr
Jul 07, 2026
sigstore CSRF possibility in OIDC authentication during signing
0.0
/ 10
None
Network
High
None
Required
Unchanged
None
None
None
SummaryThe sigstore-python OAuth authentication flow is susceptible to Cross-Site Request Forgery. Details
Fix should be fairly trivial. ImpactThis 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. Affected versions
0.0.1rc1
0.0.1rc2
0.0.1rc3
0.1.0
0.10.0
0.2.0
0.3.1
0.4.0
0.4.1
0.4.2
0.5.0
0.5.1
+ 50 more Show less
0.5.1rc1
0.5.1rc2
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.8.3
0.9.0
1.0.0
1.0.0rc1
1.1.0
1.1.1
1.1.1rc1
1.1.2
1.1.2rc1
2.0.0
2.0.0rc1
2.0.0rc2
2.0.0rc3
2.0.1
2.1.0
2.1.2
2.1.3
2.1.5
3.0.0
3.0.0rc1
3.0.0rc2
3.1.0
3.2.0
3.3.0
3.4.0
3.5.0
3.5.1
3.5.3
3.5.6
3.6.0
3.6.1
3.6.2
3.6.3
3.6.4
3.6.5
3.6.6
3.6.7
4.0.0
4.1.0
Fixed in
4.2.0
References
Updated Jul 07, 2026 · Source: OSV.dev | ||
1.1.0
minor
1 CVE
CVE-2026-24408
PYSEC-2026-1924
GHSA-hm8f-75xx-w2vr
Jul 07, 2026
sigstore CSRF possibility in OIDC authentication during signing
0.0
/ 10
None
Network
High
None
Required
Unchanged
None
None
None
SummaryThe sigstore-python OAuth authentication flow is susceptible to Cross-Site Request Forgery. Details
Fix should be fairly trivial. ImpactThis 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. Affected versions
0.0.1rc1
0.0.1rc2
0.0.1rc3
0.1.0
0.10.0
0.2.0
0.3.1
0.4.0
0.4.1
0.4.2
0.5.0
0.5.1
+ 50 more Show less
0.5.1rc1
0.5.1rc2
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.8.3
0.9.0
1.0.0
1.0.0rc1
1.1.0
1.1.1
1.1.1rc1
1.1.2
1.1.2rc1
2.0.0
2.0.0rc1
2.0.0rc2
2.0.0rc3
2.0.1
2.1.0
2.1.2
2.1.3
2.1.5
3.0.0
3.0.0rc1
3.0.0rc2
3.1.0
3.2.0
3.3.0
3.4.0
3.5.0
3.5.1
3.5.3
3.5.6
3.6.0
3.6.1
3.6.2
3.6.3
3.6.4
3.6.5
3.6.6
3.6.7
4.0.0
4.1.0
Fixed in
4.2.0
References
Updated Jul 07, 2026 · Source: OSV.dev | ||
1.0.0
major
1 CVE
CVE-2026-24408
PYSEC-2026-1924
GHSA-hm8f-75xx-w2vr
Jul 07, 2026
sigstore CSRF possibility in OIDC authentication during signing
0.0
/ 10
None
Network
High
None
Required
Unchanged
None
None
None
SummaryThe sigstore-python OAuth authentication flow is susceptible to Cross-Site Request Forgery. Details
Fix should be fairly trivial. ImpactThis 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. Affected versions
0.0.1rc1
0.0.1rc2
0.0.1rc3
0.1.0
0.10.0
0.2.0
0.3.1
0.4.0
0.4.1
0.4.2
0.5.0
0.5.1
+ 50 more Show less
0.5.1rc1
0.5.1rc2
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.8.3
0.9.0
1.0.0
1.0.0rc1
1.1.0
1.1.1
1.1.1rc1
1.1.2
1.1.2rc1
2.0.0
2.0.0rc1
2.0.0rc2
2.0.0rc3
2.0.1
2.1.0
2.1.2
2.1.3
2.1.5
3.0.0
3.0.0rc1
3.0.0rc2
3.1.0
3.2.0
3.3.0
3.4.0
3.5.0
3.5.1
3.5.3
3.5.6
3.6.0
3.6.1
3.6.2
3.6.3
3.6.4
3.6.5
3.6.6
3.6.7
4.0.0
4.1.0
Fixed in
4.2.0
References
Updated Jul 07, 2026 · Source: OSV.dev | ||
1.0.0rc1
pre
1 CVE
CVE-2026-24408
PYSEC-2026-1924
GHSA-hm8f-75xx-w2vr
Jul 07, 2026
sigstore CSRF possibility in OIDC authentication during signing
0.0
/ 10
None
Network
High
None
Required
Unchanged
None
None
None
SummaryThe sigstore-python OAuth authentication flow is susceptible to Cross-Site Request Forgery. Details
Fix should be fairly trivial. ImpactThis 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. Affected versions
0.0.1rc1
0.0.1rc2
0.0.1rc3
0.1.0
0.10.0
0.2.0
0.3.1
0.4.0
0.4.1
0.4.2
0.5.0
0.5.1
+ 50 more Show less
0.5.1rc1
0.5.1rc2
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.8.3
0.9.0
1.0.0
1.0.0rc1
1.1.0
1.1.1
1.1.1rc1
1.1.2
1.1.2rc1
2.0.0
2.0.0rc1
2.0.0rc2
2.0.0rc3
2.0.1
2.1.0
2.1.2
2.1.3
2.1.5
3.0.0
3.0.0rc1
3.0.0rc2
3.1.0
3.2.0
3.3.0
3.4.0
3.5.0
3.5.1
3.5.3
3.5.6
3.6.0
3.6.1
3.6.2
3.6.3
3.6.4
3.6.5
3.6.6
3.6.7
4.0.0
4.1.0
Fixed in
4.2.0
References
Updated Jul 07, 2026 · Source: OSV.dev | ||
0.10.0
minor
1 CVE
CVE-2026-24408
PYSEC-2026-1924
GHSA-hm8f-75xx-w2vr
Jul 07, 2026
sigstore CSRF possibility in OIDC authentication during signing
0.0
/ 10
None
Network
High
None
Required
Unchanged
None
None
None
SummaryThe sigstore-python OAuth authentication flow is susceptible to Cross-Site Request Forgery. Details
Fix should be fairly trivial. ImpactThis 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. Affected versions
0.0.1rc1
0.0.1rc2
0.0.1rc3
0.1.0
0.10.0
0.2.0
0.3.1
0.4.0
0.4.1
0.4.2
0.5.0
0.5.1
+ 50 more Show less
0.5.1rc1
0.5.1rc2
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.8.3
0.9.0
1.0.0
1.0.0rc1
1.1.0
1.1.1
1.1.1rc1
1.1.2
1.1.2rc1
2.0.0
2.0.0rc1
2.0.0rc2
2.0.0rc3
2.0.1
2.1.0
2.1.2
2.1.3
2.1.5
3.0.0
3.0.0rc1
3.0.0rc2
3.1.0
3.2.0
3.3.0
3.4.0
3.5.0
3.5.1
3.5.3
3.5.6
3.6.0
3.6.1
3.6.2
3.6.3
3.6.4
3.6.5
3.6.6
3.6.7
4.0.0
4.1.0
Fixed in
4.2.0
References
Updated Jul 07, 2026 · Source: OSV.dev | ||
0.9.0
minor
1 CVE
CVE-2026-24408
PYSEC-2026-1924
GHSA-hm8f-75xx-w2vr
Jul 07, 2026
sigstore CSRF possibility in OIDC authentication during signing
0.0
/ 10
None
Network
High
None
Required
Unchanged
None
None
None
SummaryThe sigstore-python OAuth authentication flow is susceptible to Cross-Site Request Forgery. Details
Fix should be fairly trivial. ImpactThis 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. Affected versions
0.0.1rc1
0.0.1rc2
0.0.1rc3
0.1.0
0.10.0
0.2.0
0.3.1
0.4.0
0.4.1
0.4.2
0.5.0
0.5.1
+ 50 more Show less
0.5.1rc1
0.5.1rc2
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.8.3
0.9.0
1.0.0
1.0.0rc1
1.1.0
1.1.1
1.1.1rc1
1.1.2
1.1.2rc1
2.0.0
2.0.0rc1
2.0.0rc2
2.0.0rc3
2.0.1
2.1.0
2.1.2
2.1.3
2.1.5
3.0.0
3.0.0rc1
3.0.0rc2
3.1.0
3.2.0
3.3.0
3.4.0
3.5.0
3.5.1
3.5.3
3.5.6
3.6.0
3.6.1
3.6.2
3.6.3
3.6.4
3.6.5
3.6.6
3.6.7
4.0.0
4.1.0
Fixed in
4.2.0
References
Updated Jul 07, 2026 · Source: OSV.dev | ||
0.8.3
minor
1 CVE
CVE-2026-24408
PYSEC-2026-1924
GHSA-hm8f-75xx-w2vr
Jul 07, 2026
sigstore CSRF possibility in OIDC authentication during signing
0.0
/ 10
None
Network
High
None
Required
Unchanged
None
None
None
SummaryThe sigstore-python OAuth authentication flow is susceptible to Cross-Site Request Forgery. Details
Fix should be fairly trivial. ImpactThis 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. Affected versions
0.0.1rc1
0.0.1rc2
0.0.1rc3
0.1.0
0.10.0
0.2.0
0.3.1
0.4.0
0.4.1
0.4.2
0.5.0
0.5.1
+ 50 more Show less
0.5.1rc1
0.5.1rc2
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.8.3
0.9.0
1.0.0
1.0.0rc1
1.1.0
1.1.1
1.1.1rc1
1.1.2
1.1.2rc1
2.0.0
2.0.0rc1
2.0.0rc2
2.0.0rc3
2.0.1
2.1.0
2.1.2
2.1.3
2.1.5
3.0.0
3.0.0rc1
3.0.0rc2
3.1.0
3.2.0
3.3.0
3.4.0
3.5.0
3.5.1
3.5.3
3.5.6
3.6.0
3.6.1
3.6.2
3.6.3
3.6.4
3.6.5
3.6.6
3.6.7
4.0.0
4.1.0
Fixed in
4.2.0
References
Updated Jul 07, 2026 · Source: OSV.dev | ||
0.7.0
minor
1 CVE
CVE-2026-24408
PYSEC-2026-1924
GHSA-hm8f-75xx-w2vr
Jul 07, 2026
sigstore CSRF possibility in OIDC authentication during signing
0.0
/ 10
None
Network
High
None
Required
Unchanged
None
None
None
SummaryThe sigstore-python OAuth authentication flow is susceptible to Cross-Site Request Forgery. Details
Fix should be fairly trivial. ImpactThis 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. Affected versions
0.0.1rc1
0.0.1rc2
0.0.1rc3
0.1.0
0.10.0
0.2.0
0.3.1
0.4.0
0.4.1
0.4.2
0.5.0
0.5.1
+ 50 more Show less
0.5.1rc1
0.5.1rc2
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.8.3
0.9.0
1.0.0
1.0.0rc1
1.1.0
1.1.1
1.1.1rc1
1.1.2
1.1.2rc1
2.0.0
2.0.0rc1
2.0.0rc2
2.0.0rc3
2.0.1
2.1.0
2.1.2
2.1.3
2.1.5
3.0.0
3.0.0rc1
3.0.0rc2
3.1.0
3.2.0
3.3.0
3.4.0
3.5.0
3.5.1
3.5.3
3.5.6
3.6.0
3.6.1
3.6.2
3.6.3
3.6.4
3.6.5
3.6.6
3.6.7
4.0.0
4.1.0
Fixed in
4.2.0
References
Updated Jul 07, 2026 · Source: OSV.dev | ||
0.6.8
patch
1 CVE
CVE-2026-24408
PYSEC-2026-1924
GHSA-hm8f-75xx-w2vr
Jul 07, 2026
sigstore CSRF possibility in OIDC authentication during signing
0.0
/ 10
None
Network
High
None
Required
Unchanged
None
None
None
SummaryThe sigstore-python OAuth authentication flow is susceptible to Cross-Site Request Forgery. Details
Fix should be fairly trivial. ImpactThis 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. Affected versions
0.0.1rc1
0.0.1rc2
0.0.1rc3
0.1.0
0.10.0
0.2.0
0.3.1
0.4.0
0.4.1
0.4.2
0.5.0
0.5.1
+ 50 more Show less
0.5.1rc1
0.5.1rc2
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.8.3
0.9.0
1.0.0
1.0.0rc1
1.1.0
1.1.1
1.1.1rc1
1.1.2
1.1.2rc1
2.0.0
2.0.0rc1
2.0.0rc2
2.0.0rc3
2.0.1
2.1.0
2.1.2
2.1.3
2.1.5
3.0.0
3.0.0rc1
3.0.0rc2
3.1.0
3.2.0
3.3.0
3.4.0
3.5.0
3.5.1
3.5.3
3.5.6
3.6.0
3.6.1
3.6.2
3.6.3
3.6.4
3.6.5
3.6.6
3.6.7
4.0.0
4.1.0
Fixed in
4.2.0
References
Updated Jul 07, 2026 · Source: OSV.dev | ||
0.6.7
patch
1 CVE
CVE-2026-24408
PYSEC-2026-1924
GHSA-hm8f-75xx-w2vr
Jul 07, 2026
sigstore CSRF possibility in OIDC authentication during signing
0.0
/ 10
None
Network
High
None
Required
Unchanged
None
None
None
SummaryThe sigstore-python OAuth authentication flow is susceptible to Cross-Site Request Forgery. Details
Fix should be fairly trivial. ImpactThis 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. Affected versions
0.0.1rc1
0.0.1rc2
0.0.1rc3
0.1.0
0.10.0
0.2.0
0.3.1
0.4.0
0.4.1
0.4.2
0.5.0
0.5.1
+ 50 more Show less
0.5.1rc1
0.5.1rc2
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.8.3
0.9.0
1.0.0
1.0.0rc1
1.1.0
1.1.1
1.1.1rc1
1.1.2
1.1.2rc1
2.0.0
2.0.0rc1
2.0.0rc2
2.0.0rc3
2.0.1
2.1.0
2.1.2
2.1.3
2.1.5
3.0.0
3.0.0rc1
3.0.0rc2
3.1.0
3.2.0
3.3.0
3.4.0
3.5.0
3.5.1
3.5.3
3.5.6
3.6.0
3.6.1
3.6.2
3.6.3
3.6.4
3.6.5
3.6.6
3.6.7
4.0.0
4.1.0
Fixed in
4.2.0
References
Updated Jul 07, 2026 · Source: OSV.dev | ||
0.6.6
patch
1 CVE
CVE-2026-24408
PYSEC-2026-1924
GHSA-hm8f-75xx-w2vr
Jul 07, 2026
sigstore CSRF possibility in OIDC authentication during signing
0.0
/ 10
None
Network
High
None
Required
Unchanged
None
None
None
SummaryThe sigstore-python OAuth authentication flow is susceptible to Cross-Site Request Forgery. Details
Fix should be fairly trivial. ImpactThis 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. Affected versions
0.0.1rc1
0.0.1rc2
0.0.1rc3
0.1.0
0.10.0
0.2.0
0.3.1
0.4.0
0.4.1
0.4.2
0.5.0
0.5.1
+ 50 more Show less
0.5.1rc1
0.5.1rc2
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.8.3
0.9.0
1.0.0
1.0.0rc1
1.1.0
1.1.1
1.1.1rc1
1.1.2
1.1.2rc1
2.0.0
2.0.0rc1
2.0.0rc2
2.0.0rc3
2.0.1
2.1.0
2.1.2
2.1.3
2.1.5
3.0.0
3.0.0rc1
3.0.0rc2
3.1.0
3.2.0
3.3.0
3.4.0
3.5.0
3.5.1
3.5.3
3.5.6
3.6.0
3.6.1
3.6.2
3.6.3
3.6.4
3.6.5
3.6.6
3.6.7
4.0.0
4.1.0
Fixed in
4.2.0
References
Updated Jul 07, 2026 · Source: OSV.dev | ||
0.6.5
patch
1 CVE
CVE-2026-24408
PYSEC-2026-1924
GHSA-hm8f-75xx-w2vr
Jul 07, 2026
sigstore CSRF possibility in OIDC authentication during signing
0.0
/ 10
None
Network
High
None
Required
Unchanged
None
None
None
SummaryThe sigstore-python OAuth authentication flow is susceptible to Cross-Site Request Forgery. Details
Fix should be fairly trivial. ImpactThis 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. Affected versions
0.0.1rc1
0.0.1rc2
0.0.1rc3
0.1.0
0.10.0
0.2.0
0.3.1
0.4.0
0.4.1
0.4.2
0.5.0
0.5.1
+ 50 more Show less
0.5.1rc1
0.5.1rc2
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.8.3
0.9.0
1.0.0
1.0.0rc1
1.1.0
1.1.1
1.1.1rc1
1.1.2
1.1.2rc1
2.0.0
2.0.0rc1
2.0.0rc2
2.0.0rc3
2.0.1
2.1.0
2.1.2
2.1.3
2.1.5
3.0.0
3.0.0rc1
3.0.0rc2
3.1.0
3.2.0
3.3.0
3.4.0
3.5.0
3.5.1
3.5.3
3.5.6
3.6.0
3.6.1
3.6.2
3.6.3
3.6.4
3.6.5
3.6.6
3.6.7
4.0.0
4.1.0
Fixed in
4.2.0
References
Updated Jul 07, 2026 · Source: OSV.dev | ||
0.6.4
patch
1 CVE
CVE-2026-24408
PYSEC-2026-1924
GHSA-hm8f-75xx-w2vr
Jul 07, 2026
sigstore CSRF possibility in OIDC authentication during signing
0.0
/ 10
None
Network
High
None
Required
Unchanged
None
None
None
SummaryThe sigstore-python OAuth authentication flow is susceptible to Cross-Site Request Forgery. Details
Fix should be fairly trivial. ImpactThis 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. Affected versions
0.0.1rc1
0.0.1rc2
0.0.1rc3
0.1.0
0.10.0
0.2.0
0.3.1
0.4.0
0.4.1
0.4.2
0.5.0
0.5.1
+ 50 more Show less
0.5.1rc1
0.5.1rc2
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.8.3
0.9.0
1.0.0
1.0.0rc1
1.1.0
1.1.1
1.1.1rc1
1.1.2
1.1.2rc1
2.0.0
2.0.0rc1
2.0.0rc2
2.0.0rc3
2.0.1
2.1.0
2.1.2
2.1.3
2.1.5
3.0.0
3.0.0rc1
3.0.0rc2
3.1.0
3.2.0
3.3.0
3.4.0
3.5.0
3.5.1
3.5.3
3.5.6
3.6.0
3.6.1
3.6.2
3.6.3
3.6.4
3.6.5
3.6.6
3.6.7
4.0.0
4.1.0
Fixed in
4.2.0
References
Updated Jul 07, 2026 · Source: OSV.dev |