<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-02T12:23:02.695664+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/brew-sigstore-cve-2026-24408</id>
    <title>BREW-sigstore-CVE-2026-24408 — sigstore has CSRF possibility in OIDC authentication during signing</title>
    <updated>2026-10-02T12:23:02.697711+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Homebrew: sigstore</p>
<p>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.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/brew-sigstore-cve-2026-24408"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cve-2026-24408</id>
    <title>CVE-2026-24408 — sigstore has CSRF possibility in OIDC authentication during signing</title>
    <updated>2026-10-02T12:23:02.697761+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> sigstore-python</p>
<p>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.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2026-24408"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-hm8f-75xx-w2vr</id>
    <title>GHSA-hm8f-75xx-w2vr — sigstore CSRF possibility in OIDC authentication during signing</title>
    <updated>2026-10-02T12:23:02.697792+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: sigstore</p>
<p>### Summary</p>
<p>The sigstore-python OAuth authentication flow is susceptible to Cross-Site Request Forgery.</p>
<p>### Details</p>
<p>`_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.</p>
<p>Fix should be fairly trivial.</p>
<p>### Impact</p>
<p>This 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.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-hm8f-75xx-w2vr"/>
  </entry>
</feed>
