cve.bz

CVE-2026-63447 oisf suricata: Inefficient Algorithmic Complexity

7.5 highEPSS 0.6%Fix available

High (7.5) in oisf suricata. EPSS 0.6% estimated probability of exploitation activity in the next 30 days.

On this page
Suricata is a network Intrusion Detection System, Intrusion Prevention System and Network Security Monitoring engine. From 8.0.5 until 8.0.6, the FTP parser in src/app-layer-ftp.c can continue allocating transactions after app-layer.protocols.ftp.max-tx is reached while processing one large chunk of FTP command data. The oversized transaction list is repeatedly processed with quadratic complexity after the too_many_transactions event, allowing crafted FTP traffic to degrade packet processing, reduce monitoring visibility, or cause denial of service. This issue is fixed in version 8.0.6.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.6% (unchanged from 0.6% a week ago; 0.6% 30 days ago) estimated probability of exploitation activity in the next 30 days; 51st percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-09-21. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-407 Inefficient Algorithmic Complexity
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-63447 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-63447?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-63447?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-63447 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
oisf:suricata8.0.5

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian13suricatano fix listedDEBIAN-CVE-2026-63447
Debian14suricata1:8.0.6-1DEBIAN-CVE-2026-63447
Ubuntu16.04:LTS, 18.04:LTS, 22.04:LTS and 2 moresuricatano fix listedUBUNTU-CVE-2026-63447

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Red Hat

Red Hat rates this Important.

Red Hat's statement

This vulnerability is rated as Important because an unauthenticated remote attacker transmitting network traffic inspected by Suricata can trigger severe CPU exhaustion without requiring privileges, leading to packet processing starvation and denial of service. In typical deployments where Suricata passively monitors high-throughput network segments, malicious FTP payloads can degrade inspection performance across all monitored flows. Environments that do not inspect FTP traffic or that strictly filter network access to monitored boundaries experience substantially lower operational risk.

Red Hat does not ship versions affected by this vulnerability.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-63447.

References

Check your stackJSON