<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-03T19:07:15.715749+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/brew-aider-cve-2026-64847</id>
    <title>BREW-aider-CVE-2026-64847 — AnyIO process-pool workers can block indefinitely on undrained stderr</title>
    <updated>2026-10-03T19:07:17.768115+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Homebrew: aider</p>
<p>### 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.</p>
<p>Anyone who runs untrusted or faulty code that writes too much to `stderr` is at risk.</p>
<p>### Patches
This vulnerability will be patched in v4.14.2.</p>
<p>### Workarounds
Closing `sys.stderr` in the target function should at least prevent the deadlock.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/brew-aider-cve-2026-64847"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1249</id>
    <title>certfr-2026-avi-1249 — De multiples vulnérabilités ont été découvertes dans les produits VMware. Elles permettent à un attaquant de provoquer…</title>
    <updated>2026-10-03T19:07:17.768189+00:00</updated>
    <content>certfr-2026-avi-1249</content>
    <link href="https://cve.radiocsirt.org/vuln/certfr-2026-avi-1249"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cleanstart-2026-hn56879</id>
    <title>CLEANSTART-2026-HN56879 — AnyIO is a high level asynchronous concurrency and networking framework that works on top of either Trio or asyncio</title>
    <updated>2026-10-03T19:07:17.768210+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> CleanStart: airflow-3</p>
<p>CVE-2026-64847 affects multiple packages. AnyIO is a high level asynchronous concurrency and networking framework that works on top of either Trio or asyncio. See references for individual vulnerability details.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cleanstart-2026-hn56879"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-372241</id>
    <title>EUVD-2026-372241</title>
    <updated>2026-10-03T19:07:17.768231+00:00</updated>
    <content>EUVD-2026-372241</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-372241"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-64847</id>
    <title>fkie_cve-2026-64847</title>
    <updated>2026-10-03T19:07:17.768243+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-64847"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-5p39-cfhj-2xmp</id>
    <title>GHSA-5p39-cfhj-2xmp — AnyIO process-pool workers can block indefinitely on undrained stderr</title>
    <updated>2026-10-03T19:07:17.768267+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: anyio</p>
<p>### 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.</p>
<p>Anyone who runs untrusted or faulty code that writes too much to `stderr` is at risk.</p>
<p>### Patches
This vulnerability will be patched in v4.14.2.</p>
<p>### Workarounds
Closing `sys.stderr` in the target function should at least prevent the deadlock.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-5p39-cfhj-2xmp"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/pysec-2026-4024</id>
    <title>PYSEC-2026-4024 — AnyIO process-pool workers can block indefinitely on undrained stderr</title>
    <updated>2026-10-03T19:07:17.768290+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: anyio</p>
<p>### 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.</p>
<p>Anyone who runs untrusted or faulty code that writes too much to `stderr` is at risk.</p>
<p>### Patches
This vulnerability will be patched in v4.14.2.</p>
<p>### Workarounds
Closing `sys.stderr` in the target function should at least prevent the deadlock.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/pysec-2026-4024"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/rhsa-2026:70965</id>
    <title>RHSA-2026:70965 — Red Hat Security Advisory: Red Hat AI Inference 3.4.5 (cpu)</title>
    <updated>2026-10-03T19:07:17.768312+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>python-transformers: python-transformers: Arbitrary code execution due to overridden trust_remote_code setting vllm: vLLM: Denial of Service via unbounded video frame processing aiohttp: AIOHTTP: Arbitrary code execution via untrusted input to CookieJar.load() vllm: vLLM: Arbitrary code execution via malicious HuggingFace model vllm: vLLM: Denial of Service via malformed tensor shape in speculative decoding Diffusers: Diffusers: Arbitrary remote code execution via `trust_remote_code` bypass diffusers: Diffusers: Arbitrary Code Execution via malicious model loading diffusers: Diffusers: Arbitrary code execution due to trust_remote_code guard bypass python-pyjwt: PyJWT: Authentication bypass due to forged JSON Web Tokens starlette: Starlette: Security restriction bypass via malformed HTTP Host header vllm: starlette: vLLM: Critical authentication bypass allows unauthorized API access Pillow: Pillow: Memory disclosure or denial of service via crafted McIdas AREA image python-pillow: Pillow: Denial of Service via excessive memory allocation when processing font files vllm: vLLM: Denial of Service via malformed speculative decoding workload starlette: Starlette: request.form() limits silently ignored for application/x-www-form-urlencoded enable DoS python-pillow: Pillow: Denial of Service via crafted BDF font file python-pillow: Pillow: Denial of Service via crafted GD 2.x image file vllm: vLLM: Denial of Service via adversarial regular expression in structured outputs API msgpac…</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/rhsa-2026:70965"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-64847</id>
    <title>UBUNTU-CVE-2026-64847</title>
    <updated>2026-10-03T19:07:17.768387+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:22.04:LTS: python-anyio, Ubuntu:24.04:LTS: python-anyio, Ubuntu:26.04:LTS: python-anyio</p>
<p>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.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-64847"/>
  </entry>
</feed>
