Skip to content

suricata-update: rule archive path traversal allows arbitrary file write

High
jasonish published GHSA-6v4p-4w5x-9fp2 Jul 21, 2026

Package

pip suricata-update (pip)

Affected versions

< 1.3.8

Patched versions

1.3.8

Description

Impact

suricata-update's embedded-file handling for downloaded rule archives did not confine destination paths for files referenced by rule keywords such as lua, filemd5, filesha1, and filesha256. A malicious tar or zip rule archive can reference members containing ../ so that suricata-update writes attacker-controlled files outside the configured rules directory.

Patches

Upgrade to suricata-update 1.3.8. If using Suricata-Update as bundled with Suricata, Suricata 8.0.6 and 7.0.17 will contain Suricata-Update 1.3.8.

Workarounds

Avoid running Suricata-Update as root; instead, use a dedicated account. See Running as a User Other Than Root in the Suricata documentation. Additionally, avoid untrusted ruleset archives.

References

https://redmine.openinfosecfoundation.org/issues/8633

Credits

Reported by Guillem Lefait.

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

CVE ID

CVE-2026-63347

Weaknesses

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. Learn more on MITRE.