https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-05T07:19:00.872040+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/bdu:2025-15195 bdu:2025-15195 2026-10-05T07:19:00.952414+00:00 bdu:2025-15195 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0972 certfr-2025-avi-0972 — De multiples vulnérabilités ont été découvertes dans Suricata. Elles permettent à un attaquant de provoquer un problème… 2026-10-05T07:19:00.952453+00:00 certfr-2025-avi-0972 https://cve.radiocsirt.org/vuln/euvd-2026-262029 EUVD-2026-262029 2026-10-05T07:19:00.952484+00:00 EUVD-2026-262029 https://cve.radiocsirt.org/vuln/fkie_cve-2025-64333 fkie_cve-2025-64333 2026-10-05T07:19:00.952497+00:00

Suricata is a network IDS, IPS and NSM engine developed by the OISF (Open Information Security Foundation) and the Suricata community. Prior to versions 7.0.13 and 8.0.2, a large HTTP content type, when logged can cause a stack overflow crashing Suricata. This issue has been patched in versions 7.0.13 and 8.0.2. A workaround for this issue involves limiting stream.reassembly.depth to less then half the stack size. Increasing the process stack size makes it less likely the bug will trigger.

 https://cve.radiocsirt.org/vuln/opensuse-su-2026:10082-1 openSUSE-SU-2026:10082-1 — libsuricata8_0_3-8.0.3-1.1 on GA media 2026-10-05T07:19:00.952528+00:00

libsuricata8_0_3-8.0.3-1.1 on GA media

 https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-64333 UBUNTU-CVE-2025-64333 2026-10-05T07:19:00.952556+00:00

Affected: Ubuntu:16.04:LTS: suricata, Ubuntu:18.04:LTS: suricata, Ubuntu:22.04:LTS: suricata, Ubuntu:24.04:LTS: suricata, Ubuntu:25.10: suricata

Suricata is a network IDS, IPS and NSM engine developed by the OISF (Open Information Security Foundation) and the Suricata community. Prior to versions 7.0.13 and 8.0.2, a large HTTP content type, when logged can cause a stack overflow crashing Suricata. This issue has been patched in versions 7.0.13 and 8.0.2. A workaround for this issue involves limiting stream.reassembly.depth to less then half the stack size. Increasing the process stack size makes it less likely the bug will trigger.