BREW-GGSHIELD-CVE-2026-24408 (GHSA-HM8F-75XX-W2VR)

Vulnerability from osv_homebrew – Published: 2026-08-13 16:50 – Updated: 2026-09-10 00:00 – Source website
VLAI
Summary
sigstore CSRF possibility in OIDC authentication during signing
Details

Summary

The sigstore-python OAuth authentication flow is susceptible to Cross-Site Request Forgery.

Details

_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.

Fix should be fairly trivial.

Impact

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.

Severity
0.0 (None)
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:N
References
To clipboard 

{
  "affected": [
    {
      "ecosystem_specific": {
        "fix": "bump",
        "range_state": "fixed",
        "resource": "sigstore",
        "resource_purl": "pkg:pypi/sigstore@4.5.0",
        "upstream_fixed_in": "4.2.0"
      },
      "package": {
        "ecosystem": "Homebrew",
        "name": "ggshield",
        "purl": "pkg:brew/ggshield"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "1.53.0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "database_specific": {
    "confidence": "high",
    "source": "matched",
    "strategy": "registry",
    "upstream_evidence": [
      {
        "ecosystem": "PyPI",
        "key": "pkg:pypi/sigstore@4.5.0",
        "name": "sigstore",
        "resource": "sigstore",
        "strategy": "registry",
        "subject_version": "4.5.0"
      }
    ]
  },
  "details": "### Summary\n\nThe sigstore-python OAuth authentication flow is susceptible to Cross-Site Request Forgery.\n\n### Details\n\n`_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. \n\nFix should be fairly trivial.\n\n### Impact\n\nThis 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.",
  "id": "BREW-ggshield-CVE-2026-24408",
  "modified": "2026-09-10T00:00:10Z",
  "published": "2026-08-13T16:50:00Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/sigstore/sigstore-python/security/advisories/GHSA-hm8f-75xx-w2vr"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-24408"
    },
    {
      "type": "WEB",
      "url": "https://github.com/sigstore/sigstore-python/commit/5e77497fe8f0b202bdd118949074ec2f20da69aa"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/sigstore/sigstore-python"
    },
    {
      "type": "WEB",
      "url": "https://github.com/sigstore/sigstore-python/releases/tag/v4.2.0"
    }
  ],
  "schema_version": "1.7.3",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:N",
      "type": "CVSS_V3"
    }
  ],
  "summary": "sigstore CSRF possibility in OIDC authentication during signing",
  "upstream": [
    "GHSA-hm8f-75xx-w2vr",
    "CVE-2026-24408",
    "PYSEC-2026-1924"
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.



Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.