# NATS v2.12.10 — Release v2.12.10 - Product: NATS (https://whatsnew.fyi/product/nats) - Vendor: Synadia - Date: 2026-06-02 - Version: v2.12.10 - Original notes: https://github.com/nats-io/nats-server/releases/tag/v2.12.10 - Permalink: https://whatsnew.fyi/product/nats/releases/v2.12.10 What's New is an index, not a publisher: every entry below links to the vendor's own release notes, which are the authoritative source. Entries are labelled where they are hand-curated sample data, pre-releases, or drawn from a secondary source such as a developer blog. Reuse: release facts (products, versions, dates, links, CVE ids and flags) are open data under CC BY 4.0, from the API at https://whatsnew.fyi/api/v1 or the nightly dataset at https://github.com/whatsnew-fyi/dataset. The summaries, labels and curation are © What's New: quote freely with attribution and a link back; wholesale republication of them is not permitted — terms: https://whatsnew.fyi/terms. The vendors' own release notes remain their publishers'. --- - **added** — The client ID is now available through the embedded ClientAuthentication API - **fixed** — A race condition when handling subscription interest over routes has been fixed - **fixed** — Potential protocol-level corruption from rewriting $JS.ACK subjects has been fixed - **fixed** — Potential protocol-level corruption from buffer misuse in compressed WebSocket clients has been fixed - **fixed** — The /accstatz monitoring endpoint no longer omits accounts with only leaf connections - **fixed** — Fixed a case where Raft peers were not correctly tracked after an inactivity stall during catchup - **fixed** — Quorum needed is now calculated correctly when bootstrapping the metalayer when gateway URLs resolve to multiple IP addresses - **fixed** — The filestore no longer performs a block skip check on streams with extremely high subject counts, as it could result in runaway CPU usage - **fixed** — Purge operations on both file and memory stores are now more consistent with each other - **fixed** — Counter streams and message schedules now have configuration constraints applied to prevent incorrect usage patterns - **changed** — Improved stream and consumer scale down behaviour consistency - **fixed** — Fixed an issue where the per-subject state last block was not stored correctly with a max messages per subject limit of 1 - **fixed** — Fixed a drift that could occur in the peer sets after a peer remove of an online node ##### Changelog Refer to the [2.12 Upgrade Guide](https://docs.nats.io/release-notes/whats_new/whats_new_212) for backwards compatibility notes with 2.11.x. ###### Go Version - 1.25.10 ###### Dependencies - golang.org/x/crypto v0.52.0 - golang.org/x/sys v0.45.0 - github.com/nats-io/jwt/v2 v2.8.2 - github.com/nats-io/nkeys v0.4.16 ###### Improved General - The client ID is now available through the embedded `ClientAuthentication` API (#8217) ###### Fixed General - A race condition when handling subscription interest over routes has been fixed (#8235) - Potential protocol-level corruption from rewriting `$JS.ACK` subjects has been fixed (#8242) - Potential protocol-level corruption from buffer misuse in compressed WebSocket clients has been fixed (#8244) - The `/accstatz` monitoring endpoint no longer omits accounts with only leaf connections (#8252) JetStream - Fixed a case where Raft peers were not correctly tracked after an inactivity stall during catchup (#8226) - Quorum needed is now calculated correctly when bootstrapping the metalayer when gateway URLs resolve to multiple IP addresses (#8238) - The filestore no longer performs a block skip check on streams with extremely high subject counts, as it could result in runaway CPU usage (#8227) - Purge operations on both file and memory stores are now more consistent with each other (#8241) - Counter streams and message schedules now have configuration constraints applied to prevent incorrect usage patterns (#8240) - Improved stream and consumer scale down behaviour consistency (#8253) - Fixed an issue where the per-subject state last block was not stored correctly with a max messages per subject limit of 1 (#8254) - Fixed a drift that could occur in the peer sets after a peer remove of an online node (#8258) ###### Complete Changes https://github.com/nats-io/nats-server/compare/v2.12.9...v2.12.10