VulertSecurity VulertSecurity

Vulnerability Database · Packagist · Package report

dompdf/dompdf: vulnerability history, versions and safety

dompdf/dompdf is a package in the Packagist ecosystem. Vulert records 20 vulnerabilities for it across 40 releases, from Apr 2022 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
20 vulnerabilities recorded C5 H3 M10 L2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
6 in the last 12 months

Most recent disclosure 22 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all dompdf/dompdf vulnerabilities

Vulert verdict on dompdf/dompdf i

Updated on 22 Oct 2026

Every vulnerability Vulert records for this package has a fix, and the newest was recorded 22 Jul 2026. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 20 vulnerabilities on record across 4 years, 6 in the last year.

What to do: Move the affected dependencies to the fixed versions listed below, then keep the package monitored so the next vulnerability reaches you. Fix it, then keep watch: Vulert alerts you when a new vulnerability affects the version you run. Monitor it with Vulert →

  • Vulnerabilities on record 20 over 4 years · 6 in the last year i
  • Latest disclosure 22 Jul 2026 i
  • Highest CVSS 10.0 i
  • With no published fix 0 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for dompdf/dompdf, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
2.0.2 C1 Yes Details →
v3.1.5 M4 L2 Yes Details →
v3.1.4 M4 L2 Yes Details →
v3.1.3 M4 L2 Yes Details →
v3.1.2 M4 L2 Yes Details →
v3.1.1 M4 L2 Yes Details →
v3.1.0 M4 L2 Yes Details →
v3.0.2 M4 L2 Yes Details →
v3.0.1 M4 L2 Yes Details →
v3.0.0 M4 L2 Yes Details →
v2.0.8 M4 L2 Yes Details →
v2.0.7 M4 L2 Yes Details →
v2.0.5 M4 L2 Yes Details →
v2.0.4 M4 L2 Yes Details →
v2.0.3 M5 L2 Yes Details →
v2.0.2 C1 M5 L2 Yes Details →
v2.0.1 C1 M5 L2 Yes Details →
v2.0.0 C1 H1 M5 L2 Yes Details →
v1.2.2 C3 H1 M7 L2 Yes Details →
v1.2.1 C3 H1 M7 L2 Yes Details →
v1.2.0 C4 H1 M7 L2 Yes Details →
v1.1.1 C4 H1 M7 L2 Yes Details →
v1.1.0 C4 H1 M7 L2 Yes Details →
v1.0.2 C4 H1 M7 L2 Yes Details →
v1.0.1 C4 H1 M7 L2 Yes Details →
v1.0.0 C4 H1 M7 L2 Yes Details →
v0.8.6 C4 H1 M7 L2 Yes Details →
v0.8.5 C4 H1 M7 L2 Yes Details →
v0.8.4 C4 H1 M7 L2 Yes Details →
v0.8.3 C4 H1 M7 L2 Yes Details →
v0.8.2 C4 H1 M7 L2 Yes Details →
v0.8.1 C4 H1 M7 L2 Yes Details →
v0.8.0 C4 H1 M7 L2 Yes Details →
v0.7.0 C4 H1 M7 L2 Yes Details →
v0.7.0-beta3 C4 H1 M7 L2 Yes Details →
v0.7.0-beta2 C4 H1 M7 L2 Yes Details →
v0.7.0-beta C4 H1 M7 L2 Yes Details →
v0.6.2 C4 H1 M7 L2 Yes Details →
v0.6.1 C4 H2 M9 L2 Yes Details →
v0.6.0 C4 H3 M10 L2 Yes Details →

Newest 40 of 40 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 9
  • 2023 3
  • 2024 2
  • 2026 6

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 6 of the 20 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for dompdf/dompdf

The 5 most severe of 20 vulnerabilities recorded for this package

Search all 20 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2023-23924: Dompdf vulnerable to URI validation failure on SVG parsing 10.0 critical 2.0.2 01 Feb 2023
CVE-2023-24813: Dompdf SVG Parsing URI Validation Failure 10.0 critical 2.0.3 07 Feb 2023
CVE-2022-28368: Remote code injection in dompdf/dompdf 9.8 critical 1.2.1 04 Apr 2022
CVE-2021-3838: dompdf/dompdf Critical PHAR Deserialization Vulnerability 9.8 critical 2.0.0 15 Nov 2024
CVE-2021-3902: dompdf/dompdf SVG Parser XXE Vulnerability Leading to SSRF and Deserialization Attacks 9.8 critical 2.0.0 15 Nov 2024

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524173

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About dompdf/dompdf

Is dompdf/dompdf safe to use?

Vulert records 20 vulnerabilities for dompdf/dompdf in Packagist: 5 critical, 3 high, 10 medium and 2 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

How many vulnerabilities does dompdf/dompdf have?

20 vulnerabilities are recorded for dompdf/dompdf in the Packagist ecosystem: 5 critical, 3 high, 10 medium and 2 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new dompdf/dompdf vulnerabilities disclosed?

6 vulnerabilities were recorded for dompdf/dompdf in the last 12 months, and the oldest entry in this database dates to 04 Apr 2022. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of dompdf/dompdf are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor dompdf/dompdf for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the dompdf/dompdf version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.