# CVE-2026-49359: PhpWeasyPrint vulnerable to SSRF and local file disclosure via the attachment option

> Attackers can exploit the attachment option to perform Server-Side Request Forgery and read local files via PHP stream wrappers.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Jun 2026
- **Updated:** 23 Jun 2026
- **Also known as:** GHSA-x8g9-h984-pc36

## What is CVE-2026-49359?

CVE-2026-49359 is a medium-severity server-side request forgery vulnerability in pontedilana php-weasyprint, published on 19 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

PhpWeasyPrint is a PHP library allowing PDF generation from a URL or an HTML page. Prior to version 2.6.0, `pontedilana/php-weasyprint` fetches the content of option values server-side via `file_get_contents()` when the value looks like a URL, without restricting the URL scheme. The `attachment` option of `Pdf` is the reachable sink: any value that passes `isOptionUrl()` (`filter_var(..., FILTER_VALIDATE_URL)`) is downloaded by the PHP process and embedded into the generated PDF. Because `FILTER_VALIDATE_URL` accepts `http`, `https`, `ftp`, `file` and PHP stream wrappers such as `php://`, an attacker who can influence the `attachment` value reaches both a **Server-Side Request Forgery** primitive (e.g. internal HTTP endpoints, cloud metadata) and a local file disclosure primitive (`file://`, `php://filter/...`), with the fetched bytes exfiltrated as a PDF attachment. This is the same class of issue KnpLabs/snappy patched for its `xsl-style-sheet` option in GHSA-c5fp-p67m-gq56. The library is documented as a one-to-one substitute for KnpLabs/snappy and shares the same code shape. PhpWeasyPrint version 2.6.0 contains a patch for the issue.

Weakness: CWE-918 (Server-Side Request Forgery)

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

2 open source packages ship an affected version, including pontedilana/php-weasyprint.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pontedilana/php-weasyprint` | Packagist | All versions | 2.6.0 |
| `pontedilana/php-weasyprint` | Packagist | All versions | 2.6.0 |

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

Upgrade pontedilana/php-weasyprint to 2.6.0 or later.

## Is CVE-2026-49359 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-49359 is a medium-severity server-side request forgery vulnerability in pontedilana php-weasyprint, published on 19 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-49359 exists.

Affected packages and fixed versions:
- pontedilana/php-weasyprint (Packagist): affected all versions; fixed in 2.6.0
- pontedilana/php-weasyprint (Packagist): affected all versions; fixed in 2.6.0

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-49359/ (Markdown: https://insights.sbomify.com/CVE-2026-49359/index.md)
```

## Sources

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

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