LiveActive security incident?Get immediate response
CVE Record

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.

NoneCVSS 0Not KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

CVE-2026-24408 affects sigstore-python before 4.2.0. During OIDC authentication for signing, the tool generated a CSRF “state” value but did not appear to verify the returned value. The published CVSS impact is none, but affected signing workflows should still update because authentication flow integrity matters for software supply-chain trust.

Executive priority

Treat as a low-severity but supply-chain-relevant maintenance update. It does not have documented active exploitation or measured impact in the sources, but signing infrastructure should avoid known authentication-flow weaknesses. Schedule prompt dependency updates where sigstore-python is used for signing.

Technical view

The issue is CWE-352 in sigstore-python’s OAuth authentication flow. `_OAuthSession` creates a unique state parameter for the auth request, but prior to 4.2.0 the response state was apparently not cross-checked. The CVSS vector is AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:N with score 0.0.

Likely exposure

Exposure is limited to environments using sigstore-python versions earlier than 4.2.0, especially where interactive OIDC authentication is used during signing. Projects only verifying signatures, or not using sigstore-python, are not shown as affected by the provided sources.

Exploitation context

The sources describe a CSRF possibility requiring user interaction and high attack complexity. No provided source or KEV listing indicates active exploitation. The published CVSS vector lists no confidentiality, integrity, or availability impact, but the issue still concerns authentication flow correctness.

Researcher notes

The public record is concise. It identifies missing state validation in OAuth handling and points to the 4.2.0 patch commit and release. The CVSS score is 0.0 despite the CWE-352 classification, so researchers should review the patch and advisory before assigning operational risk.

Mitigation direction

  • Upgrade sigstore-python to version 4.2.0 or later.
  • Review vendor advisory GHSA-hm8f-75xx-w2vr for any updated guidance.
  • Prioritize systems performing OIDC-backed signing with sigstore-python.
  • Track dependency manifests for transitive or pinned sigstore-python versions.

Validation and detection

  • Inventory installed sigstore-python versions in build, release, and developer environments.
  • Confirm affected instances are below version 4.2.0.
  • Verify upgraded environments report sigstore-python 4.2.0 or later.
  • Review signing workflows that invoke OIDC authentication.
Prepared
Confidence
high
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-352: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-24408 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
None
CVSS
0 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
0CVSS 3.1NoneCVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:N1.60Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

0None
CVSS 3.1 vector shape for CVE-2026-24408Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
sigstoresigstore-python< 4.2.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.