CVE-2026-59674
Deferred Deferred - Pending Action

Symlink Following in openSUSE Tumbleweed Suricata Package

Vulnerability report for CVE-2026-59674, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-07-14

Last updated on: 2026-07-15

Assigner: SUSE

Description

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-14
Last Modified
2026-07-15
Generated
2026-08-03
AI Q&A
2026-07-14
EPSS Evaluated
2026-08-02
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
suse suricata From 8.0.5-2.1 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-61 The product, when opening a file or directory, does not sufficiently account for when the file is a symbolic link that resolves to a target outside of the intended control sphere. This could allow an attacker to cause the product to operate on unauthorized files.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-59674 is a UNIX Symbolic Link (Symlink) Following vulnerability in the Suricata package on openSUSE Tumbleweed. It allows a local attacker with access to the 'suricata' user account to escalate privileges to root.

The vulnerability occurs in the package's '%post' scriptlet, which runs after installation or update. The script attempts to change ownership of a file named '.migrated-to-nonroot' to the 'suricata' user using the `chown` command. However, this file is created in a directory writable by the 'suricata' user. An attacker can exploit this by deleting the file and replacing it with a symbolic link pointing to a sensitive system file, such as '/etc/shadow'. When the script runs, it changes ownership of the linked file to the 'suricata' user, allowing the attacker to gain root-level access.

The proposed fix removes the unnecessary `chown` operation, as it is not required for Suricata's functionality. The patch also ensures the migration file is placed in a root-owned directory to prevent tampering and improves the update message system for better user notification.

Detection Guidance

To detect this vulnerability on your system, you can check for the presence of the vulnerable Suricata package version and inspect the `%post` scriptlet behavior.

  • Check the installed Suricata package version using the following command: `rpm -q suricata`. If the version is before 8.0.5-2.1 on openSUSE Tumbleweed, the system may be vulnerable.
  • Inspect the `%post` scriptlet in the Suricata package for the problematic `chown` command. You can extract the scriptlet using: `rpm -q --scripts suricata`. Look for a line that attempts to change ownership of `.migrated-to-nonroot` to the 'suricata' user.
  • Verify the directory where `.migrated-to-nonroot` is created. If it is writable by the 'suricata' user, the system is vulnerable. Use `ls -ld /path/to/directory` to check permissions.
  • Check for the existence of the `.migrated-to-nonroot` file in the expected directory. If it is a symbolic link instead of a regular file, it may indicate an attempted exploit.
Impact Analysis

If you are using openSUSE Tumbleweed with the affected Suricata package, this vulnerability could allow a local attacker to escalate privileges from the 'suricata' user to root. This means:

  • An attacker with access to the 'suricata' user account could gain full control over the system, including reading, modifying, or deleting sensitive files.
  • The attacker could install malicious software, create backdoors, or disrupt system operations.
  • Sensitive data, such as passwords, configuration files, or personal information, could be compromised.

The vulnerability is considered a local privilege escalation (LPE), meaning the attacker must already have access to the system as the 'suricata' user. However, once exploited, it grants the highest level of system privileges (root), significantly increasing the potential damage.

Compliance Impact

This vulnerability could impact compliance with several common standards and regulations, depending on the context of the affected system:

  • GDPR (General Data Protection Regulation): If the system processes or stores personal data of EU citizens, a privilege escalation vulnerability could lead to unauthorized access to this data. GDPR requires organizations to implement appropriate security measures to protect personal data, and a failure to patch such vulnerabilities could result in non-compliance, leading to fines or legal action.
  • HIPAA (Health Insurance Portability and Accountability Act): For systems handling protected health information (PHI) in the U.S., this vulnerability could allow unauthorized access to sensitive patient data. HIPAA mandates safeguards to protect PHI, and failing to address such vulnerabilities could result in violations and penalties.
  • PCI DSS (Payment Card Industry Data Security Standard): If the system processes payment card data, this vulnerability could lead to unauthorized access to cardholder information. PCI DSS requires systems to be protected against known vulnerabilities, and failure to patch could result in non-compliance and potential fines.
  • ISO 27001: This standard requires organizations to manage information security risks, including vulnerabilities that could lead to unauthorized access. Failure to address this vulnerability could result in non-conformity with ISO 27001 requirements.

Organizations should promptly apply the available patch to mitigate this vulnerability and maintain compliance with relevant regulations. Additionally, they should review their systems for signs of exploitation and ensure proper access controls are in place to limit the risk of local privilege escalation attacks.

Mitigation Strategies

To mitigate this vulnerability, follow these steps immediately:

  • Update the Suricata package to the latest version (8.0.5-2.1 or later) using the package manager: `zypper update suricata`. This version includes the fix that removes the unnecessary `chown` operation.
  • If updating is not immediately possible, manually inspect and modify the `%post` scriptlet to remove the `chown` command targeting `.migrated-to-nonroot`. Ensure the file is created in a root-owned directory to prevent tampering.
  • Restrict write permissions on directories where Suricata-related files are created. Ensure the 'suricata' user cannot modify critical system files or directories.
  • Monitor the system for any unusual symbolic links in directories writable by the 'suricata' user. Remove or investigate any suspicious links.
  • Review system logs for any unauthorized changes to file ownership or permissions, particularly those involving sensitive files like `/etc/shadow`.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-59674. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart