Urwid is a console user interface library for Python. Prior to 4.0.7, handle_short_request() in urwid/display/web.py performs unguarded character encoding on POST input and unguarded UTF-8 decoding on polling update socket output. A remote attacker who obtains a valid X-Urwid-ID session token can submit non-ASCII POST data that raises UnicodeEncodeError, while non-UTF-8 polling output raises UnicodeDecodeError, causing the CGI handler to return an error and terminate request processing. The POST exception path also leaves an opened file descriptor unclosed for the CGI process lifetime, so repeated requests can cause denial of service for the web display interface. This issue is fixed in version 4.0.7.
CVE-2026-103022
MEDIUMPre-NVD 5.35.3
EchelonGraph scoreHIGH confidence
“—” beside the score: it is equal to the CVSS score beside it.
Score 5.3 from GitHub Security Advisory (severity: MODERATE) published 2026-11-09. A secondary CVSS source baseline 5.3; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Also known asEUVD-2026-118521 (ENISA EUVD) · GHSA-cp25-j9x5-p5xm (GitHub Security Advisories)Source: ENISA EUVD
5.3EG
EchelonGraph verdictMonitorRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 5.3Exploit: None knownExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 5.3
- EG Score
- 5.3MEDIUMhigh confidence
- EG Risk
- 39EG Risk 39/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity53% × 45%Impact severity (EG Severity): CVSS 5.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation0.5% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability100% × 15%CISA's SSVC Automatable value: yes (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 0.5%
- EPSS %ILE
- 41st
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (5.3): severity, escalated by confirmed exploitation. This CVE's 5.3 is its impact severity (EG Severity), not escalated.
- EG Severity
- 5.3 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
November 6, 2026
Last Modified
November 12, 2026
Advisory Details (4)
Auto-updated Nov 6, 2026Patch available. Sources: github, github_commit, github_pr, github_release.
GitHub release Patch Available
4.0.7
Patch available: urwid/urwid 4.0.7
https://github.com/urwid/urwid/releases/tag/4.0.7GitHub commit Patch Available
commit b79d9a96843a (urwid/urwid)
Patch available: urwid/urwid 4.0.7 (contains commit b79d9a96843a)
https://github.com/urwid/urwid/commit/b79d9a96843a6f5950bb2bfab5d059bdc61c538bGitHub pull request Patch Available
Fix encoding handling by web display
Patch available: urwid/urwid 4.0.7 (PR #1201 merged 2026-07-24)
https://github.com/urwid/urwid/pull/1201GitHub advisoryMentions a patch (unverified)
handle_short_request() crashes on non-ASCII POST body (UnicodeEncodeError DoS) · Advisory · urwid/urwid · GitHub
https://github.com/urwid/urwid/security/advisories/GHSA-cp25-j9x5-p5xmVendor Advisories for CVE-2026-103022(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(1)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| pip | urwid @ 4.0.7 (fixes <= 4.0.6) | — | ghsa |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(4 across 4 ecosystems)
Debian:12(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| urwid | 2.1.2-4 ... 4.2.5-1 (18 versions) |
| — |
Debian:13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| urwid | 2.6.16-1, 3.0.4-1, 4.1.3-1, 4.2.1-1, 4.2.5-1 |
| — |
Debian:14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| urwid | 2.6.16-1, 3.0.4-1 |
| — |
PyPI(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| urwid | 0.8.0 ... 4.0.6 (92 versions) |
| — |
Weakness Classification(3)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 12× in last 7d / 12× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.
- 2026-11-12 22:31 UTCEchelonGraph re-scored
- 2026-11-12 22:31 UTCGHSA enrichmentGHSA-cp25-j9x5-p5xm · GitHub severity MODERATE · GitHub CVSS 5.3
- 2026-11-12 16:32 UTCEPSS rescoreEPSS 0.5% · 41st percentile
- 2026-11-11 16:37 UTCEPSS rescoreEPSS 0.5% · 41st percentile
- 2026-11-11 05:29 UTCEchelonGraph re-scored
- 2026-11-11 05:29 UTCGHSA enrichmentGHSA-cp25-j9x5-p5xm · GitHub severity MODERATE · GitHub CVSS 5.3
- 2026-11-11 03:49 UTCEchelonGraph re-scored
- 2026-11-11 03:49 UTCGHSA enrichmentGHSA-cp25-j9x5-p5xm · GitHub severity MODERATE · GitHub CVSS 5.3
- 2026-11-10 16:41 UTCEPSS rescoreEPSS 0.5% · 41st percentile
- 2026-11-09 22:45 UTCEchelonGraph re-scored
- 2026-11-09 22:45 UTCGHSA enrichmentGHSA-cp25-j9x5-p5xm · GitHub severity MODERATE · GitHub CVSS 5.3
- 2026-11-09 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
- 2026-11-08 16:37 UTCEPSS rescoreEPSS 0.5% · 41st percentile
- 2026-11-07 16:37 UTCEPSS rescoreEPSS 0.5% · 41st percentile
- 2026-11-06 22:27 UTCEchelonGraph re-scored
- 2026-11-06 22:04 UTCENISA EUVD ID recordedEUVD-2026-118521 · Source: ENISA EUVD
- 2026-11-06 21:36 UTCEchelonGraph re-scoredFirst assessed: 5.3 MEDIUM
- 2026-11-06 21:36 UTCMITRE cvelistV5first tracked
Related CVEs(same product + same CWE)
Frequently asked(5)
What is CVE-2026-103022?
CVE-2026-103022 is a medium-severity vulnerability; its CVE record was published on November 6, 2026. Urwid is a console user interface library for Python. Prior to 4.0.7, handle_short_request() in urwid/display/web.py performs unguarded character encoding on POST input and unguarded UTF-8 decoding on polling update socket output. A remote attacker who obtains a valid X-Urwid-ID session token can…
When was the CVE record for CVE-2026-103022 published?
The CVE record for CVE-2026-103022 was published on November 6, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 12, 2026; the record at its source may have been updated since.
Is CVE-2026-103022 actively exploited?
CVE-2026-103022 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (41st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-103022?
CVE-2026-103022 has a CVSS base score of 5.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-103022?
A fix for CVE-2026-103022 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-103022 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-103022
Is Your Infrastructure Affected by CVE-2026-103022?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.