<?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://cve.radiocsirt.org</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>Sun, 18 Oct 2026 09:18:22 +0000</lastBuildDate>
    <item>
      <title>BREW-checkov-CVE-2025-48945 — pycares has a Use-After-Free Vulnerability</title>
      <link>https://cve.radiocsirt.org/vuln/brew-checkov-cve-2025-48945</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: checkov&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;pycares is vulnerable to a use-after-free condition that occurs when a Channel object is garbage collected while DNS queries are still pending. This results in a fatal Python error and interpreter crash.&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;### Root Cause&lt;/p&gt;
&lt;p&gt;The vulnerability stems from improper handling of callback references when the Channel object is destroyed:&lt;/p&gt;
&lt;p&gt;1. When a DNS query is initiated, pycares stores a callback reference using `ffi.new_handle()`
2. If the Channel object is garbage collected while queries are pending, the callback references become invalid
3. When c-ares attempts to invoke the callback, it accesses freed memory, causing a fatal error&lt;/p&gt;
&lt;p&gt;This issue was much more likely to occur when using `event_thread=True` but could happen without it under the right circumstances.&lt;/p&gt;
&lt;p&gt;### Technical Details&lt;/p&gt;
&lt;p&gt;The core issue is a race condition between Python&amp;#39;s garbage collector and c-ares&amp;#39;s callback execution:&lt;/p&gt;
&lt;p&gt;1. When `__del__` is called from within a c-ares callback context, we cannot immediately call `ares_destroy()` because c-ares is still executing code after the callback returns
2. c-ares needs to execute cleanup code after our Python callback returns (specifically at lines 1422-1429 in ares_process.c)
3. If we destroy the channel too quickly, c-ares accesses freed memory&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;Applications using `pycares` can be crashed remotely by triggering DNS queries that result in `Channel` objects being garbage collected before query completion. This is particularly problematic i…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: checkov&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;pycares is vulnerable to a use-after-free condition that occurs when a Channel object is garbage collected while DNS queries are still pending. This results in a fatal Python error and interpreter crash.&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;### Root Cause&lt;/p&gt;
&lt;p&gt;The vulnerability stems from improper handling of callback references when the Channel object is destroyed:&lt;/p&gt;
&lt;p&gt;1. When a DNS query is initiated, pycares stores a callback reference using `ffi.new_handle()`
2. If the Channel object is garbage collected while queries are pending, the callback references become invalid
3. When c-ares attempts to invoke the callback, it accesses freed memory, causing a fatal error&lt;/p&gt;
&lt;p&gt;This issue was much more likely to occur when using `event_thread=True` but could happen without it under the right circumstances.&lt;/p&gt;
&lt;p&gt;### Technical Details&lt;/p&gt;
&lt;p&gt;The core issue is a race condition between Python&amp;#39;s garbage collector and c-ares&amp;#39;s callback execution:&lt;/p&gt;
&lt;p&gt;1. When `__del__` is called from within a c-ares callback context, we cannot immediately call `ares_destroy()` because c-ares is still executing code after the callback returns
2. c-ares needs to execute cleanup code after our Python callback returns (specifically at lines 1422-1429 in ares_process.c)
3. If we destroy the channel too quickly, c-ares accesses freed memory&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;Applications using `pycares` can be crashed remotely by triggering DNS queries that result in `Channel` objects being garbage collected before query completion. This is particularly problematic i…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/brew-checkov-cve-2025-48945</guid>
    </item>
    <item>
      <title>CVE-2025-48945 — pycares has a Use-After-Free Vulnerability</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2025-48945</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; aio-libs aiodns&lt;/p&gt;
&lt;p&gt;pycares is a Python module which provides an interface to c-ares. c-ares is a C library that performs DNS requests and name resolutions asynchronously. Prior to version 4.9.0, pycares is vulnerable to a use-after-free condition that occurs when a Channel object is garbage collected while DNS queries are still pending. This results in a fatal Python error and interpreter crash. The vulnerability has been fixed in pycares 4.9.0 by implementing a safe channel destruction mechanism.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; aio-libs aiodns&lt;/p&gt;
&lt;p&gt;pycares is a Python module which provides an interface to c-ares. c-ares is a C library that performs DNS requests and name resolutions asynchronously. Prior to version 4.9.0, pycares is vulnerable to a use-after-free condition that occurs when a Channel object is garbage collected while DNS queries are still pending. This results in a fatal Python error and interpreter crash. The vulnerability has been fixed in pycares 4.9.0 by implementing a safe channel destruction mechanism.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2025-48945</guid>
    </item>
  </channel>
</rss>
