---
id: "CVE-2026-76524"
kind: "vulnerability"
aliases: ["CVE-2026-76524"]
title: "Snort 3: local control socket lets low-privilege users run commands"
severity: "high"
cvss: 7.8
epss: 0.00136
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["linux", "network-security", "package", "snort"]
not_affected_if: ["no-local-untrusted-users", "snort-not-installed"]
published_at: "2026-10-21T17:19:09+00:00"
first_seen_at: "2026-10-23T21:57:29+00:00"
updated_at: "2026-10-25T03:08:20+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-76524", "first_seen_at": "2026-10-23T21:57:29+00:00"}, {"source": "epss", "url": "https://api.first.org/data/v1/epss?cve=CVE-2026-76524", "first_seen_at": "2026-10-24T13:15:54+00:00"}]
---

# Snort 3: local control socket lets low-privilege users run commands

Snort 3's control channel socket does not check authentication for local connections. A local user with low privileges can connect to it and run arbitrary commands as the Snort 3 process user, and read and write its memory.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Run `snort --version` to see the installed Snort 3 version.
- Check whether the control channel socket is present and who can connect to it (unknown: the sources do not name the socket path or permissions).

## Fix

- Upgrade Open Source Snort 3 to a fixed release (unknown: the sources do not name the fixed version).
- Restrict local access to the Snort control channel socket until patched (unknown: the sources do not give the exact setting).

## Timeline

- 2026-10-23T21:57:29+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-76524
- 2026-10-24T13:15:54+00:00 epss https://api.first.org/data/v1/epss?cve=CVE-2026-76524

## From the sources

A vulnerability in the control channel socket implementation of Open Source Snort 3 could allow an authenticated, local attacker with low privileges to execute arbitrary commands as the Snort 3 process user.

This vulnerability is due to a lack of authentication when a local user connects to the Snort control channel socket. An attacker could exploit this vulnerability by connecting to the Snort 3 control channel socket as a local user. A successful exploit could allow the attacker to execute arbitrary commands as well as read and write Snort 3 process memory.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_