# Tillitis TKey Client has an Error in Protocol Implementation

Advisory record · `GHSA-4w7r-3222-8h6v`

- **Identifiers:** `GHSA-4w7r-3222-8h6v` · `CVE-2026-32953` · `GO-2026-4728`
- **State:** Confirmed
- **Severity:** CVSS 4.7 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-303](https://cwe.mitre.org/data/definitions/303.html)
- **Tags:** [Authentication bypass](https://agentprime.io/advisories/tag/auth-bypass.md)
- **Published:** 17 Mar 2026
- **Updated:** 23 Mar 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 17 Mar 2026, 19:42 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `github.com/tillitis/tkeyclient` (Go): affected `<1.3.0`; fixed in `1.3.0`

## Machine-written summary

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

> The Go module github.com/tillitis/tkeyclient before 1.3.0 has a bug in how it sends the User Supplied Secret digest to the TKey, so a USS whose digest begins with 0 is ignored and the key material is the same as if no USS was given. Attackers would need to know or guess a vulnerable USS value, such as the example "adl", to get the same keys; the source describes this as an affected-user check rather than a remote attack. Upgrade to version 1.3.0, noting that upgrading changes key material for affected users, who can keep their old keys by not entering a USS.

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

- 4.7 Medium, CVSS 4.0: `CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:H/SI:H/SA:H`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0027, the 19th percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:08 UTC: First seen by agentprime
- 31 Oct 2026, 15:08 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-4w7r-3222-8h6v)

## Sources

- [GitHub Advisory Database: GHSA-4w7r-3222-8h6v](https://github.com/advisories/GHSA-4w7r-3222-8h6v)
- [OSV: GHSA-4w7r-3222-8h6v](https://osv.dev/vulnerability/GHSA-4w7r-3222-8h6v)
- <https://github.com/tillitis/tkeyclient/security/advisories/GHSA-4w7r-3222-8h6v>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-32953>
- <https://github.com/tillitis/tkeyclient/commit/4954dccf0287657edf8d405057e134cdff9c59e8>
- <https://github.com/tillitis/tkeyclient>
- <https://github.com/tillitis/tkeyclient/releases/tag/v1.3.0>

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-4w7r-3222-8h6v>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-4w7r-3222-8h6v/>. Everything for agents: <https://agentprime.io/llms.txt>.
