Skip to main content
VulnerabilityPublished

CVE-2026-103022: Urwid · handle_short_request() crashes on non-ASCII POST body (UnicodeEncodeError DoS)

Affects vitSource GCVE Database

0
Compare
Authoritative record:CVE-2026-103022· Medium 5.3

Not known to be exploited · CVSS 5.3 Medium : upgrade to 2.3.5 when convenient.

Data as of 10 Nov 2026, 18:55 UTC

CVSS 3.1 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.15.3
Patch
Available – fixed in 2.3.5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.

What to do

Upgrade vit to 2.3.5.

Affected software

ProductAffectedFixed in
Homebrewvitpkg:brew/vitOther threatsAffected
  • >=2.0.0_1 <2.3.5
Fixed in
  • 2.3.5

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available in Urwid version 4.0.7. Users should upgrade to version 4.0.7 or later to resolve this issue. No direct workaround exists other than disabling the Urwid web display interface.

Description

The Urwid library's handle_short_request() function crashes when processing POST requests with non-ASCII bytes in the body, causing an unhandled UnicodeEncodeError and resulting in HTTP 500 errors. This leads to a denial of service (DoS) for users of the Urwid web interface. The issue affects Urwid versions up to 4.0.6 and is fixed in version 4.0.7. No direct workaround exists other than disabling the web interface.

References

Community reviews

Loading reviews…