CVE-2026-29785 | nats-io nats-server up to 2.11.13/2.12.4 null pointer dereference (GHSA-52jh-2xxh-pwh6)

VDB-353505 · CVE-2026-29785 · GHSA-52JH-2XXH-PWH6 NATS-IO NATS-SERVER UP TO 2.11.13/2.12.4 NULL POINTER DEREFERENCE HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 6.3 $0-$5k 1.93+ Summaryinfo A vulnerability was found in nats-io nats-server up to 2.11.13/2.12.4. It has been classified as problematic. This impacts an unknown function. Performing a manipulation results in null pointer dereference. This vulnerability is known as CVE-2026-29785. Remote exploitation of the attack is possible. No exploit is available. Upgrading the affected component is recommended. Detailsinfo A vulnerability, which was classified as problematic, was found in nats-io nats-server up to 2.11.13/2.12.4. This affects an unknown code block. The manipulation with an unknown input leads to a null pointer dereference vulnerability. CWE is classifying the issue as CWE-476. A NULL pointer dereference occurs when the application dereferences a pointer that it expects to be valid, but is NULL, typically causing a crash or exit. This is going to have an impact on availability. The summary by CVE is: NATS-Server is a High-Performance server for NATS.io, a cloud and edge native messaging system. Prior to versions 2.11.14 and 2.12.5, if the nats-server has the "leafnode" configuration enabled (not default), then anyone who can connect can crash the nats-server by triggering a panic. This happens pre-authentication and requires that compression be enabled (which it is, by default, when leafnodes are used). Versions 2.11.14 and 2.12.5 contain a fix. As a workaround, disable compression on the leafnode port. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-29785 since 03/04/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. Upgrading to version 2.11.14 or 2.12.5 eliminates this vulnerability. Applying the patch a1488de6f2ba6e666aef0f9cce0016f7f167d6a8 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version. Productinfo Vendor nats-io Name nats-server Version 2.11.0 2.11.1 2.11.2 2.11.3 2.11.4 2.11.5 2.11.6 2.11.7 2.11.8 2.11.9 2.11.10 2.11.11 2.11.12 2.11.13 2.12.0 2.12.1 2.12.2 2.12.3 2.12.4 License open-source Website Product: https://github.com/nats-io/nats-server/ CPE 2.3info 🔒 🔒 🔒 CPE 2.2info 🔒 🔒 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv3info VulDB Meta Base Score: 6.4 VulDB Meta Temp Score: 6.3 VulDB Base Score: 5.3 VulDB Temp Score: 5.1 VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA Base Score: 7.5 CNA Vector (GitHub_M): 🔒 CVSSv2info Vector Complexity Authentication Confidentiality Integrity Availability Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock VulDB Base Score: 🔒 VulDB Temp Score: 🔒 VulDB Reliability: 🔍 Exploitinginfo Class: Null pointer dereference CWE: CWE-476 / CWE-404 CAPEC: 🔒 ATT&CK: 🔒 Physical: No Local: No Remote: Yes Availability: 🔒 Status: Not defined Price Prediction: 🔍 Current Price Estimation: 🔒 0-Day Unlock Unlock Unlock Unlock Today Unlock Unlock Unlock Unlock Threat Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: Upgrade Status: 🔍 0-Day Time: 🔒 Upgrade: nats-server 2.11.14/2.12.5 Patch: a1488de6f2ba6e666aef0f9cce0016f7f167d6a8 Timelineinfo 03/04/2026 CVE reserved 03/25/2026 +21 days Advisory disclosed 03/25/2026 +0 days VulDB entry created 03/25/2026 +0 days VulDB entry last update Sourcesinfo Product: github.com Advisory: GHSA-52jh-2xxh-pwh6 Status: Confirmed CVE: CVE-2026-29785 (🔒) GCVE (CVE): GCVE-0-2026-29785 GCVE (VulDB): GCVE-100-353505 Entryinfo Created: 03/25/2026 23:02 Changes: 03/25/2026 23:02 (66) Complete: 🔍 Cache ID: 99:FAB:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸