# CVE-2026-8318: VectifyAI PageIndex PDF Table of Contents page_index.py toc_transformer infinite loop

> Remote attackers can cause a denial of service via an infinite loop in the PDF table of contents handler of the PageIndex library.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 May 2026
- **Updated:** 11 May 2026
- **Also known as:** GHSA-fp52-pxf6-37vh

## What is CVE-2026-8318?

CVE-2026-8318 is a medium-severity denial of service vulnerability in VectifyAI PageIndex, published on 11 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A security flaw has been discovered in VectifyAI PageIndex up to f50e52975313c6716c02b20a119577a1929decba. Affected by this vulnerability is the function toc_transformer of the file pageindex/page_index.py of the component PDF Table of Contents Handler. The manipulation results in infinite loop. The attack may be launched remotely. The exploit has been released to the public and may be used for attacks. This product operates on a rolling release basis, ensuring continuous delivery. Consequently, there are no version details for either affected or updated releases.

Weakness: CWE-835 (Loop with Unreachable Exit Condition), CWE-404 (Improper Resource Shutdown or Release)

## Which versions are affected by CVE-2026-8318?


## How do I fix CVE-2026-8318?

No fix has been published for CVE-2026-8318 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-8318 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-8318 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-8318 and fix it if it is affected.

What it is: CVE-2026-8318 is a medium-severity denial of service vulnerability in VectifyAI PageIndex, published on 11 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-8318 exists.

Affected product: VectifyAI PageIndex. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-8318/ (Markdown: https://insights.sbomify.com/CVE-2026-8318/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-8318
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-8318
- OSV: https://osv.dev/vulnerability/CVE-2026-8318

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-8318/
Summaries are generated and may contain mistakes; the official description above is the record.