{"answers":{"affected":"3 open source packages ship an affected version, including sigstore. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-24408 in the wild and no public exploit code.","fix":"Upgrade sigstore to 4.2.0 or later.","what":"CVE-2026-24408 is a vulnerability in sigstore-python, published on 26 Jan 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-24408 and fix it if it is affected.\n\nWhat it is: CVE-2026-24408 is a vulnerability in sigstore-python, published on 26 Jan 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-24408 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- sigstore (PyPI): affected all versions; fixed in 4.2.0\n- sigstore (PyPI): affected all versions; fixed in 4.2.0\n- sigstore (PyPI): affected all versions; fixed in 4.2.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-24408/ (Markdown: https://insights.sbomify.com/CVE-2026-24408/index.md)","id":"CVE-2026-24408","markdown":"https://insights.sbomify.com/CVE-2026-24408/index.md","name":"CVE-2026-24408","record":{"aliases":["GHSA-hm8f-75xx-w2vr","PYSEC-2026-1924","openSUSE-SU-2026:10104-1"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Python signing library","requires_auth":"none","summary":"Attackers can exploit missing state validation in OAuth flows to perform Cross-Site Request Forgery, potentially compromising user accounts during signing operations.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"sigstore-python","vendor":"linuxfoundation"}],"cvss":{"score":0,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"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.","ecosystems":["PyPI","openSUSE:Tumbleweed"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"sigstore has CSRF possibility in OIDC authentication during signing","id":"CVE-2026-24408","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"csrf","year":"2026"},"n_packages":4,"n_references":3,"next":{"headline":"iccDEV has Undefined Behavior and Null Pointer Deference in CIccTagXmlFloatNum\u003c\u003e::ParseXml()","id":"CVE-2026-24409"},"packages":[{"ecosystem":"PyPI","fixed":["4.2.0"],"introduced":["0"],"last_affected":[],"package":"sigstore","purl":null,"source":"GHSA-hm8f-75xx-w2vr"},{"ecosystem":"PyPI","fixed":["4.2.0"],"introduced":["0"],"last_affected":[],"package":"sigstore","purl":"pkg:pypi/sigstore","source":"GHSA-hm8f-75xx-w2vr"},{"ecosystem":"PyPI","fixed":["4.2.0"],"introduced":["0"],"last_affected":[],"package":"sigstore","purl":"pkg:pypi/sigstore","source":"PYSEC-2026-1924"},{"ecosystem":"openSUSE:Tumbleweed","fixed":["4.2.0-1.1"],"introduced":["0"],"last_affected":[],"package":"python-sigstore","purl":"pkg:rpm/opensuse/python-sigstore\u0026distro=openSUSE%20Tumbleweed","source":"openSUSE-SU-2026:10104-1"}],"prev":{"headline":"iccDEV has Undefined Behavior in icSigCalcOp()","id":"CVE-2026-24407"},"products":["sigstore-python"],"published":"2026-01-26","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"CC BY 4.0","name":"SUSE","prefix":"openSUSE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-01-27","vendors":["sigstore"]},"summary":"Attackers can exploit missing state validation in OAuth flows to perform Cross-Site Request Forgery, potentially compromising user accounts during signing operations.","url":"https://insights.sbomify.com/CVE-2026-24408/"}