Skip to content

CWE-835: Loop with Unreachable Exit Condition ('Infinite Loop')

Base

The product contains an iteration or loop with an exit condition that cannot be reached, i.e., an infinite loop.

Consequences

  • Availability: DoS: Resource Consumption (CPU), DoS: Resource Consumption (Memory), DoS: Amplification

Recent advisories

  • GHSA-5849-834g-hvw5 — pypdf has possible infinite loop when hitting EOF in standard xref table during trailer search
  • GHSA-mfr5-77xh-9j7h — pypdf has possible infinite loop when cloning dictionaries
  • GHSA-h6cr-wjv9-3cpp — Forge: Denial of Service via infinite loop in BigInteger.modInverse() with negative input (incomplete fix of CVE-2026-33891)
  • GHSA-fw5c-8223-6h42 — russh: peer-declared zero maximum packet size permanently stalls channel writes (silent AsyncWrite hang)
  • EEF-CVE-2026-115269 — HTTP/2 WINDOW_UPDATE and SETTINGS frames reset the request body read timeout in Bandit
  • GHSA-3j72-p6qg-6xp7 — Pillow: TarIO negative size field causes infinite CPU-spin loop
  • GHSA-39mj-jf6j-2qj3 — pypdf: Possible infinite loop when hitting EOF in standard xref table
  • GHSA-9mx8-4j7g-633p — pypdf: Possible infinite loop when removing tree items
  • GHSA-qfv9-64jg-mh7p — pypdf: Possible infinite loop in PdfWriter.find_outline_item
  • GHSA-f2g6-542v-9j58 — Pillow: Infinite loop in PdfParser.rewrite_pages on page tree Parent cycle
  • GHSA-254f-3936-288h — Pillow: PdfParser can recurse without limit in get_value() and linearize_page_tree()
  • GHSA-22hg-r758-rrw9 — Pillow: Infinite loop in MIC n_frames when the embedded TIFF
  • EEF-CVE-2026-96596 — erl_tar:extract/2 loops forever on a GNU sparse member with a trailing hole
  • GHSA-gh4c-6fx4-qh6g — urllib3: Chunked Deflate streaming can enter an infinite loop
  • GHSA-jqhh-cjmq-vmv6 — Open WebUI: Any authenticated user can hang the server via a cyclic chat message history

All advisories for CWE-835

Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor