Soup Sieve is a CSS selector library designed to be used with Beautiful Soup 4. Prior to 2.8.4, the CSS selector parser in soupsieve allocates unbounded memory when compiling large comma-separated selector lists, allowing an attacker who can supply a crafted selector string to soupsieve.compile() or Beautiful Soup .select() / .select_one() to allocate hundreds of megabytes of heap memory from a relatively small input and cause denial of service. This issue is fixed in version 2.8.4.
CVE-2026-49476
This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 58% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 7.5
- EG Score
- 7.5(medium)
- EG Risk
- 65(Attend)EG Risk 65/100SSVC: Attend
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity75% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 1%
- EPSS %ILE
- 42%
- KEV
- Not listed
Published
July 9, 2026
Last Modified
July 28, 2026
Advisory Details (3)
Auto-updated Jul 15, 2026Memory Exhaustion via Large Comma-Separated Selector Lists in soupsieve · Advisory · facelessuser/soupsieve · GitHub
https://github.com/facelessuser/soupsieve/security/advisories/GHSA-2wc2-fm75-p42x2.8.4
Patch available: facelessuser/soupsieve 2.8.4
https://github.com/facelessuser/soupsieve/releases/tag/2.8.4commit 28108ab80581 (facelessuser/soupsieve)
Patch available: facelessuser/soupsieve 2.8.4 (contains commit 28108ab80581)
https://github.com/facelessuser/soupsieve/commit/28108ab805818c832d9568142a99844fd95a0d39Vendor Advisories for CVE-2026-49476(4)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- RHSA-2026:60520Red Hat Product SecurityCritical
Red Hat Security Advisory: RHOAI 3.4.4 - Red Hat OpenShift AI
- GHSA-2wc2-fm75-p42xGitHub Security AdvisoriesHigh
Soup Sieve has Memory Exhaustion via Large Comma-Separated Selector Lists
- RHSA-2026:34119Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update
- RHSA-2026:23992Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update
Patch Availability(3)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | rhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9:1787073593 | 2026-08-27 | redhat |
| redhat | python-rpds-py-main-2026.6.3-1.hum1 | 2026-07-01 | redhat |
| redhat | python-attrs-main-26.1.0-3.hum1 | 2026-06-07 | redhat |
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
(5 across 5 ecosystems)
Debian:11(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| soupsieve | 2.2.1-1 ... 2.8.4-1 (15 versions) | — | — |
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| soupsieve | 2.3.2-1 ... 2.8.4-1 (11 versions) | — | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| soupsieve | 2.7-1, 2.7-2, 2.8.1-1, 2.8.3-1, 2.8.4-1 | — | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| soupsieve | 2.7-1, 2.7-2, 2.8.1-1, 2.8.3-1 | 2.8.4-1 | — |
PyPI(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| soupsieve | 0.4 ... 2.8.3 (51 versions) | 2.8.4 | — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 19× in last 7d / 106× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.
Showing the most recent 100 of 143 total refreshes for this CVE.
- 2026-08-30 06:56 UTCEG score recompute
- 2026-08-30 06:56 UTCVendor advisory
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-28 21:41 UTCEPSS rescore
- 2026-08-27 21:46 UTCEG score recompute
- 2026-08-27 21:46 UTCVendor advisory
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-27 01:10 UTCEG score recompute
- 2026-08-27 01:10 UTCVendor advisory
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-26 03:53 UTCEG score recompute
- 2026-08-26 03:53 UTCVendor advisory
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-25 11:10 UTCVendor advisory
- 2026-08-24 22:11 UTCEG score recompute
- 2026-08-24 22:11 UTCVendor advisory
- 2026-08-24 09:37 UTCEG score recompute
- 2026-08-24 09:37 UTCVendor advisory
- 2026-08-23 18:51 UTCVendor advisory
- 2026-08-23 06:20 UTCEG score recompute
- 2026-08-23 06:20 UTCVendor advisory
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 17:49 UTCVendor advisory
- 2026-08-22 05:17 UTCEG score recompute
- 2026-08-22 05:17 UTCVendor advisory
Show 75 moreShow fewer
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 16:43 UTCVendor advisory
- 2026-08-21 03:51 UTCEG score recompute
- 2026-08-21 03:51 UTCVendor advisory
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 15:17 UTCVendor advisory
- 2026-08-20 01:50 UTCEG score recompute
- 2026-08-20 01:50 UTCVendor advisory
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 09:17 UTCVendor advisory
- 2026-08-18 20:43 UTCEG score recompute
- 2026-08-18 20:43 UTCVendor advisory
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-18 04:24 UTCVendor advisory
- 2026-08-17 15:44 UTCEG score recompute
- 2026-08-17 15:44 UTCVendor advisory
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 03:13 UTCEG score recompute
- 2026-08-17 03:13 UTCVendor advisory
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 14:42 UTCEG score recompute
- 2026-08-16 14:42 UTCVendor advisory
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-16 02:10 UTCVendor advisory
- 2026-08-15 13:40 UTCEG score recompute
- 2026-08-15 13:40 UTCVendor advisory
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-15 01:09 UTCVendor advisory
- 2026-08-14 12:38 UTCVendor advisory
- 2026-08-14 00:07 UTCEG score recompute
- 2026-08-14 00:07 UTCVendor advisory
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 11:35 UTCVendor advisory
- 2026-08-12 23:04 UTCEG score recompute
- 2026-08-12 23:04 UTCVendor advisory
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-12 10:34 UTCVendor advisory
- 2026-08-11 22:02 UTCEG score recompute
- 2026-08-11 22:02 UTCVendor advisory
- 2026-08-11 09:31 UTCEG score recompute
- 2026-08-11 09:31 UTCVendor advisory
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 21:00 UTCVendor advisory
- 2026-08-10 08:28 UTCVendor advisory
- 2026-08-09 19:58 UTCEG score recompute
- 2026-08-09 19:58 UTCVendor advisory
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-09 07:27 UTCVendor advisory
- 2026-08-08 18:56 UTCEG score recompute
- 2026-08-08 18:56 UTCVendor advisory
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-08 06:24 UTCVendor advisory
- 2026-08-07 17:53 UTCEG score recompute
- 2026-08-07 17:53 UTCVendor advisory
- 2026-08-07 05:22 UTCVendor advisory
- 2026-08-06 16:51 UTCEG score recompute
- 2026-08-06 16:51 UTCVendor advisory
- 2026-08-06 13:47 UTCEPSS rescore
- 2026-08-06 04:20 UTCEG score recompute
- 2026-08-06 04:20 UTCVendor advisory
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-05 15:50 UTCVendor advisory
- 2026-08-05 02:35 UTCEG score recompute
- 2026-08-05 02:35 UTCVendor advisory
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-04 14:04 UTCEG score recompute
- 2026-08-04 14:04 UTCVendor advisory
- 2026-08-04 10:39 UTCEPSS rescore
- 2026-08-04 01:26 UTCVendor advisory
- 2026-08-03 12:55 UTCEG score recompute
- 2026-08-03 12:55 UTCVendor advisory
- 2026-08-03 10:36 UTCEPSS rescore
- 2026-08-02 22:21 UTCVendor advisory
- 2026-08-02 09:50 UTCEG score recompute
- 2026-08-02 09:50 UTCVendor advisory
Related CVEs(same vendor + same CWE)
Same vendor
10 shownredhat
- CVE-2001-0825EG 10.0HIGH
- CVE-2001-1009EG 10.0EPSS p93HIGH
- CVE-2001-0554EG 10.0EPSS p99HIGH
- CVE-2001-1162EG 10.0EPSS p96HIGH
- CVE-2001-0414EG 10.0EPSS p100HIGH
- CVE-2001-0191EG 10.0EPSS p92HIGH
- CVE-2001-0301EG 10.0EPSS p91HIGH
- CVE-2001-0197EG 10.0EPSS p96HIGH
- CVE-2001-0233EG 10.0EPSS p96HIGH
- CVE-2001-0010EG 10.0EPSS p98HIGH
Same CWE
10 shownCWE-400 · CWE-770
- CVE-2004-1464NVD 5.9EG 9.0 KEVEPSS p91CRITICAL
- CVE-2010-3705EG 8.3HIGH
- CVE-2006-1364NVD 7.5EG 8.2EPSS p99HIGH
- CVE-2008-5180NVD 5.3EG 7.9EPSS p99HIGH
- CVE-2012-0024EG 7.8HIGH
- CVE-2011-3192EG 7.8EPSS p100HIGH
- CVE-2010-4686EG 7.8HIGH
- CVE-2010-4671EG 7.8HIGH
- CVE-2009-2054EG 7.8HIGH
- CVE-2009-2726EG 7.8EPSS p93HIGH
Frequently asked(5)
What is CVE-2026-49476?
When was CVE-2026-49476 disclosed?
Is CVE-2026-49476 actively exploited?
What is the CVSS score of CVE-2026-49476?
How do I remediate CVE-2026-49476?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-49476
Is Your Infrastructure Affected by CVE-2026-49476?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.