GCVE Workshop - 22 September 2026 (14:00-18:00), Luxembourg Before The Vulnopticon Conference - Registration

BREW-YEWTUBE-CVE-2026-64847 (GHSA-5P39-CFHJ-2XMP)

Vulnerability from osv_homebrew – Published: 2026-09-18 19:37 – Updated: 2026-09-18 19:37 – Source website
VLAI
Summary
AnyIO process-pool workers can block indefinitely on undrained stderr
Details

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.

Anyone who runs untrusted or faulty code that writes too much to stderr is at risk.

Patches

This vulnerability will be patched in v4.14.2.

Workarounds

Closing sys.stderr in the target function should at least prevent the deadlock.


{
  "affected": [
    {
      "ecosystem_specific": {
        "fix": "bump",
        "range_state": "fixed",
        "resource": "anyio",
        "resource_purl": "pkg:pypi/anyio@4.15.1",
        "upstream_fixed_in": "4.14.2"
      },
      "package": {
        "ecosystem": "Homebrew",
        "name": "yewtube",
        "purl": "pkg:brew/yewtube"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "2.10.5"
            },
            {
              "fixed": "2.13.1_4"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "database_specific": {
    "confidence": "high",
    "source": "matched",
    "strategy": "registry",
    "upstream_evidence": [
      {
        "ecosystem": "PyPI",
        "key": "pkg:pypi/anyio@4.15.1",
        "name": "anyio",
        "resource": "anyio",
        "strategy": "registry",
        "subject_version": "4.15.1"
      }
    ]
  },
  "details": "### Impact\nAnyIO 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.\n\nAnyone who runs untrusted or faulty code that writes too much to `stderr` is at risk.\n\n### Patches\nThis vulnerability will be patched in v4.14.2.\n\n### Workarounds\nClosing `sys.stderr` in the target function should at least prevent the deadlock.",
  "id": "BREW-yewtube-CVE-2026-64847",
  "modified": "2026-09-18T19:37:42Z",
  "published": "2026-09-18T19:37:42Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/agronholm/anyio/security/advisories/GHSA-5p39-cfhj-2xmp"
    },
    {
      "type": "WEB",
      "url": "https://github.com/agronholm/anyio/pull/1207"
    },
    {
      "type": "WEB",
      "url": "https://github.com/agronholm/anyio/commit/f1b7301c8264b0d2e8d24a5788fd29e93dea4040"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/agronholm/anyio"
    },
    {
      "type": "WEB",
      "url": "https://github.com/agronholm/anyio/releases/tag/4.14.2"
    }
  ],
  "schema_version": "1.7.3",
  "severity": [
    {
      "score": "CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N",
      "type": "CVSS_V4"
    }
  ],
  "summary": "AnyIO process-pool workers can block indefinitely on undrained stderr",
  "upstream": [
    "GHSA-5p39-cfhj-2xmp",
    "CVE-2026-64847"
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…

Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.


Loading…