Which versions of Suricata are affected by CVE-2026-59674?

A critical vulnerability in openSUSE Tumbleweed's Suricata security monitoring package allows escalation from the unprivileged Suricata service account to full root system access.. A patch is available.

How to fix or mitigate CVE-2026-59674?

Within 24 hours: identify all systems running openSUSE Tumbleweed with Suricata IDS/IPS enabled and document current access controls on the suricata service account. Within 7 days: implement interim mitigations including restrictive filesystem ACLs on all suricata-managed directories to prevent symlink creation, deploy SELinux or AppArmor policies limiting suricata account capabilities, and enable detailed audit logging for symlink operations. Within 30 days: monitor openSUSE and Suricata vendor security advisories for patch availability; if patched versions emerge, plan a phased update cadence; if no patch timeline appears, evaluate alternative IDS/IPS solutions compatible with openSUSE Tumbleweed or migrate affected systems to patched Linux distributions.

Suricata CVE-2026-59674

Q: What is the CVSS score of CVE-2026-59674?

CVE-2026-59674 has a CVSS 4.0 base score of 7.1 (High). CVSS vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:N/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.1%.

EUVD-2026-43633 HIGH

UNIX Symbolic Link (Symlink) Following (CWE-61)

2026-07-14 suse

GHSA-j33g-47h2-2687

Privilege Escalation Red Hat Suricata Suse Opensuse Tumbleweed

7.1

CVSS 4.0 · Vendor: suse

Severity by source

Vendor (suse) PRIMARY

7.1 HIGH

CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:N/AU:X/R:X/V:X/RE:X/U:X

vuln.today AI

7.8 HIGH

Local escalation by the already-authenticated suricata account (AV:L, PR:L), low complexity, no interaction; symlink abuse yields root so C/I/A all High, scope Unchanged as it stays within the host OS authority.

3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

4.0 AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

SUSE

7.8 HIGH

AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Red Hat

8.8 HIGH

qualitative

Primary rating from Vendor (suse).

CVSS VectorVendor: suse

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Lifecycle Timeline

Patch available

Jul 14, 2026 - 11:17 EUVD

Analysis Generated

Jul 14, 2026 - 08:16 vuln.today

CVE Published

Jul 14, 2026 - 07:32 cve.org

HIGH 7.1

DescriptionCVE.org

A UNIX Symbolic Link (Symlink) Following vulnerability in openSUSE Tumbleweed suricata package allows the suricata user to escalate to root.

This issue affects openSUSE Tumbleweed: from ? before 8.0.5-2.1; openSUSE Tumbleweed: from ? before 8.0.5-2.1.

AnalysisAI

Local privilege escalation in the openSUSE Tumbleweed packaging of Suricata allows the unprivileged 'suricata' service account to gain root through a symbolic-link following flaw (CWE-61) in files or directories the package manages with predictable, service-writable paths. Any actor already holding the suricata user context - for example via a compromised or misconfigured IDS/IPS process - can plant a symlink that redirects a root-executed operation to a target of their choosing, yielding full system compromise. The CVSS 4.0 exploit-maturity metric is set to Proof-of-Concept (E:P); there is no evidence of active exploitation in CISA KEV, and no public exploit identified at time of analysis.

Technical ContextAI

Suricata is an open-source network IDS/IPS/NSM engine that typically runs its detection process under a dedicated low-privilege 'suricata' account while certain maintenance, rotation, or startup operations run as root. This issue is a distribution-packaging defect (root cause class CWE-61, UNIX Symbolic Link Following), meaning a root-privileged operation shipped by the openSUSE Tumbleweed suricata package operates on a path that the suricata user can control, without first verifying it is not a symlink. The CPE data (cpe:2.3:a:suse:opensuse_tumbleweed) scopes the flaw to SUSE's Tumbleweed distribution packaging rather than to upstream Suricata source code, so it is a downstream packaging bug - likely in a logrotate rule, tmpfiles/systemd unit, cron job, or install/pre-post script that chowns, writes, or truncates a file under a suricata-writable directory as root.

RemediationAI

Apply the vendor-released patch: update the suricata package to 8.0.5-2.1 or later via 'zypper up suricata' (or a full 'zypper dup' on Tumbleweed) to obtain the fixed packaging that no longer follows attacker-controlled symlinks. Until patched, restrict who and what can act as the suricata user: run Suricata under a hardened systemd unit with ProtectSystem/ReadOnlyPaths and NoNewPrivileges to limit what the account can influence, and audit suricata-writable directories (log, run, and temp paths) removing any unexpected symlinks - the trade-off is that overly aggressive path hardening can break log rotation or rule reload. Where feasible, ensure root-run maintenance operations do not traverse suricata-owned directories, accepting that this may require adjusting logrotate/tmpfiles configuration. Refer to the SUSE advisory at https://bugzilla.suse.com/show_bug.cgi?id=CVE-2026-59674 for the definitive fixed version.