Vulnerability DatabaseCVE-2026-119760

CVE-2026-119760: 
SNIPROXY vulnerability analysis and mitigation

Overview

CVE-2026-119760 is a NULL pointer dereference vulnerability in sniproxy through version 0.7.0, affecting the resolv_cancel() function in src/resolv.c. Remote unauthenticated attackers can crash the sniproxy daemon by sending a TLS SNI name or HTTP Host header of exactly 254 or 255 characters that matches a wildcard backend entry, then closing the connection. The vulnerability was disclosed on October 30, 2026, with a patch committed on October 31, 2026. It carries a CVSS v3.1 base score of 7.5 (High) and a CVSS v4.0 base score of 8.7 (High) (GitHub Advisory, VulnCheck).

Technical details

The root cause is a NULL pointer dereference (CWE-476) arising from a mismatch between hostname length validation and DNS library constraints. The valid_hostname() function in sniproxy accepts hostnames up to 255 characters, but the underlying libudns library rejects names longer than 253 characters (the maximum for DNS text form), causing resolv_query() to return NULL. Despite this failure, resolve_server_address() still sets the connection state to RESOLVING and stores the NULL return value in con->query_handle. When the client subsequently closes the connection, close_client_socket() at connection.c:737-738 unconditionally calls resolv_cancel(con->query_handle) with a NULL argument, and resolv_cancel() at resolv.c:219-224 dereferences the NULL pointer without a guard check, causing a segmentation fault (GitHub Issue #411, connection.c source, resolv.c source). The attack requires no authentication, no user interaction, and works against both TLS (SNI) and HTTP (Host header) listeners configured with a wildcard (*) backend and DNS resolution enabled.

Impact

Successful exploitation results in a complete denial of service — the sniproxy daemon crashes with a segmentation fault, interrupting all proxied connections. There is no confidentiality or integrity impact; the vulnerability is limited to availability. Any service relying on sniproxy for TLS SNI routing or HTTP proxying would be rendered unavailable until the daemon is restarted, and the attack can be repeated to prevent recovery (GitHub Advisory, VulnCheck).

Exploitability

No public proof-of-concept exploit code has been observed, and there is no evidence of in-the-wild exploitation at this time (GitHub Advisory). The vulnerability is rated as automatable by NVD SSVC analysis, meaning it can be reliably triggered without manual interaction. The EPSS score is approximately 0.477%, indicating a low but non-negligible probability of exploitation in the near term. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. The attack is trivially reproducible with a short Python script, as demonstrated in the original bug report (GitHub Issue #411).

Exploitation steps

  1. Identify target: Locate an internet-facing or network-accessible sniproxy instance (version ≤ 0.7.0) compiled with --enable-dns and configured with a wildcard (.* or *) backend entry that uses DNS resolution.
  2. Craft overlong hostname: Construct a hostname of exactly 254 or 255 characters (e.g., three 63-character labels plus one 62-character label joined by dots: 'a'*63 + '.' + 'a'*63 + '.' + 'a'*63 + '.' + 'a'*62).
  3. Send malicious TLS ClientHello: Embed the overlong hostname as the TLS SNI extension in a crafted ClientHello packet and send it to the sniproxy TLS listener port. Alternatively, send an HTTP request with the overlong hostname in the Host: header to an HTTP listener.
  4. Close the connection: After a brief delay (e.g., 0.5 seconds) to allow sniproxy to attempt DNS resolution, close the TCP connection. This triggers close_client_socket(), which calls resolv_cancel(NULL).
  5. Daemon crashes: The NULL pointer dereference in resolv_cancel() causes a segmentation fault, crashing the sniproxy daemon and denying service to all proxied connections (GitHub Issue #411).

Indicators of compromise

  • Logs: sniproxy log entries containing Failed to submit DNS query: malformed query immediately before a daemon crash; absence of subsequent log entries indicating the process terminated unexpectedly.
  • Process: Unexpected termination of the sniproxy process; core dump files (e.g., core) generated in the sniproxy working directory with a stack trace referencing resolv_cancel at resolv.c:224 and close_client_socket at connection.c:738.
  • Network: Repeated inbound TCP connections to the sniproxy listener port from the same source IP, each sending a TLS ClientHello or HTTP request with a 254–255 character hostname followed by an immediate connection close; connections that do not complete a full TLS handshake.

Mitigation and workarounds

The upstream maintainer committed a fix on October 31, 2026 (commit 719fe9a in the main repository), which adds a NULL guard before calling resolv_cancel() and clears con->query_handle after cancellation (GitHub Issue #411). A fork by renaudallard provides two complementary patches: one adding the NULL guard in close_client_socket() (commit d5d7829) and another ensuring resolv_query() properly handles all DNS submission failures and aborts connections cleanly (commit 17986ba). Users should update sniproxy to a version newer than 0.7.0 incorporating these fixes. As a temporary workaround, network-level filtering to block connections with SNI names or HTTP Host headers exceeding 253 characters, or rate limiting inbound connections, can reduce exposure during patching windows.

Community reactions

The vulnerability was identified and reported by renaudallard via GitHub Issue #411 on October 23, 2026, with a detailed reproduction script and stack trace (GitHub Issue #411). The CVE was assigned by VulnCheck and published on October 30, 2026. A Mastodon post by @thehackerwire noted the vulnerability shortly after disclosure. No significant broader media coverage or vendor statements beyond the GitHub issue and advisory have been observed.

Additional resources

Linux Distribution fix status

Fix availability across major Linux distributions and their releases.

Debian

Fixed

bookworm

sniproxy

Affected

sid

sniproxy: 0.7.0-2

Fixed

trixie

sniproxy

Affected

Ubuntu

Unknown

bionic (esm-apps)

sniproxy

Unknown

devel

sniproxy

Unknown

focal (esm-apps)

sniproxy

Unknown

jammy

sniproxy

Unknown

jammy (esm-apps)

sniproxy

Unknown

noble

sniproxy

Unknown

noble (esm-apps)

sniproxy

Unknown

resolute

sniproxy

Unknown

Source: This report was generated using AI

Related SNIPROXY vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

CVE-2023-25076CRITICAL9.8
  • SNIPROXY logoSNIPROXY
  • sniproxy
NoYesMar 30, 2023
CVE-2026-119760HIGH8.7
  • SNIPROXY logoSNIPROXY
  • sniproxy
NoYesOct 30, 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