CVE-2026-9323: Insecure PRNG and Information Exposure in urwid Web Display Backend
Noroxi assessment
Priority: Monitor (action score 36/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.71% (FIRST EPSS); higher than 53.9% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: python3-urwid (AlmaLinux:10) 2.5.3-4.el10_2.5; python3-urwid (AlmaLinux:8) 1.3.1-5.el8_10; python3-urwid (AlmaLinux:9) 2.1.2-4.el9_8.1.
Low priority for now. Upgrade to python3-urwid (AlmaLinux:10) 2.5.3-4.el10_2.5; python3-urwid (AlmaLinux:8) 1.3.1-5.el8_10; python3-urwid (AlmaLinux:9) 2.1.2-4.el9_8.1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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
- EUVD-2026-45381
- ALSA-2026:58561
- ALSA-2026:58562
- ALSA-2026:58952
- openSUSE-SU-2026:11356-1
- RHSA-2026:57637
- RHSA-2026:57638
- RHSA-2026:58561
- RHSA-2026:58562
- RHSA-2026:58952
- RHSA-2026:58953
- RHSA-2026:58954
- RHSA-2026:58955
- RHSA-2026:59198
- RHSA-2026:60353
- RLSA-2026:58561
- RLSA-2026:58562
- RLSA-2026:58952
- SUSE-SU-2026:3425-1
- SUSE-SU-2026:3460-1
- Published
- Jul 18, 2026
- Updated
- Nov 8, 2026
- EPSS
- 0.7% · 53th percentile
- CWE
- CWE-338
Report tools
Action score
36
Monitor
Low priority for now.
- CVSS
- 36 / 40 · 9.2 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.7%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · VulnCheck
- 9.2
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (VulnCheck). Independent of NVD's CPE analysis and usually ahead of it.
urwid urwid
- up to and including 24acd12affected · git
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | python3-urwid | before 2.5.3-4.el10_2.5 | 2.5.3-4.el10_2.5 |
| AlmaLinux:8 | python3-urwid | before 1.3.1-5.el8_10 | 1.3.1-5.el8_10 |
| AlmaLinux:9 | python3-urwid | before 2.1.2-4.el9_8.1 | 2.1.2-4.el9_8.1 |
| Debian:12 | urwid | before 2.1.2-4+deb12u1 | 2.1.2-4+deb12u1 |
| Debian:13 | urwid | from 0 | — |
| Debian:14 | urwid | before 4.1.3-1 | 4.1.3-1 |
| openSUSE:Tumbleweed | python-urwid | before 4.0.5-1.1 | 4.0.5-1.1 |
| Red Hat:enterprise_linux_eus:10.0 | python-urwid | before 0:2.5.3-4.el10_0.5 | 0:2.5.3-4.el10_0.5 |
| Red Hat:enterprise_linux_eus:10.0 | python-urwid-debugsource | before 0:2.5.3-4.el10_0.5 | 0:2.5.3-4.el10_0.5 |
| Red Hat:enterprise_linux_eus:10.0 | python3-urwid | before 0:2.5.3-4.el10_0.5 | 0:2.5.3-4.el10_0.5 |
| Red Hat:enterprise_linux_eus:10.0 | python3-urwid-debuginfo | before 0:2.5.3-4.el10_0.5 | 0:2.5.3-4.el10_0.5 |
| Red Hat:enterprise_linux:10.2 | python-urwid | before 0:2.5.3-4.el10_2.5 | 0:2.5.3-4.el10_2.5 |
| Red Hat:enterprise_linux:10.2 | python-urwid-debugsource | before 0:2.5.3-4.el10_2.5 | 0:2.5.3-4.el10_2.5 |
| Red Hat:enterprise_linux:10.2 | python3-urwid | before 0:2.5.3-4.el10_2.5 | 0:2.5.3-4.el10_2.5 |
| Red Hat:enterprise_linux:10.2 | python3-urwid-debuginfo | before 0:2.5.3-4.el10_2.5 | 0:2.5.3-4.el10_2.5 |
| Red Hat:enterprise_linux:8::baseos | python-urwid | before 0:1.3.1-5.el8_10 | 0:1.3.1-5.el8_10 |
| Red Hat:enterprise_linux:8::baseos | python-urwid-debugsource | before 0:1.3.1-5.el8_10 | 0:1.3.1-5.el8_10 |
| Red Hat:enterprise_linux:8::baseos | python3-urwid | before 0:1.3.1-5.el8_10 | 0:1.3.1-5.el8_10 |
| Red Hat:enterprise_linux:8::baseos | python3-urwid-debuginfo | before 0:1.3.1-5.el8_10 | 0:1.3.1-5.el8_10 |
| Red Hat:enterprise_linux:9::baseos | python-urwid | before 0:2.1.2-4.el9_8.1 | 0:2.1.2-4.el9_8.1 |
| Red Hat:enterprise_linux:9::baseos | python-urwid-debugsource | before 0:2.1.2-4.el9_8.1 | 0:2.1.2-4.el9_8.1 |
| Red Hat:enterprise_linux:9::baseos | python3-urwid | before 0:2.1.2-4.el9_8.1 | 0:2.1.2-4.el9_8.1 |
| Red Hat:enterprise_linux:9::baseos | python3-urwid-debuginfo | before 0:2.1.2-4.el9_8.1 | 0:2.1.2-4.el9_8.1 |
| Red Hat:rhel_aus:8.4::baseos | python-urwid | before 0:1.3.1-4.el8_4.1 | 0:1.3.1-4.el8_4.1 |
+28
Same product
urwid: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-103022Urwid: handle_short_request() crashes on non-ASCII POST body (UnicodeEncodeError DoS)21Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| almalinux:python3-urwid | 2.5.3-4.el10_2.5 · AlmaLinux:10 | Package registry (OSV) |
| debian:urwid | 2.1.2-4+deb12u1 · Debian:12 | Package registry (OSV) |
| opensuse:python-urwid | 4.0.5-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:python-urwid | 0:1.3.1-4.el8_8.1 · Red Hat:rhel_e4s:8.8::baseos | Package registry (OSV) |
| red hat:python-urwid-debugsource | 0:1.3.1-4.el8_8.1 · Red Hat:rhel_e4s:8.8::baseos | Package registry (OSV) |
| red hat:python3-urwid | 0:1.3.1-4.el8_8.1 · Red Hat:rhel_e4s:8.8::baseos | Package registry (OSV) |
| red hat:python3-urwid-debuginfo | 0:1.3.1-4.el8_8.1 · Red Hat:rhel_e4s:8.8::baseos | Package registry (OSV) |
| rocky linux:python-urwid | 0:2.5.3-4.el10_2.5 · Rocky Linux:10 | Package registry (OSV) |
| suse:python-urwid | 2.1.2-150400.11.6.1 · SUSE:Linux Enterprise Module for Python 3 15 SP7 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Katriel Mosesreporter
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-338 · Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)CVSS vector
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- github.com/urwid/urwid/commit/24acd12f0d0598036d0d577f2ee63e4a27b4a3d9
- github.com/urwid/urwid/issues/1127
- github.com/urwid/urwid/pull/1128
- github.com/urwid/urwid/security/advisories/GHSA-rjwp-g85x-gmjv
- www.vulncheck.com/advisories/insecure-prng-and-information-exposure-in-urwid-web-display-backend
- lists.debian.org/debian-lts-announce/2026/09/msg00015.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.