# CVE-2026-126779: Spatie Browsershot 2.2.0 before 5.5.0 Local File Read via setHtml()

> Attackers supplying HTML to Browsershot's setHtml can read local server files rendered into PDF or screenshot.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Harmful if only installed:** No
- **Needs a specific call:** Yes (`setHtml()`)
- **Fix available:** No
- **Published:** 11 Nov 2026
- **Updated:** 11 Nov 2026
- **Also known as:** GHSA-wp7g-f22j-79fp

## What is CVE-2026-126779?

CVE-2026-126779 is a high-severity path traversal vulnerability in spatie browsershot, published on 11 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Spatie Browsershot 2.2.0 before 5.5.0 contains a local file read vulnerability that allows attackers to read server files by supplying root-relative references in HTML passed to setHtml(). Attackers can embed iframe, img, link or script elements referencing paths like /etc/passwd, which resolve to file:// URLs and render file contents into the returned PDF or screenshot.

Weakness: CWE-73 (External Control of File Name or Path)

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

An affected version is only exploitable if your software calls setHtml(). Many projects that include it are not exposed.


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

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

## Is CVE-2026-126779 being exploited?

There is no known exploitation of CVE-2026-126779 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-126779 is a high-severity path traversal vulnerability in spatie browsershot, published on 11 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-126779 in the wild and no public exploit code.
Exposure: An affected version is only exploitable if your software calls setHtml(). Many projects that include it are not exposed.

Affected product: spatie browsershot. 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.
   If an affected version is present, also search the code for calls to setHtml() and report whether any exist.
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-126779/ (Markdown: https://insights.sbomify.com/CVE-2026-126779/index.md)
```

## Sources

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

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