Menu

Star on GitHub · 3.2k

CVE-2026-24408

0.0 · NONE

sigstore-python is a Python tool for generating and verifying Sigstore signatures.

Published Jan 26, 2026CWE-352EPSS 0.18%

Overview

CVE-2026-24408 is a none-severity vulnerability. It was published on January 26, 2026 and has a CVSS 3.1 base score of 0.0 (NONE).

This vulnerability has a CVSS 3.1 base score of 0.0, rated NONE. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

Technical description

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.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-24408?

CVE-2026-24408 is a none-severity vulnerability. It was published on January 26, 2026 and has a CVSS 3.1 base score of 0.0 (NONE).

How severe is CVE-2026-24408?

This vulnerability has a CVSS 3.1 base score of 0.0, rated NONE. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2026-24408?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-24408?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-24408 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related NONE CVEs from 2026

View all