Skip to main content
VulnerabilityPublished

CVE-2026-132277: Inscriptis · Quadratic memory growth from sibling <table> elements in get_text()

Affects inscriptisSource GCVE Database

0
Compare
Authoritative record:CVE-2026-132277· Medium 5.3

Not known to be exploited · CVSS 5.3 Medium : upgrade to 2.7.6 when convenient.

Data as of 21 Nov 2026, 00:32 UTC

CVSS 3.1 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.15.3
Patch
Available – fixed in 2.7.6
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.

What to do

Upgrade inscriptis to 2.7.6.

Affected software

ProductAffectedFixed in
PyPIinscriptisAffected
  • >=2.0.0 <2.7.6
Fixed in
  • 2.7.6

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available in inscriptis version 2.7.6 that fixes the quadratic memory growth issue by properly removing extra padding entries during table rendering. Users should upgrade to version 2.7.6 or later to mitigate this vulnerability. Until upgraded, avoid processing untrusted HTML with many sibling <table> elements or apply input validation to limit such constructs.

Description

Inscriptis versions from 2.0.0 up to but not including 2.7.6 have a vulnerability causing quadratic memory growth when processing multiple sibling <table> elements in the get_text() function. This leads to excessive memory consumption and large output sizes, potentially exhausting system memory with crafted HTML input. The issue arises from improper handling of indentation prefixes in block-level parent elements. A patch is available in version 2.7.6 that fixes this by correctly removing extra padding entries, significantly reducing memory usage and output size.

References

Community reviews

Loading reviews…