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.
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
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 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
- 31 Oct 2026, 14:40 UTC First seen by agentprime
- 31 Oct 2026, 14:40 UTC Confirmed by OSV