New from Wiz Research: Critical NGINX flaw. Understand the risk and impact.
Vulnerability DatabaseCVE-2026-125334

CVE-2026-125334: 
Grafana vulnerability analysis and mitigation

Overview

CVE-2026-125334 is a NULL Pointer Dereference (CWE-476) vulnerability in node-forge (also known as Forge), a native JavaScript implementation of Transport Layer Security. A forge.tls client can receive a TLS handshake record while its session is uninitialized — such as after a close_notify alert, after close() is called, or before handshake() is invoked — causing tls.handleHandshake() to dereference a null c.session object and throw an uncaught TypeError that can terminate the Node.js process. All versions of node-forge up to and including 1.4.2 are affected; the issue was fixed in version 1.4.3. It carries a CVSS v3.1 base score of 5.9 (Medium) (Github Advisory). The vulnerability was reported by @manus-use, published to the GitHub Advisory Database on November 10, 2026, and assigned GHSA-j8rw-jp99-435v (Github Advisory).

Technical details

The root cause is a NULL Pointer Dereference (CWE-476) in tls.handleHandshake() within lib/tls.js. Before dispatching any handshake message, the function unconditionally calls c.session.md5.update(bytes) to update handshake digests; however, c.session is set to null by c.reset() when the connection is closed (e.g., upon receiving a close_notify alert or an explicit close() call), and it is also null before handshake() is ever called. Because closing the connection does not set the fail flag, the client remains in a state expecting a ServerHello, so a subsequently received Handshake record still reaches handleHandshake(), which dereferences the null session and throws TypeError: Cannot read properties of null (reading 'md5'). After a reset, the connection operates without encryption, meaning an on-path attacker can inject the malicious records even when the legitimate server is honest. The fix in version 1.4.3 adds a guard condition — c.session || c.entity === tls.ConnectionEnd.server — so that handshake messages received by a client without a session are silently ignored (Github Advisory, Forge Commit).

Impact

Successful exploitation results in a Denial of Service (DoS) by terminating the Node.js process. Any application that uses forge.tls as a client and passes raw socket data to connection.process() without wrapping the call in a try/catch block — as illustrated in the library's own README example — is vulnerable to process termination, which drops all active connections handled by that process. There is no confidentiality or integrity impact; data exfiltration and unauthorized modification are not possible through this vulnerability. forge.tls server implementations are not affected, as servers initialize their session upon receiving a ClientHello rather than relying on a pre-existing session object (Github Advisory).

Exploitability

A proof-of-concept (PoC) exploit is publicly available in the official security advisory and has been committed to the repository at tests/pocs/GHSA-j8rw-jp99-435v.js (Github Advisory). The PoC demonstrates a DoS-style crash using two hex-encoded TLS records: a warning-level close_notify alert followed by an empty ServerHello handshake record. No authentication or user interaction is required, but the attack complexity is rated High (AC:H) because the attacker must either control the server the client connects to or occupy an on-path network position. The EPSS score is approximately 0.28–0.30%, indicating a low near-term exploitation probability. There is no evidence of in-the-wild exploitation, no known threat actor attribution, and the vulnerability is not listed in the CISA KEV catalog (Github Advisory).

Exploitation steps

  1. Identify a target: Locate a Node.js application that uses node-forge (versions ≤ 1.4.2) as a TLS client and passes socket data directly to connection.process() without exception handling — a pattern common in applications following the library's README example.
  2. Establish attacker position: Position as either a malicious server that the target client connects to, or as an on-path network attacker capable of injecting unencrypted TLS records (possible after a connection reset, when no encryption is in use).
  3. Initiate or wait for a client handshake: Allow or cause the client to call c.handshake(), which allocates c.session and places the client in the SERVER_HELLO expect state.
  4. Send a warning-level close_notify alert: Deliver the TLS alert record 15 03 01 00 02 01 00 to the client via c.process(). This triggers c.reset(), setting c.session to null and c.fail to false, while leaving the client still expecting a ServerHello.
  5. Deliver a stray ServerHello handshake record: Send the TLS handshake record 16 03 01 00 04 02 00 00 00 (an empty ServerHello). The client's handleHandshake() attempts to call c.session.md5.update(bytes) on the null session, throwing TypeError: Cannot read properties of null (reading 'md5').
  6. Achieve process termination: If the application does not catch the exception propagating from connection.process(), the Node.js process terminates, dropping all active connections (Github Advisory, Forge Commit).

Indicators of compromise

  • Logs: Node.js process crash logs or unhandled exception output containing TypeError: Cannot read properties of null (reading 'md5') with a stack trace pointing to tls.handleHandshake in lib/tls.js (e.g., at tls.handleHandshake (lib/tls.js:2060)).
  • Network: Unexpected TLS alert records (content type 0x15, level 0x01 warning, description 0x00 close_notify) immediately followed by TLS handshake records (content type 0x16, handshake type 0x02 ServerHello) from a server or injected mid-stream by a third party.
  • Process: Sudden, unexplained termination of a Node.js process that uses node-forge for TLS client connections, particularly if the process exits without a graceful shutdown sequence and all in-flight connections are dropped simultaneously (Github Advisory).

Mitigation and workarounds

The primary remediation is to upgrade node-forge to version 1.4.3 or later, which silently ignores handshake records received by a client without an active session (Github Advisory, Forge Release). For applications that cannot upgrade immediately, two workarounds are available: (1) wrap all calls to connection.process() in a try/catch block and close the socket on exception, or (2) stop passing socket data to process() once the closed callback has been invoked and until handshake() is called again. The fix was merged via pull request #1169 and committed at 2cfaeb5 (Forge PR #1169, Forge Commit).

Additional resources

Linux Distribution fix status

Fix availability across major Linux distributions and their releases.

Ubuntu

Unknown

focal (esm-apps)

node-node-forge

Unknown

jammy

node-node-forge

Unknown

jammy (esm-apps)

node-node-forge

Unknown

RHEL / CentOS

Affected

RHEL 8

Not Affected

RHEL 9

Not Affected

RHEL 10

Not Affected

Source: This report was generated using AI

Related Grafana vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

CVE-2026-128086MEDIUM5.3
  • Grafana logoGrafana
  • containers-common
NoYesNov 13, 2026
CVE-2026-128085MEDIUM5.3
  • cAdvisor logocAdvisor
  • cloud-sql-proxy-2.17
NoYesNov 13, 2026
CVE-2026-126358MEDIUM5.3
  • JavaScript logoJavaScript
  • grafana-selinux
NoYesNov 13, 2026
CVE-2026-126357MEDIUM5.3
  • JavaScript logoJavaScript
  • grafana
NoYesNov 13, 2026
CVE-2026-126359LOW3.4
  • JavaScript logoJavaScript
  • hono
NoYesNov 13, 2026

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Additional Wiz resources

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management