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

BREW-YEWTUBE-CVE-2026-63374 (GHSA-82R6-8W77-94W6)

Vulnerability from osv_homebrew – Published: 2026-09-18 19:37 – Updated: 2026-09-18 19:37 – Source website
VLAI
Summary
AnyIO: TLSStream IDNA 2003 host name encoding enables potential TLS certificate spoofing
Details

Impact

Services using internationalized (non-ASCII) domain names are potentially vulnerable to TLS connections made from AnyIO's connect_tcp() or directly via TLSStream.wrap() where the connection has (through other means) been hijacked and redirected to a malicious server. The attacker would obtain a legitimate certificate using the IDNA 2003 encoded version of the domain name and offer it to the connecting client, making the certificate validate properly on the client's end.

Patches

The vulnerability will be patched in v4.14.2.

Workarounds

Encode host names via the idna package prior to connecting.


{
  "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\nServices using internationalized (non-ASCII) domain names are potentially vulnerable to TLS connections made from AnyIO\u0027s `connect_tcp()` or directly via `TLSStream.wrap()` where the connection has (through other means) been hijacked and redirected to a malicious server. The attacker would obtain a legitimate certificate using the IDNA 2003 encoded version of the domain name and offer it to the connecting client, making the certificate validate properly on the client\u0027s end.\n\n### Patches\nThe vulnerability will be patched in v4.14.2.\n\n### Workarounds\nEncode host names via the `idna` package prior to connecting.",
  "id": "BREW-yewtube-CVE-2026-63374",
  "modified": "2026-09-18T19:37:42Z",
  "published": "2026-09-18T19:37:42Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/agronholm/anyio/security/advisories/GHSA-82r6-8w77-94w6"
    },
    {
      "type": "WEB",
      "url": "https://github.com/agronholm/anyio/pull/1208"
    },
    {
      "type": "WEB",
      "url": "https://github.com/agronholm/anyio/commit/68f58915f82d9be8109ebbbd8f5d70577d43f2ce"
    },
    {
      "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:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N",
      "type": "CVSS_V4"
    }
  ],
  "summary": "AnyIO: TLSStream IDNA 2003 host name encoding enables potential TLS certificate spoofing",
  "upstream": [
    "GHSA-82r6-8w77-94w6",
    "CVE-2026-63374"
  ]
}



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…