PatchTheCVE: libslirphttps://patchthecve.com/CVEs with upgrade or downgrade fix stepsCVE-2021-3595: An invalid pointer initialization issue was found in the SLiRP networking implementation of QEMUhttps://patchthecve.com/cve/CVE-2021-3595.htmlhttps://patchthecve.com/cve/CVE-2021-3595.htmlWed, 17 Jun 2026 04:05:24 +0000LOW 3.8: An invalid pointer initialization issue was found in the SLiRP networking implementation of QEMU. The flaw exists in the tftp_input() function and could occur while processing a udp packet that is smaller than the size of the 'tftp_t' structure. This issue may lead to out-of-bounds read access or inCVE-2021-3594: An invalid pointer initialization issue was found in the SLiRP networking implementation of QEMUhttps://patchthecve.com/cve/CVE-2021-3594.htmlhttps://patchthecve.com/cve/CVE-2021-3594.htmlWed, 17 Jun 2026 04:05:24 +0000LOW 3.8: An invalid pointer initialization issue was found in the SLiRP networking implementation of QEMU. The flaw exists in the udp_input() function and could occur while processing a udp packet that is smaller than the size of the 'udphdr' structure. This issue may lead to out-of-bounds read access or indCVE-2021-3593: An invalid pointer initialization issue was found in the SLiRP networking implementation of QEMUhttps://patchthecve.com/cve/CVE-2021-3593.htmlhttps://patchthecve.com/cve/CVE-2021-3593.htmlWed, 17 Jun 2026 04:05:24 +0000LOW 3.8: An invalid pointer initialization issue was found in the SLiRP networking implementation of QEMU. The flaw exists in the udp6_input() function and could occur while processing a udp packet that is smaller than the size of the 'udphdr' structure. This issue may lead to out-of-bounds read access or inCVE-2021-3592: An invalid pointer initialization issue was found in the SLiRP networking implementation of QEMUhttps://patchthecve.com/cve/CVE-2021-3592.htmlhttps://patchthecve.com/cve/CVE-2021-3592.htmlWed, 17 Jun 2026 04:05:23 +0000LOW 3.8: An invalid pointer initialization issue was found in the SLiRP networking implementation of QEMU. The flaw exists in the bootp_input() function and could occur while processing a udp packet that is smaller than the size of the 'bootp_t' structure. A malicious guest could use this flaw to leak 10 bytCVE-2020-29130: slirp.c in libslirp through 4.3.1 has a buffer over-read because it tries to read a certain amount of header dhttps://patchthecve.com/cve/CVE-2020-29130.htmlhttps://patchthecve.com/cve/CVE-2020-29130.htmlWed, 17 Jun 2026 03:11:04 +0000MEDIUM 4.3: slirp.c in libslirp through 4.3.1 has a buffer over-read because it tries to read a certain amount of header data even if that exceeds the total packet length.CVE-2020-29129: ncsi.c in libslirp through 4.3.1 has a buffer over-read because it tries to read a certain amount of header dahttps://patchthecve.com/cve/CVE-2020-29129.htmlhttps://patchthecve.com/cve/CVE-2020-29129.htmlWed, 17 Jun 2026 03:11:04 +0000MEDIUM 4.3: ncsi.c in libslirp through 4.3.1 has a buffer over-read because it tries to read a certain amount of header data even if that exceeds the total packet length.CVE-2020-10756: An out-of-bounds read vulnerability was found in the SLiRP networking implementation of the QEMU emulatorhttps://patchthecve.com/cve/CVE-2020-10756.htmlhttps://patchthecve.com/cve/CVE-2020-10756.htmlWed, 17 Jun 2026 02:48:23 +0000MEDIUM 6.5: An out-of-bounds read vulnerability was found in the SLiRP networking implementation of the QEMU emulator. This flaw occurs in the icmp6_send_echoreply() routine while replying to an ICMP echo request, also known as ping. This flaw allows a malicious guest to leak the contents of the host memory, reCVE-2020-1983: A use after free vulnerability in ip_reass() in ip_input.c of libslirp 4.2.0 and prior releases allows craftedhttps://patchthecve.com/cve/CVE-2020-1983.htmlhttps://patchthecve.com/cve/CVE-2020-1983.htmlWed, 17 Jun 2026 03:02:46 +0000HIGH 7.5: A use after free vulnerability in ip_reass() in ip_input.c of libslirp 4.2.0 and prior releases allows crafted packets to cause a denial of service.CVE-2020-8608: In libslirp 4.1.0, as used in QEMU 4.2.0, tcp_subr.c misuses snprintf return values, leading to a buffer overfhttps://patchthecve.com/cve/CVE-2020-8608.htmlhttps://patchthecve.com/cve/CVE-2020-8608.htmlWed, 17 Jun 2026 03:26:38 +0000MEDIUM 5.6: In libslirp 4.1.0, as used in QEMU 4.2.0, tcp_subr.c misuses snprintf return values, leading to a buffer overflow in later code.CVE-2020-7211: tftp.c in libslirp 4.1.0, as used in QEMU 4.2.0, does not prevent ..\ directory traversal on Windows.https://patchthecve.com/cve/CVE-2020-7211.htmlhttps://patchthecve.com/cve/CVE-2020-7211.htmlWed, 17 Jun 2026 03:24:31 +0000HIGH 7.5: tftp.c in libslirp 4.1.0, as used in QEMU 4.2.0, does not prevent ..\ directory traversal on Windows.CVE-2020-7039: tcp_emu in tcp_subr.c in libslirp 4.1.0, as used in QEMU 4.2.0, mismanages memory, as demonstrated by IRC DCC https://patchthecve.com/cve/CVE-2020-7039.htmlhttps://patchthecve.com/cve/CVE-2020-7039.htmlWed, 17 Jun 2026 03:24:10 +0000MEDIUM 5.6: tcp_emu in tcp_subr.c in libslirp 4.1.0, as used in QEMU 4.2.0, mismanages memory, as demonstrated by IRC DCC commands in EMU_IRC. This can cause a heap-based buffer overflow or other out-of-bounds access which can lead to a DoS or potential execute arbitrary code.CVE-2019-15890: libslirp 4.0.0, as used in QEMU 4.1.0, has a use-after-free in ip_reass in ip_input.c.https://patchthecve.com/cve/CVE-2019-15890.htmlhttps://patchthecve.com/cve/CVE-2019-15890.htmlWed, 17 Jun 2026 02:21:16 +0000HIGH 7.5: libslirp 4.0.0, as used in QEMU 4.1.0, has a use-after-free in ip_reass in ip_input.c.CVE-2019-14378: ip_reass in ip_input.c in libslirp 4.0.0 has a heap-based buffer overflow via a large packet because it mishanhttps://patchthecve.com/cve/CVE-2019-14378.htmlhttps://patchthecve.com/cve/CVE-2019-14378.htmlWed, 17 Jun 2026 02:18:18 +0000HIGH 8.8: ip_reass in ip_input.c in libslirp 4.0.0 has a heap-based buffer overflow via a large packet because it mishandles a case involving the first fragment.