Wiz se junta ao Google Cloud: Fazendo magia juntos

CVE-2026-125334: 
Grafana Análise e mitigação de vulnerabilidades

Visão geral

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).

Detalhes técnicos

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).

Impacto

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).

Explorabilidade

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).

Etapas de exploração

  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).

Indicadores de compromisso

  • 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).

Mitigação e soluções alternativas

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).

Recursos adicionais

Status correto da distribuição Linux

Corrija a disponibilidade entre as principais distribuições Linux e seus lançamentos.

Ubuntu

Desconhecido

focal (esm-apps)

node-node-forge

Desconhecido

jammy

node-node-forge

Desconhecido

jammy (esm-apps)

node-node-forge

Desconhecido

RHEL / CentOS

Afetado

RHEL 8

Não Afetado

RHEL 9

Não Afetado

RHEL 10

Não Afetado

Origem: Este relatório foi gerado usando IA

Relacionado Grafana Vulnerabilidades:

CVE ID

Gravidade

Pontuação

Tecnologias

Nome do componente

Exploit CISA KEV

Tem correção

Data de publicação

CVE-2026-128086MEDIUM5.3
  • Grafana logoGrafana
  • ignition-edge
NãoSimNov 13, 2026
CVE-2026-128085MEDIUM5.3
  • cAdvisor logocAdvisor
  • vault-2.1
NãoSimNov 13, 2026
CVE-2026-126358MEDIUM5.3
  • JavaScript logoJavaScript
  • grafana.src
NãoSimNov 13, 2026
CVE-2026-126357MEDIUM5.3
  • JavaScript logoJavaScript
  • grafana
NãoSimNov 13, 2026
CVE-2026-126359LOW3.4
  • JavaScript logoJavaScript
  • hono
NãoSimNov 13, 2026

Avaliação Gratuita de Vulnerabilidades

Avalie a sua postura de segurança na nuvem

Avalie suas práticas de segurança em nuvem em 9 domínios de segurança para avaliar seu nível de risco e identificar lacunas em suas defesas.

Avaliação de solicitação

Recursos adicionais da Wiz

Marque uma demonstração personalizada

Pronto para ver a Wiz em ação?

"A melhor experiência do usuário que eu já vi, fornece visibilidade total para cargas de trabalho na nuvem."
David EstlickCISO
"A Wiz fornece um único painel de vidro para ver o que está acontecendo em nossos ambientes de nuvem."
Adam FletcherDiretor de Segurança
"Sabemos que se a Wiz identifica algo como crítico, na verdade é."
Greg PoniatowskiChefe de Gerenciamento de Ameaças e Vulnerabilidades