CVE-2019-10051: An issue was discovered in Suricata 4.1.3

This week

HIGH 7.5REMOTEDOWNGRADE

CVE-2019-10051 is a high-severity flaw (CVSS 7.5) affecting suricata. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

An issue was discovered in Suricata 4.1.3. If the function filetracker_newchunk encounters an unsafe "Some(sfcm) => { ft.new_chunk }" item, then the program enters an smb/files.rs error condition and crashes.

Why this priority

High severity
Public exploit reference
Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	2.1% (top 18%)
CISA exploited list	No
Weakness	CWE-754
Published	2019-08-28
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: suricata-ids

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2019-08-28 20:15 UTCPublished CVE record published
2026-06-17 02:10 UTCUpdated Record last modified

suricata-ids suricata DOWNGRADE

Affected: 4.1.3 · 4.1.4

Fixed in: no fixed release known

Safe to downgrade to: a release before 4.1.3

1. Check installed version

apt-cache policy suricata || rpm -q suricata || suricata --version

2. No fixed release: DOWNGRADE to a release before 4.1.3 (Debian / Ubuntu)

apt-cache madison suricata sudo apt install suricata=<VERSION_BEFORE_4.1.3> sudo apt-mark hold suricata

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list suricata sudo dnf downgrade suricata-<VERSION_BEFORE_4.1.3> sudo dnf versionlock add suricata

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2019-10051?

suricata: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2019-10051 being exploited?

CVE-2019-10051 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2019-10051 affect?

CVE-2019-10051 affects suricata. Severity is high (CVSS 7.5). An issue was discovered in Suricata 4.1.3. If the function filetracker_newchunk encounters an unsafe "Some(sfcm) => { ft.new_chunk }" item, then the program enters an smb/files.rs error condition and crashes.

How urgent is CVE-2019-10051?

Priority 57/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

Software pages

Suricata and Snort vulnerabilities

Related CVEs

CVE-2026-31937 HIGH 7.5 UPGRADE Suricata is a network IDS, IPS and NSM engine
CVE-2026-31931 HIGH 7.5 UPGRADE Suricata is a network IDS, IPS and NSM engine
CVE-2026-31933 HIGH 7.5 UPGRADE Suricata is a network IDS, IPS and NSM engine
CVE-2026-31932 HIGH 7.5 UPGRADE Suricata is a network IDS, IPS and NSM engine
CVE-2026-31934 HIGH 7.5 UPGRADE Suricata is a network IDS, IPS and NSM engine

References

← Back to latest CVEs