Vulnerabilities in pkg:golang/github.com/tillitis/tkeyclient

PACKAGE
Advisory Identifier: GHSA-4w7r-3222-8h6v
Advisory Summary

CVE-2026-32953 is a MODERATE tillitis tkey client has an vulnerability (CWE-303: Incorrect Implementation of Authentication Algorithm) affecting Github.com/tillitis/tkeyclient libraries in the Go ecosystem. The issue involves tillitis tkey client has an error in protocol implementation. Remediation is available by upgrading affected packages to version 1.3.0.

1 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:golang/github.com/tillitis/tkeyclient

1 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:golang/github.com/tillitis/tkeyclient. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-4w7r-3222-8h6v CVE-2026-32953 MODERATE Tillitis TKey Client has an Error in Protocol Implementation

CVE-2026-32953 at a Glance

CVE Identifier CVE-2026-32953
GHSA Identifier GHSA-4w7r-3222-8h6v
Severity MODERATE
CVSS v3.1 Base Score N/A
CWE Classification CWE-303: Incorrect Implementation of Authentication Algorithm
Affected Product Github.com/tillitis/tkeyclient
Package Ecosystem Go
Published Date
Last Updated

How to Fix CVE-2026-32953

To remediate this vulnerability, upgrade all affected Github.com/tillitis/tkeyclient dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/tillitis/tkeyclient fixed: 1.3.0
Upgrade github.com/tillitis/tkeyclient to 1.3.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/tillitis/tkeyclient

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-32953, inspect your project dependencies for Github.com/tillitis/tkeyclient:

inspect dependencies for github.com/tillitis/tkeyclient

Analyze the terminal output to locate any version of Github.com/tillitis/tkeyclient in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.3.0), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-303: Incorrect Implementation of Authentication Algorithm, where the requirements for the product dictate the use of an established authentication algorithm, but the implementation of the algorithm is incorrect. In Github.com/tillitis/tkeyclient, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## Impact Some specific (1 out of 256) User Supplied Secrets (USS) were not used, making the resulting Compound Device Identifier (CDI) the same as if no USS was provided. Affected client applications: all client apps using the [tkeyclient](https://github.com/tillitis/tkeyclient) Go module. ## Patches Upgrade to v1.3.0. **NOTE WELL**: For the affected end users upgrading an app containing `tkeyclient` to v1.3.0 means their key material will change. An end user can get their old keys by not entering any USS. Please make sure to communicate this to end users. ## Affected users The steps required to assess whether your USS is vulnerable may vary depending on the client application. The example below shows how to perform the check using `tkey-ssh-agent` and the known vulnerable USS `adl`. 1. Insert the TKey into the client 2. Run `tkey-ssh-agent -p --uss` 3. When prompted for a User Supplied Secret, enter `adl` 4. Note the public key and call it `pubkey-with-uss` 5. Remove the TKey from the client 6. Insert the TKey into the client again 7. Run `tkey-ssh-agent -p` 8. Note the public key and call it `pubkey-without-uss` Expected behavior: `pubkey-with-uss` and `pubkey-without-uss` should not be equal. Observed behavior: `pubkey-with-uss` and `pubkey-without-uss` are equal. ## Workaround We recommend everyone using `tkeyclient` to update to v1.3.0 and release new versions of the client apps using it. However, end users that are unable to upgrade to a new version of a client app, the recommendation is to change to an unaffected USS. Include specific instructions for your client app. ## Details When loading the device app an optional 32 bytes USS digest is also sent. The intention is to ask the end user to enter a USS of arbitrary length, hash it, and then send a 32 bytes digest to TKey. However, there was a bug when sending the digest from the client. The index in the outgoing buffer is wrong and overwrites the boolean defining if the USS is used or not. This means that if the USS digest begins with a 0, the rest of the digest is not used at all. If it begins with something else, setting the boolean to true, the USS is used. The exported `LoadApp()` function calls an internal helper function `loadApp()` which contains this code: ```go if len(secretPhrase) == 0 { tx[6] = 0 } else { tx[6] = 1 // Note the 6 here // Hash user's phrase as USS uss := blake2s.Sum256(secretPhrase) copy(tx[6:], uss[:]) // Note that 6 is used again } ``` A side effect of this behavior is that only 31 bytes of the USS are used. This is not considered a security issue, but an option has been added to enforce use of the full USS. See the release notes for details. To avoid forcing all users to roll their keys, this option is disabled by default and must be explicitly enabled. ### The fix The fix focuses on solving the vulnerability only by: 1) use correct index, 2) always use the last 31 bytes of the USS: ```go if len(secretPhrase) == 0 { tx[6] = 0 } else { tx[6] = 1 // Hash user's phrase as USS uss := blake2s.Sum256(secretPhrase) copy(tx[7:], uss[1:]) } ``` This change means the key material of affected end users will change compared to earlier versions of `tkeyclient`. They have the choice of: 1. Not using a USS and keep their keys. 2. Keep using their USS and use new generated keys. 3. Use another USS and thus new keys.

CVE-2026-32953 Affected Github.com/tillitis/tkeyclient Versions

1 component(s)
Fixed Versions:
1.3.0
Product / Package Ecosystem Affected Versions Fixed Version
github.com/tillitis/tkeyclient
Go
< 1.3.0
1.3.0

References

Frequently Asked Questions

What is CVE-2026-32953?
CVE-2026-32953 is a security vulnerability in Github.com/tillitis/tkeyclient involving Tillitis TKey Client has an Error in Protocol Implementation under CWE-303: Incorrect Implementation of Authentication Algorithm.
Which Github.com/tillitis/tkeyclient versions are affected?
Affected versions include releases prior to 1.3.0 across affected packages: github.com/tillitis/tkeyclient.
What version fixes CVE-2026-32953?
Upgrading to 1.3.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/tillitis/tkeyclient affected?
Yes, github.com/tillitis/tkeyclient is affected in releases prior to 1.3.0. Upgrade your dependency to 1.3.0 or later.
What CWE is associated with CVE-2026-32953?
CVE-2026-32953 is classified under CWE-303: Incorrect Implementation of Authentication Algorithm (The requirements for the product dictate the use of an established authentication algorithm, but the implementation of the algorithm is incorrect.).
How can I check Go dependencies for CVE-2026-32953?
Run the dependency tree command: 'inspect dependencies for github.com/tillitis/tkeyclient'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-4w7r-3222-8h6v",
  "modified" : "2026-03-20T21:22:09Z",
  "published" : "2026-03-17T19:42:31Z",
  "aliases" : [ "CVE-2026-32953" ],
  "summary" : "Tillitis TKey Client has an Error in Protocol Implementation",
  "details" : "## Impact\n\nSome specific (1 out of 256) User Supplied Secrets (USS) were not used,\nmaking the resulting Compound Device Identifier (CDI) the same as if no\nUSS was provided.\n\nAffected client applications: all client apps using the\n[tkeyclient](https://github.com/tillitis/tkeyclient) Go module.\n\n## Patches\n\nUpgrade to v1.3.0.\n\n**NOTE WELL**: For the affected end users upgrading an app containing\n`tkeyclient` to v1.3.0 means their key material will change. An end\nuser can get their old keys by not entering any USS. Please make sure\nto communicate this to end users.\n\n## Affected users\n\nThe steps required to assess whether your USS is vulnerable may vary\ndepending on the client application. The example below shows how to\nperform the check using `tkey-ssh-agent` and the known vulnerable USS\n`adl`.\n\n1. Insert the TKey into the client\n2. Run `tkey-ssh-agent -p --uss`\n3. When prompted for a User Supplied Secret, enter `adl`\n4. Note the public key and call it `pubkey-with-uss`\n5. Remove the TKey from the client\n6. Insert the TKey into the client again\n7. Run `tkey-ssh-agent -p`\n8. Note the public key and call it `pubkey-without-uss`\n\nExpected behavior:\n`pubkey-with-uss` and `pubkey-without-uss` should not be equal.\n\nObserved behavior:\n`pubkey-with-uss` and `pubkey-without-uss` are equal.\n\n## Workaround\n\nWe recommend everyone using `tkeyclient` to update to v1.3.0 and\nrelease new versions of the client apps using it.\n\nHowever, end users that are unable to upgrade to a new version of a client\napp, the recommendation is to change to an unaffected USS. Include\nspecific instructions for your client app.\n\n## Details\n\nWhen loading the device app an optional 32 bytes USS digest is also\nsent. The intention is to ask the end user to enter a USS of arbitrary\nlength, hash it, and then send a 32 bytes digest to TKey.\n\nHowever, there was a bug when sending the digest from the client. The\nindex in the outgoing buffer is wrong and overwrites the boolean\ndefining if the USS is used or not.\n\nThis means that if the USS digest begins with a 0, the rest of the\ndigest is not used at all. If it begins with something else, setting\nthe boolean to true, the USS is used.\n\nThe exported `LoadApp()` function calls an internal helper function\n`loadApp()` which contains this code:\n\n```go\n  if len(secretPhrase) == 0 {\n    tx[6] = 0\n  } else {\n    tx[6] = 1 // Note the 6 here\n    // Hash user's phrase as USS\n    uss := blake2s.Sum256(secretPhrase)\n    copy(tx[6:], uss[:]) // Note that 6 is used again\n  }\n```\n\nA side effect of this behavior is that only 31 bytes of the USS are\nused. This is not considered a security issue, but an option has been\nadded to enforce use of the full USS. See the release notes for\ndetails. To avoid forcing all users to roll their keys, this option is\ndisabled by default and must be explicitly enabled.\n\n### The fix\n\nThe fix focuses on solving the vulnerability only by: 1) use correct\nindex, 2) always use the last 31 bytes of the USS:\n\n```go\n  if len(secretPhrase) == 0 {\n    tx[6] = 0\n  } else {\n    tx[6] = 1\n    // Hash user's phrase as USS\n    uss := blake2s.Sum256(secretPhrase)\n    copy(tx[7:], uss[1:])\n  }\n```\n\nThis change means the key material of affected end users will change\ncompared to earlier versions of `tkeyclient`. They have the choice of:\n\n1. Not using a USS and keep their keys.\n2. Keep using their USS and use new generated keys.\n3. Use another USS and thus new keys.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "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"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/tillitis/tkeyclient"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.3.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/tillitis/tkeyclient/security/advisories/GHSA-4w7r-3222-8h6v"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-32953"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/tillitis/tkeyclient/commit/4954dccf0287657edf8d405057e134cdff9c59e8"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/tillitis/tkeyclient"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/tillitis/tkeyclient/releases/tag/v1.3.0"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-303" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-03-17T19:42:31Z",
    "nvd_published_at" : "2026-03-20T05:16:14Z"
  }
}