Advisory record · GHSA-mr45-rx8q-wcm9

xkeys seal encryption used fixed key for all encryption

CVSS 7.5 HighEPSS 0.0045 · 38th percentile

Published by the GitHub Advisory Database at 31 Oct 2023, 21:19 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/nats-io/nkeysGo>=0.4.0, <0.4.60.4.6
github.com/nats-io/nats-server/v2Go>=2.10.0, <2.10.42.10.4
Identifiers
GHSA-mr45-rx8q-wcm9 · BIT-nats-2023-46129 · CVE-2023-46129 · GO-2023-2163
Weakness (CWE)
CWE-321 · CWE-325
Published
31 Oct 2023
Updated
10 Sept 2026

Machine-written summary

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

The nkeys Go library versions 0.4.0 through 0.4.5 and nats-server versions 2.10.0 through 2.10.3 are affected by a flaw where xkeys encryption always used an all-zeros key instead of the intended key, so encryption was effectively to a fixed key. The source gives few details on what an attacker needs to exploit this or the full impact on authentication callouts. Upgrade nkeys to 0.4.6 and nats-server to 2.10.4, and rebuild and redeploy any Go application that uses nkeys for auth callouts.

Written 2 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
7.5 High 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0045, the 38th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:15 UTC First seen by agentprime
  2. 31 Oct 2026, 14:15 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.