<?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>Mon, 28 Sep 2026 07:53:09 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-64847 — AnyIO process-pool workers can block indefinitely on undrained stderr</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-64847</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; agronholm anyio&lt;/p&gt;
&lt;p&gt;AnyIO is a high level asynchronous concurrency and networking framework that works on top of either Trio or asyncio. Prior to 4.14.2, AnyIO starts process-pool workers with standard error connected to a pipe that the parent never drains, even though the documented behavior redirects all three standard streams. Worker code that writes enough attacker-influenced data to sys.stderr can fill the pipe and block before returning the standard-output protocol response, causing the awaiting process-pool call to remain blocked indefinitely. Applications that run untrusted or faulty worker code capable of producing substantial standard-error output are affected. This issue is fixed in version 4.14.2.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; agronholm anyio&lt;/p&gt;
&lt;p&gt;AnyIO is a high level asynchronous concurrency and networking framework that works on top of either Trio or asyncio. Prior to 4.14.2, AnyIO starts process-pool workers with standard error connected to a pipe that the parent never drains, even though the documented behavior redirects all three standard streams. Worker code that writes enough attacker-influenced data to sys.stderr can fill the pipe and block before returning the standard-output protocol response, causing the awaiting process-pool call to remain blocked indefinitely. Applications that run untrusted or faulty worker code capable of producing substantial standard-error output are affected. This issue is fixed in version 4.14.2.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-64847</guid>
    </item>
    <item>
      <title>GHSA-5p39-cfhj-2xmp — AnyIO process-pool workers can block indefinitely on undrained stderr</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-5p39-cfhj-2xmp</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: anyio&lt;/p&gt;
&lt;p&gt;### Impact
AnyIO starts process-pool workers with stderr connected to a pipe but never drains that pipe. The worker redirects stdin and stdout to /dev/null to protect its protocol, but does not redirect stderr even though the documentation says all three standard streams are redirected. Worker code that writes enough attacker-influenced data to stderr can fill the pipe, block before returning the stdout protocol response, and wedge the awaiting process-pool call.&lt;/p&gt;
&lt;p&gt;Anyone who runs untrusted or faulty code that writes too much to `stderr` is at risk.&lt;/p&gt;
&lt;p&gt;### Patches
This vulnerability will be patched in v4.14.2.&lt;/p&gt;
&lt;p&gt;### Workarounds
Closing `sys.stderr` in the target function should at least prevent the deadlock.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: anyio&lt;/p&gt;
&lt;p&gt;### Impact
AnyIO starts process-pool workers with stderr connected to a pipe but never drains that pipe. The worker redirects stdin and stdout to /dev/null to protect its protocol, but does not redirect stderr even though the documentation says all three standard streams are redirected. Worker code that writes enough attacker-influenced data to stderr can fill the pipe, block before returning the stdout protocol response, and wedge the awaiting process-pool call.&lt;/p&gt;
&lt;p&gt;Anyone who runs untrusted or faulty code that writes too much to `stderr` is at risk.&lt;/p&gt;
&lt;p&gt;### Patches
This vulnerability will be patched in v4.14.2.&lt;/p&gt;
&lt;p&gt;### Workarounds
Closing `sys.stderr` in the target function should at least prevent the deadlock.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-5p39-cfhj-2xmp</guid>
    </item>
  </channel>
</rss>
