jupyter-notebook: The package sanitize-html before 2.7.1 are vulnerable to Regular Expression Denial of Service (ReDoS) due to insecure...
CVE-2022-25887 is fixed in 3 products on 1 platform, first by jupyter-notebook 6.4.8-1ubuntu0.1+esm1, released August 29, 2022. It is not reported as exploited. Patch Radar priority: High.
The package sanitize-html before 2.7.1 are vulnerable to Regular Expression Denial of Service (ReDoS) due to insecure global regular expression replacement logic of HTML comment removal.
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| jupyter-notebook · Ubuntu 22.04.1 LTS (jammy) | 6.4.8-1ubuntu0.1+esm1 | jupyter-notebook 6.4.8-1ubuntu0.1+esm1 | Aug 29, 2022 |
| jupyter-notebook · Ubuntu 24.04.5 LTS (noble) | 6.4.12-2.2ubuntu1+esm1 | jupyter-notebook 6.4.12-2.2ubuntu1+esm1 | Aug 29, 2022 |
| jupyter-notebook · Ubuntu 24.10 (oracular) | 6.4.13-2ubuntu0.1 | jupyter-notebook 6.4.13-2ubuntu0.1 | Jan 16, 2026 |
| jupyter-notebook · Ubuntu 25.04 (plucky) | 6.4.13-5ubuntu0.1 | jupyter-notebook 6.4.13-5ubuntu0.1 | Jan 16, 2026 |
| node-sanitize-html · Debian 12.15 (bookworm) | 2.7.1+~2.6.2-1 | DEBIAN-CVE-2022-25887 | Aug 30, 2022 |
| node-sanitize-html · Debian 13.5 (trixie) | 2.7.1+~2.6.2-1 | DEBIAN-CVE-2022-25887 | Aug 30, 2022 |
| node-sanitize-html · Debian 14 | 2.7.1+~2.6.2-1 | DEBIAN-CVE-2022-25887 | Aug 30, 2022 |
| python3-notebook · Ubuntu 22.04.1 LTS (jammy) | 6.4.8-1ubuntu0.1+esm1 | python3-notebook 6.4.8-1ubuntu0.1+esm1 | Aug 29, 2022 |
| python3-notebook · Ubuntu 24.04.5 LTS (noble) | 6.4.12-2.2ubuntu1+esm1 | python3-notebook 6.4.12-2.2ubuntu1+esm1 | Aug 29, 2022 |
| python3-notebook · Ubuntu 24.10 (oracular) | 6.4.13-2ubuntu0.1 | python3-notebook 6.4.13-2ubuntu0.1 | Jan 16, 2026 |
| python3-notebook · Ubuntu 25.04 (plucky) | 6.4.13-5ubuntu0.1 | python3-notebook 6.4.13-5ubuntu0.1 | Jan 16, 2026 |
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.