Advisory record · GHSA-qjwp-hrq6-r26r

kas checks out SHA-like git branches as valid commits

CVSS 2.1 LowEPSS 0.0025 · 15th percentile

Published by the GitHub Advisory Database at 1 Jun 2026, 14:26 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
kasPyPI<5.35.3
Identifiers
GHSA-qjwp-hrq6-r26r · CVE-2026-47191 · PYSEC-2026-2544
Weakness (CWE)
CWE-347
Published
1 Jun 2026
Updated
15 Aug 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Packages affected: kas before 5.3, fixed in 5.3. An attacker who has taken over a git repository used in a kas configuration can add a branch named like a commit ID. Because kas checks out by commit ID alone, a user may end up on that branch instead of the validated commit, with the SHA-256 case being the main concern. Upgrade to kas 5.3. Where possible, use signed commits or tags, or mirror the repository and verify it before use.

Written 5 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
2.1 Low 4.0 CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0025, the 15th percentile, on 12 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:40 UTC First seen by agentprime
  2. 31 Oct 2026, 14:40 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.