N/A

CVSS Score

3.1

-

CVSS Score

Basic Information

Concerned about an active attack path?

Talk to our security experts and see Miggo in action.

Miggo Vulnerability Database

→

CVE-2026-24408

CVE-2026-24408: sigstore has CSRF possibility in OIDC authentication during signing

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.

(GitHub Advisory)

Miggo Vulnerability Database

→

CVE-2026-24408

CVE-2026-24408:

N/A

CVSS Score

3.1

-

CVSS Score

Basic Information

Is this CVE running in your environment?

Easily map the attack path and prioritize which CVEs are a threat to your organization

Validate Exposure

Technical Details

Package Name	Ecosystem	Vulnerable Versions	First Patched Version
sigstore	pip	< 4.2.0	4.2.0

Technical Details

Vulnerability Intelligence
Miggo AI

Root Cause Analysis

The vulnerability lies in the OIDC authentication flow of sigstore-python, specifically within the identity_token function in sigstore/oidc.py. The core of the issue is a missing validation of the state parameter, which is a crucial defense against Cross-Site Request Forgery (CSRF) in OAuth 2.0 and OIDC flows.

The _OAuthSession class generates a unique, unguessable state value for each authentication request. This value is sent to the identity provider and should be returned unmodified in the response. The client must then verify that the returned state matches the one it originally sent.

The provided patch introduces this missing validation in the identity_token function. The added lines of code compare the state from the authentication server's response with the state stored in the local session (server.oauth_session.state). If they do not match, it raises an IdentityError, effectively preventing the CSRF attack.

Therefore, the sigstore.oidc.identity_token function is the vulnerable function, as it was the component that failed to perform this critical security check. During exploitation, this function would be called to complete the OIDC flow, and without the patch, it would improperly trust the authentication response, leading to the vulnerability.

Vulnerable functions

sigstore.oidc.identity_token

sigstore/oidc.py

The `identity_token` function is responsible for handling the OIDC authentication flow. Before the patch, it did not validate the `state` parameter returned by the identity provider against the state sent in the initial request. This omission allows for a Cross-Site Request Forgery (CSRF) attack, where an attacker could trick a user into completing an authentication flow initiated by the attacker, potentially leading to the user signing artifacts with an identity controlled by the attacker.

Vulnerability Intelligence
Miggo AI

Unlock WAF rules for this CVE

Generate vendor-ready rules for the observed attack patterns, plus reasoning and safe deployment guidance

Get WAF rules

WAF Protection Rules

WAF Rule

W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.

Reasoning

*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.