<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 06 Oct 2026 12:04:02 +0000</lastBuildDate>
    <item>
      <title>Withdrawn: BELL-CVE-2026-18313 — CVE-2026-18313 does not affect BellSoft software</title>
      <link>https://vulnerability.circl.lu/vuln/bell-cve-2026-18313</link>
      <description>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/bell-cve-2026-18313</guid>
    </item>
    <item>
      <title>fkie_cve-2026-18313</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-18313</link>
      <description>&lt;p&gt;rpcapd can allocate up to 65536 bytes per each RPCAP_MSG_UPDATEFILTER_REQ or RPCAP_MSG_STARTCAP_REQ message received from the client, but it never frees the memory, so it leaks memory even under normal use.  A malicious client can cause the server to leak memory substantially faster.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;rpcapd can allocate up to 65536 bytes per each RPCAP_MSG_UPDATEFILTER_REQ or RPCAP_MSG_STARTCAP_REQ message received from the client, but it never frees the memory, so it leaks memory even under normal use.  A malicious client can cause the server to leak memory substantially faster.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-18313</guid>
    </item>
    <item>
      <title>GCVE-1988-2026-0387 — [Bugtraq] [slackware-security] libpcap (SSA:2026-249-01)</title>
      <link>https://vulnerability.circl.lu/vuln/gcve-1988-2026-0387</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; unknown libpcap SSA:2026-249-01&lt;/p&gt;
&lt;p&gt;-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
[slackware-security]  libpcap (SSA:2026-249-01)
New libpcap packages are available for Slackware 15.0 and -current to
fix security issues.
Here are the details from the Slackware 15.0 ChangeLog:
+--------------------------+
patches/packages/libpcap-1.10.7-i586-1_slack15.0.txz:  Upgraded.
This libpcap release fixes a number of vulnerabilities.
For more information, see:
https://www.cve.org/CVERecord?id=CVE-2026-0799
https://www.cve.org/CVERecord?id=CVE-2026-31912
https://www.cve.org/CVERecord?id=CVE-2026-31911
https://www.cve.org/CVERecord?id=CVE-2026-6244
https://www.cve.org/CVERecord?id=CVE-2026-6554
https://www.cve.org/CVERecord?id=CVE-2026-18313
https://www.cve.org/CVERecord?id=CVE-2026-18238
(* Security fix *)
+--------------------------+
Where to find the new packages:
+-----------------------------+
Thanks to the friendly folks at the OSU Open Source Lab
(http://osuosl.org) for donating FTP and rsync hosting
to the Slackware project!  :-)
Also see the &amp;#34;Get Slack&amp;#34; section on http://slackware.com for
additional mirror sites near you.
Updated package for Slackware 15.0:
ftp://ftp.slackware.com/pub/slackware/slackware-15.0/patches/packages/libpcap-1.10.7-i586-1_slack15.0.txz
Updated package for Slackware x86_64 15.0:
ftp://ftp.slackware.com/pub/slackware/slackware64-15.0/patches/packages/libpcap-1.10.7-x86_64-1_slack15.0.txz
Updated package for Slackware -current:
ftp://ftp.slackware.com/pub/slackware/slackware-current/slackwar…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; unknown libpcap SSA:2026-249-01&lt;/p&gt;
&lt;p&gt;-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
[slackware-security]  libpcap (SSA:2026-249-01)
New libpcap packages are available for Slackware 15.0 and -current to
fix security issues.
Here are the details from the Slackware 15.0 ChangeLog:
+--------------------------+
patches/packages/libpcap-1.10.7-i586-1_slack15.0.txz:  Upgraded.
This libpcap release fixes a number of vulnerabilities.
For more information, see:
https://www.cve.org/CVERecord?id=CVE-2026-0799
https://www.cve.org/CVERecord?id=CVE-2026-31912
https://www.cve.org/CVERecord?id=CVE-2026-31911
https://www.cve.org/CVERecord?id=CVE-2026-6244
https://www.cve.org/CVERecord?id=CVE-2026-6554
https://www.cve.org/CVERecord?id=CVE-2026-18313
https://www.cve.org/CVERecord?id=CVE-2026-18238
(* Security fix *)
+--------------------------+
Where to find the new packages:
+-----------------------------+
Thanks to the friendly folks at the OSU Open Source Lab
(http://osuosl.org) for donating FTP and rsync hosting
to the Slackware project!  :-)
Also see the &amp;#34;Get Slack&amp;#34; section on http://slackware.com for
additional mirror sites near you.
Updated package for Slackware 15.0:
ftp://ftp.slackware.com/pub/slackware/slackware-15.0/patches/packages/libpcap-1.10.7-i586-1_slack15.0.txz
Updated package for Slackware x86_64 15.0:
ftp://ftp.slackware.com/pub/slackware/slackware64-15.0/patches/packages/libpcap-1.10.7-x86_64-1_slack15.0.txz
Updated package for Slackware -current:
ftp://ftp.slackware.com/pub/slackware/slackware-current/slackwar…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/gcve-1988-2026-0387</guid>
    </item>
    <item>
      <title>GHSA-f2rh-ff9r-fh4j</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-f2rh-ff9r-fh4j</link>
      <description>&lt;p&gt;rpcapd can allocate up to 65536 bytes per each RPCAP_MSG_UPDATEFILTER_REQ or RPCAP_MSG_STARTCAP_REQ message received from the client, but it never frees the memory, so it leaks memory even under normal use.  A malicious client can cause the server to leak memory substantially faster.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;rpcapd can allocate up to 65536 bytes per each RPCAP_MSG_UPDATEFILTER_REQ or RPCAP_MSG_STARTCAP_REQ message received from the client, but it never frees the memory, so it leaks memory even under normal use.  A malicious client can cause the server to leak memory substantially faster.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-f2rh-ff9r-fh4j</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-18313 — rpcapd memory leak in libpcap before 1.10.7</title>
      <link>https://vulnerability.circl.lu/vuln/msrc_cve-2026-18313</link>
      <description>msrc_CVE-2026-18313</description>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/msrc_cve-2026-18313</guid>
    </item>
    <item>
      <title>OESA-2026-3988 — libpcap security update</title>
      <link>https://vulnerability.circl.lu/vuln/oesa-2026-3988</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS-SP3: libpcap&lt;/p&gt;
&lt;p&gt;This is the official web site of tcpdump, a powerful command-line  packet analyzer; and libpcap, a portable C/C++ library for  network traffic capture.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In BPF instructions that load/store a value from/to a scratch memory register the register index is an unsigned 32-bit integer and must not exceed 15, but libpcap BPF interpreter does not validate the value. In particular uncommon use cases a crafted filter program can cause the interpreter to try reading and writing the OS process memory in the 16GiB starting at the current stack frame on 64-bit architectures and in the entire address space on 32-bit architectures.(CVE-2026-0799)&lt;/p&gt;
&lt;p&gt;The rpcap client code that processes a RPCAP_MSG_PACKET message received from the server incorrectly validates its headers. A malicious server can send a crafted message and cause the client to treat up to 20 bytes of the client process memory beyond the end of the buffer as if it was a part of the captured packet.(CVE-2026-18238)&lt;/p&gt;
&lt;p&gt;rpcapd can allocate up to 65536 bytes per each RPCAP_MSG_UPDATEFILTER_REQ or RPCAP_MSG_STARTCAP_REQ message received from the client, but it never frees the memory, so it leaks memory even under normal use. A malicious client can cause the server to leak memory substantially faster.(CVE-2026-18313)&lt;/p&gt;
&lt;p&gt;libpcap BPF interpreter calls abort() if it encounters a BPF instruction that has an invalid opcode. In particular uncommon use cases a crafted filter program can terminate the OS process.(CVE-2026-31911…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS-SP3: libpcap&lt;/p&gt;
&lt;p&gt;This is the official web site of tcpdump, a powerful command-line  packet analyzer; and libpcap, a portable C/C++ library for  network traffic capture.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In BPF instructions that load/store a value from/to a scratch memory register the register index is an unsigned 32-bit integer and must not exceed 15, but libpcap BPF interpreter does not validate the value. In particular uncommon use cases a crafted filter program can cause the interpreter to try reading and writing the OS process memory in the 16GiB starting at the current stack frame on 64-bit architectures and in the entire address space on 32-bit architectures.(CVE-2026-0799)&lt;/p&gt;
&lt;p&gt;The rpcap client code that processes a RPCAP_MSG_PACKET message received from the server incorrectly validates its headers. A malicious server can send a crafted message and cause the client to treat up to 20 bytes of the client process memory beyond the end of the buffer as if it was a part of the captured packet.(CVE-2026-18238)&lt;/p&gt;
&lt;p&gt;rpcapd can allocate up to 65536 bytes per each RPCAP_MSG_UPDATEFILTER_REQ or RPCAP_MSG_STARTCAP_REQ message received from the client, but it never frees the memory, so it leaks memory even under normal use. A malicious client can cause the server to leak memory substantially faster.(CVE-2026-18313)&lt;/p&gt;
&lt;p&gt;libpcap BPF interpreter calls abort() if it encounters a BPF instruction that has an invalid opcode. In particular uncommon use cases a crafted filter program can terminate the OS process.(CVE-2026-31911…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/oesa-2026-3988</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:11744-1 — libpcap-devel-1.10.7-1.1 on GA media</title>
      <link>https://vulnerability.circl.lu/vuln/opensuse-su-2026:11744-1</link>
      <description>&lt;p&gt;libpcap-devel-1.10.7-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;libpcap-devel-1.10.7-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/opensuse-su-2026:11744-1</guid>
    </item>
    <item>
      <title>SUSE-SU-2026:23737-1 — Security update for libpcap</title>
      <link>https://vulnerability.circl.lu/vuln/suse-su-2026:23737-1</link>
      <description>&lt;p&gt;Security update for libpcap&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for libpcap&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/suse-su-2026:23737-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-18313</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-18313</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: libpcap, Ubuntu:Pro:16.04:LTS: libpcap, Ubuntu:Pro:18.04:LTS: libpcap, Ubuntu:Pro:20.04:LTS: libpcap, Ubuntu:22.04:LTS: libpcap, Ubuntu:24.04:LTS: libpcap, Ubuntu:26.04:LTS: libpcap&lt;/p&gt;
&lt;p&gt;rpcapd can allocate up to 65536 bytes per each RPCAP_MSG_UPDATEFILTER_REQ or RPCAP_MSG_STARTCAP_REQ message received from the client, but it never frees the memory, so it leaks memory even under normal use.  A malicious client can cause the server to leak memory substantially faster.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: libpcap, Ubuntu:Pro:16.04:LTS: libpcap, Ubuntu:Pro:18.04:LTS: libpcap, Ubuntu:Pro:20.04:LTS: libpcap, Ubuntu:22.04:LTS: libpcap, Ubuntu:24.04:LTS: libpcap, Ubuntu:26.04:LTS: libpcap&lt;/p&gt;
&lt;p&gt;rpcapd can allocate up to 65536 bytes per each RPCAP_MSG_UPDATEFILTER_REQ or RPCAP_MSG_STARTCAP_REQ message received from the client, but it never frees the memory, so it leaks memory even under normal use.  A malicious client can cause the server to leak memory substantially faster.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-18313</guid>
    </item>
  </channel>
</rss>
