CVE-2023-35852: suricata · n/a
Affects suricataSource CVE Database V5
Not known to be exploited : upgrade to 6.0.13 soon.
Data as of 25 Oct 2026, 22:44 UTC
Rated High by the CNA (mitre) · No CVSS score from NVD or the CNA
- EPSS
- 1.1% chance of exploitation in 30 days – higher than 65% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 6.0.13
Exploitation evidence
Disclosed: evidence found.
CVE published 19 Jun 2023
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Upgrade oisf/suricata to 6.0.13.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHuboisf/suricatapkg:github/oisf/suricataOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade Suricata to version 6.0.13 or later, where this vulnerability is fixed. The fix requires explicit enabling of 'allow-absolute-filenames' and 'allow-write' options in the dataset rules configuration to permit directory traversal and writing. Systems that do not require such functionality do not need to enable these options, thereby mitigating the risk. No additional vendor advisories indicate other mitigations or that no action is required.
Description
Suricata versions prior to 6.0.13 contain a vulnerability where a dataset filename derived from a rule can cause absolute or relative directory traversal. This allows an adversary controlling an external source of rules to write to arbitrary locations on the local filesystem. The issue is fixed in version 6.0.13 by requiring explicit configuration options to allow absolute filenames and write access in dataset rules.
References
- github.com/OISF/suricata/compare/suricata-6.0.12...suricata-6.0.13 (opens in a new tab)
- github.com/OISF/suricata/commit/aee1523b4591430ebed1ded0bb95508e6717a335 (opens in a new tab)
- github.com/OISF/suricata/commit/735f5aa9ca3b28cfacc7a443f93a44387fbacf17 (opens in a new tab)
- stamus-networks.com/stamus-labs (opens in a new tab)
- lists.debian.org/debian-lts-announce/2025/03/msg00029.html (opens in a new tab)