Skip to main content
Menu
CVEs

CVE

Spatie Browsershot 2.2.0 before 5.5.0 Local File Read via setHtml()

Browsershot 2.2.0 before 5.5.0 is affected when attacker-supplied HTML with root-relative references is passed to setHtml(). The fix is in 5.5.0.

CVE-2026-126779

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

8.7HighCNA
Exploited
No known exploitation
Fix
Fixed in 5.5.0
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 5.5.0.

Published
Last modified
Reference
Last checked
26/100 · provisional
Unclear
None on Exploit-DB, Metasploit or GitHub

Summary

Spatie Browsershot, a library for generating PDFs and screenshots from HTML, has a local file read flaw in its setHtml() method. A remote attacker without logging in can embed root-relative references such as /etc/passwd in supplied HTML, causing the server's file contents to appear in the returned PDF or screenshot.

Read the original 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.

Who should check

Teams running spatie/browsershot from 2.2.0 before 5.5.0 that render HTML through setHtml() or html()

Read the source excerpt

“Affecting browsershot >= 2.2.0, < 5.5.0”

vulncheck.com

cve.now Index

26Pcve.now Index 26 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity8.7/10CVSS 8.7
  • No patch0/5No signal

What would change the score

  • Would score about 71 if added to CISA KEV
  • Would score about 66 if CISA's SSVC rates exploitation active
  • Would score about 31 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 5.5.0.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-126779 (Spatie Browsershot 2.2.0 before 5.5.0 Local File Read via setHtml()), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-126779 (entry last updated 2026-11-11):
Affected:
- spatie browsershot: from 2.2.0, fixed in 5.5.0
Fixed versions: 5.5.0.
Conditions (all must be true for the bug to be hit):
- Browsershot version 2.2.0 up to but not including 5.5.0 (source: https://www.vulncheck.com/advisories/spatie-browsershot-2.2.0-before-5.5.0-local-file-read-via-sethtml)
- Attacker-supplied HTML with root-relative references is passed to setHtml() (source: https://www.vulncheck.com/advisories/spatie-browsershot-2.2.0-before-5.5.0-local-file-read-via-sethtml)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-126779 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126779 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/spatie/browsershot/pull/989
- https://github.com/spatie/browsershot/commit/eba71ab7f4aba23d9321d653ccd19d4e94432516
- https://github.com/spatie/browsershot/releases/tag/5.5.0
- https://github.com/spatie/browsershot/blob/2.2.0/src/Browsershot.php#L242-L248
- https://www.vulncheck.com/advisories/spatie-browsershot-2.2.0-before-5.5.0-local-file-read-via-sethtml
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-126779
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-126779"}.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • spatie browsershot

    From 2.2.0 · fixed in 5.5.0

Evidence 7

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 5

  1. Patch
  2. Patch
  3. Repository
  4. Repository
  5. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-126779

Is CVE-2026-126779 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

When HTML containing root-relative references is passed to setHtml(), Browsershot can read server files such as /etc/passwd. Their contents are then rendered into the returned PDF or screenshot.Source: vulncheck.com

Which versions are affected by CVE-2026-126779?

browsershot: from 2.2.0 before 5.5.0.Source: cve.now feed data

Am I affected, and how do I check?

Browsershot versions from 2.2.0 up to but not including 5.5.0 are affected. The affected setup is code that passes HTML with root-relative references to setHtml(); check the installed Browsershot version in composer.lock and whether setHtml() is called.Source: vulncheck.com

How do I fix CVE-2026-126779?

Upgrade Browsershot to 5.5.0 or later, which is the fixed version listed for this issue. No workaround is listed in the facts.Source: vulncheck.com