CVE-2026-9323

HIGHPre-NVD 8.18.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 8.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-18. A secondary CVSS source baseline 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 5 sources updated this week

Also known asEUVD-2026-45381 (ENISA EUVD) · GHSA-83x9-8wvq-rrcp (GitHub Security Advisories)Source: ENISA EUVD

8.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 8.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

The urwid web display backend (urwid/display/web.py) generates web session identifiers (urwid_id) in Screen.start() by concatenating two random.randrange(10**9) calls that use Python's Mersenne Twister PRNG, which is not cryptographically secure. Each call consumes approximately 30 bits of PRNG state, and the Mersenne Twister internal state is approximately 19,937 bits, so an attacker who observes approximately 334 session IDs (for example via the X-Urwid-ID HTTP response header) can fully reconstruct the internal state and predict all past and future session IDs (Path B). The same identifier is also used as the filename of a FIFO created in the world-listable /tmp directory (for example /tmp/urwid375487765176907690.in), so any local user on the host can list /tmp to enumerate active session tokens directly (Path A). With a valid session ID, an attacker can read the victim's terminal screen via the polling endpoint, inject keystrokes into the victim's session (yielding OS-level code execution with the session owner's privileges if the session runs a shell), and inject exit sequences or flood the FIFO to terminate or crash the session. A prior Bandit S311 warning on this usage was suppressed with # noqa: S311 rather than fixed

CVSS v3
8.1
EG Score
8.1HIGHmedium confidence
EG Risk
37
EG Risk 37/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)
Severity81% × 45%
Impact severity (EG Severity): CVSS 8.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.7% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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.
EPSS PROB
0.7%
EPSS %ILE
53rd
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 (8.1): severity, escalated by confirmed exploitation. This CVE's 8.1 is its impact severity (EG Severity), not escalated.

EG Severity
8.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-28). 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; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (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

July 18, 2026

Last Modified

September 15, 2026

Advisory Details (5)

Auto-updated Jul 18, 2026
Patch available. Sources: github_commit, github_pr.
Web page

Insecure PRNG and Information Exposure in urwid Web Display Backend | Advisories | VulnCheck

https://www.vulncheck.com/advisories/insecure-prng-and-information-exposure-in-urwid-web-display-backend
GitHub pull request Patch Available

Web display: use secure random session identifiers

Patch available: urwid/urwid 4.0.1 (PR #1128 merged 2026-04-28)

https://github.com/urwid/urwid/pull/1128
Web page

Security Vulnerabilities Found · Issue #1127 · urwid/urwid · GitHub

https://github.com/urwid/urwid/issues/1127
GitHub commit Patch Available

commit 24acd12f0d05 (urwid/urwid)

Patch available: urwid/urwid 4.0.2 (contains commit 24acd12f0d05)

https://github.com/urwid/urwid/commit/24acd12f0d0598036d0d577f2ee63e4a27b4a3d9
Web page

GitHub - urwid/urwid: Console user interface library for Python (official repo) · GitHub

https://github.com/urwid/urwid

Vendor Advisories for CVE-2026-9323(11)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(11)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntupython3-urwid (3.0.4-1ubuntu0.1~esm1) @ resolute2026-10-28ubuntu
redhatpython-urwid-0:2.5.3-4.el10_0.52026-08-26redhat
redhatpython-urwid-0:2.1.2-4.el9_4.12026-08-24redhat
redhatpython-urwid-0:2.1.2-4.el9_6.12026-08-24redhat
redhatpython-urwid-0:2.5.3-4.el10_2.52026-08-24redhat
redhatpython-urwid-0:1.3.1-4.el8_6.12026-08-24redhat
redhatpython-urwid-0:1.3.1-5.el8_102026-08-24redhat
redhatpython-urwid-0:2.1.2-4.el9_8.12026-08-24redhat
redhatpython-urwid-0:2.1.2-4.el9_2.12026-08-24redhat
redhatpython-urwid-0:1.3.1-4.el8_4.12026-08-20redhat
redhatpython-urwid-0:1.3.1-4.el8_8.12026-08-20redhat

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:11(1)
PackageVulnerable rangeFix by version rangeDependents
urwid2.1.2-1 ... 3.0.4-1 (17 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
urwid2.1.2-4
  • every version up to 2.1.2-4+deb12u1: fixed in 2.1.2-4+deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
urwid2.6.16-1, 3.0.4-1, 4.1.3-1, 4.2.1-1
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
urwid2.6.16-1, 3.0.4-1
  • every version up to 4.1.3-1: fixed in 4.1.3-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 12× in last 7d / 48× 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 it from the CNA feed. 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). Most recent first.

Showing the most recent 99 of 279 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 180 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  2. 2026-10-28 19:22 UTCEG score recompute
  3. 2026-10-28 19:22 UTCVendor advisory
  4. 2026-10-28 19:22 UTCGHSA enrichmentGHSA-83x9-8wvq-rrcp · GitHub severity CRITICAL · GitHub CVSS 8.1
  5. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  6. 2026-10-28 15:55 UTCOSV refresh
  7. 2026-10-27 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  8. 2026-10-26 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  9. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  10. 2026-10-25 13:50 UTCEG score recompute
  11. 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  12. 2026-10-23 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  13. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  14. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  15. 2026-10-20 19:28 UTCEG score recompute
  16. 2026-10-20 19:28 UTCVendor advisory
  17. 2026-10-20 19:28 UTCGHSA enrichmentGHSA-83x9-8wvq-rrcp · GitHub severity CRITICAL · GitHub CVSS 8.1
  18. 2026-10-20 16:34 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  19. 2026-10-19 16:34 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  20. 2026-10-18 02:59 UTCEG score recompute
  21. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  22. 2026-10-16 16:45 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  23. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  24. 2026-10-14 16:34 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  25. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
Show 74 more
  1. 2026-10-13 04:29 UTCEG score recompute
  2. 2026-10-13 04:29 UTCVendor advisory
  3. 2026-10-13 04:28 UTCGHSA enrichmentGHSA-83x9-8wvq-rrcp · GitHub severity CRITICAL · GitHub CVSS 8.1
  4. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  5. 2026-10-12 14:43 UTCEG score recompute
  6. 2026-10-11 19:12 UTCEG score recompute
  7. 2026-10-11 16:28 UTCEG score recompute
  8. 2026-10-11 13:50 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  9. 2026-10-11 13:42 UTCEG score recompute
  10. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  11. 2026-10-09 20:08 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  12. 2026-10-08 17:14 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  13. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  14. 2026-10-06 15:19 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  15. 2026-10-05 17:44 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  16. 2026-10-04 23:23 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  17. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  18. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  19. 2026-10-01 19:51 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  20. 2026-10-01 10:23 UTCEG score recompute
  21. 2026-10-01 10:23 UTCVendor advisory
  22. 2026-10-01 10:23 UTCGHSA enrichmentGHSA-83x9-8wvq-rrcp · GitHub severity CRITICAL · GitHub CVSS 8.1
  23. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  24. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  25. 2026-09-28 07:48 UTCEG score recompute
  26. 2026-09-28 07:48 UTCVendor advisory
  27. 2026-09-28 07:48 UTCGHSA enrichmentGHSA-83x9-8wvq-rrcp · GitHub severity CRITICAL · GitHub CVSS 8.1
  28. 2026-09-27 13:49 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  29. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  30. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  31. 2026-09-24 04:27 UTCEG score recompute
  32. 2026-09-24 04:27 UTCVendor advisory
  33. 2026-09-24 04:27 UTCGHSA enrichmentGHSA-83x9-8wvq-rrcp · GitHub severity CRITICAL · GitHub CVSS 8.1
  34. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  35. 2026-09-23 02:23 UTCEG score recompute
  36. 2026-09-23 02:23 UTCVendor advisory
  37. 2026-09-23 02:23 UTCGHSA enrichmentGHSA-83x9-8wvq-rrcp · GitHub severity CRITICAL · GitHub CVSS 8.1
  38. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  39. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  40. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  41. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  42. 2026-09-18 04:29 UTCEG score recompute
  43. 2026-09-18 04:29 UTCVendor advisory
  44. 2026-09-18 04:29 UTCGHSA enrichmentGHSA-83x9-8wvq-rrcp · GitHub severity CRITICAL · GitHub CVSS 8.1
  45. 2026-09-17 19:32 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  46. 2026-09-17 10:13 UTCEG score recompute
  47. 2026-09-17 10:13 UTCVendor advisory
  48. 2026-09-17 10:13 UTCGHSA enrichmentGHSA-83x9-8wvq-rrcp · GitHub severity CRITICAL · GitHub CVSS 8.1
  49. 2026-09-16 14:09 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  50. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  51. 2026-09-15 08:26 UTCEG score recompute
  52. 2026-09-15 08:26 UTCVendor advisory
  53. 2026-09-15 08:26 UTCGHSA enrichmentGHSA-83x9-8wvq-rrcp · GitHub severity CRITICAL · GitHub CVSS 8.1
  54. 2026-09-15 07:28 UTCEG score recompute
  55. 2026-09-15 07:28 UTCVendor advisory
  56. 2026-09-15 07:28 UTCGHSA enrichmentGHSA-83x9-8wvq-rrcp · GitHub severity CRITICAL · GitHub CVSS 8.1
  57. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  58. 2026-09-14 06:21 UTCVendor advisory
  59. 2026-09-14 06:21 UTCGHSA enrichmentGHSA-83x9-8wvq-rrcp · GitHub severity CRITICAL · GitHub CVSS 8.1
  60. 2026-09-13 17:26 UTCEG score recompute
  61. 2026-09-13 17:26 UTCVendor advisory
  62. 2026-09-13 17:26 UTCGHSA enrichmentGHSA-83x9-8wvq-rrcp · GitHub severity CRITICAL · GitHub CVSS 8.1
  63. 2026-09-13 16:48 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  64. 2026-09-13 04:31 UTCEG score recompute
  65. 2026-09-13 04:31 UTCVendor advisory
  66. 2026-09-13 04:31 UTCGHSA enrichmentGHSA-83x9-8wvq-rrcp · GitHub severity CRITICAL · GitHub CVSS 8.1
  67. 2026-09-12 15:02 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  68. 2026-09-12 10:27 UTCVendor advisory
  69. 2026-09-12 10:27 UTCGHSA enrichmentGHSA-83x9-8wvq-rrcp · GitHub severity CRITICAL · GitHub CVSS 8.1
  70. 2026-09-11 21:03 UTCEG score recompute
  71. 2026-09-11 21:03 UTCVendor advisory
  72. 2026-09-11 21:03 UTCGHSA enrichmentGHSA-83x9-8wvq-rrcp · GitHub severity CRITICAL · GitHub CVSS 8.1
  73. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  74. 2026-09-11 09:38 UTCEPSS rescoreEPSS 0.4% · 35th percentile

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-9323?
CVE-2026-9323 is a high-severity vulnerability; its CVE record was published on July 18, 2026. The urwid web display backend (urwid/display/web.py) generates web session identifiers (urwid_id) in Screen.start() by concatenating two random.randrange(109) calls that use Python's Mersenne Twister PRNG, which is not cryptographically secure. Each call consumes approximately 30 bits of PRNG…
When was CVE-2026-9323 made public?
CVE-2026-9323 was made public on July 18, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on July 18, 2026. EchelonGraph's copy of the record carries a last-modified date of September 15, 2026; the record at its source may have been updated since.
Is CVE-2026-9323 actively exploited?
CVE-2026-9323 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (53rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-9323?
CVE-2026-9323 has a CVSS base score of 8.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-9323?
A fix for CVE-2026-9323 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-9323 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-9323

Explore →

Is Your Infrastructure Affected by CVE-2026-9323?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs