Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-2fmj-p74r-3wjm

PhpWeasyPrint vulnerable to PHAR deserialization via output filename (CVE-2023-28115 case-insensitive bypass)

CVSS 8.1 HighEPSS 0.0073 · 54th percentile

Published by the GitHub Advisory Database at 26 Jun 2026, 22:10 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
pontedilana/php-weasyprintPackagist<2.6.02.6.0
Identifiers
GHSA-2fmj-p74r-3wjm · CVE-2026-49286 · PKSA-xz12-xgjc-r2wn
Weakness (CWE)
CWE-502
Tags
Published
26 Jun 2026
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

PhpWeasyPrint (Packagist package pontedilana/php-weasyprint) versions before 2.6.0 use a case-sensitive check to block the phar:// stream wrapper in the output filename, which PHP's case-insensitive wrappers can bypass. An attacker who can control the output filename passed to generate() or generateFromHtml(), and who can place a PHAR archive on the filesystem (for example through an upload), can trigger PHAR metadata deserialization and remote code execution on servers running PHP below 8. Upgrade to version 2.6.0, which fixes the issue.

Written 31 Oct 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.1 High 3.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0073, the 54th percentile, on 10 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 13:58 UTC First seen by agentprime
  2. 31 Oct 2026, 13:58 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.