# xkeys seal encryption used fixed key for all encryption Advisory record · `GHSA-mr45-rx8q-wcm9` - **Identifiers:** `GHSA-mr45-rx8q-wcm9` · `BIT-nats-2023-46129` · `CVE-2023-46129` · `GO-2023-2163` - **State:** Confirmed - **Severity:** CVSS 7.5 High - **Critical:** No - **Weakness (CWE):** [CWE-321](https://cwe.mitre.org/data/definitions/321.html) · [CWE-325](https://cwe.mitre.org/data/definitions/325.html) - **Tags:** [Hard-coded credentials](https://agentprime.io/advisories/tag/hard-coded-credentials.md) · [CWE-325](https://agentprime.io/advisories/tag/cwe-325.md) - **Published:** 31 Oct 2023 - **Updated:** 10 Sept 2026 - **Reviewed by a person:** No 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. ## Affected packages - `github.com/nats-io/nkeys` (Go): affected `>=0.4.0, <0.4.6`; fixed in `0.4.6` - `github.com/nats-io/nats-server/v2` (Go): affected `>=2.10.0, <2.10.4`; fixed in `2.10.4` ## 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 - 7.5 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`, from 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 - 31 Oct 2026, 14:15 UTC: First seen by agentprime - 31 Oct 2026, 14:15 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-mr45-rx8q-wcm9) ## Sources - [GitHub Advisory Database: GHSA-mr45-rx8q-wcm9](https://github.com/advisories/GHSA-mr45-rx8q-wcm9) - [OSV: GHSA-mr45-rx8q-wcm9](https://osv.dev/vulnerability/GHSA-mr45-rx8q-wcm9) - - - - - - - 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 (), 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: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .