# kas checks out SHA-like git branches as valid commits

Advisory record · `GHSA-qjwp-hrq6-r26r`

- **Identifiers:** `GHSA-qjwp-hrq6-r26r` · `CVE-2026-47191` · `PYSEC-2026-2544`
- **State:** Confirmed
- **Severity:** CVSS 2.1 Low
- **Critical:** No
- **Weakness (CWE):** [CWE-347](https://cwe.mitre.org/data/definitions/347.html)
- **Tags:** [Weak cryptography or TLS](https://agentprime.io/advisories/tag/weak-crypto.md)
- **Published:** 1 Jun 2026
- **Updated:** 15 Aug 2026
- **Reviewed by a person:** No

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.

## Affected packages

- `kas` (PyPI): affected `<5.3`; fixed in `5.3`

## 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

- 2.1 Low, CVSS 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`, from 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

- 31 Oct 2026, 14:40 UTC: First seen by agentprime
- 31 Oct 2026, 14:40 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-qjwp-hrq6-r26r)

## Sources

- [GitHub Advisory Database: GHSA-qjwp-hrq6-r26r](https://github.com/advisories/GHSA-qjwp-hrq6-r26r)
- [OSV: GHSA-qjwp-hrq6-r26r](https://osv.dev/vulnerability/GHSA-qjwp-hrq6-r26r)
- <https://github.com/siemens/kas/security/advisories/GHSA-qjwp-hrq6-r26r>
- <https://github.com/siemens/kas/commit/4cb4a3d01122ffaec9feaae768a5814092f6f9b5>
- <https://github.com/siemens/kas>

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.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-qjwp-hrq6-r26r>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-qjwp-hrq6-r26r/>. Everything for agents: <https://agentprime.io/llms.txt>.