How severe is CVE-2022-0085?

CVE-2022-0085 has a CVSS score of 3.7/10, rated LOW. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2022-0085?

CVE-2022-0085 affects the following packages: dompdf/dompdf (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2022-0085?

Update dompdf/dompdf to 2.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-0085 is resolved across your whole dependency graph.

How do I detect CVE-2022-0085 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for dompdf/dompdf, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2022-0085 if there is no patch (or I can't update yet)?

Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

Is CVE-2022-0085 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2022-0085, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2022-0085?

CVE-2022-0085 has an EPSS (Exploit Prediction Scoring System) score of 1.0%, placing it in the 63th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2022-0085?

CVE-2022-0085 is classified as Server-Side Request Forgery (SSRF) (CWE-918). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2022-0085 published, and has it been updated?

CVE-2022-0085 was published on June 28, 2022 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘

🐘 Packagist

Not in CISA KEV

LOW severity

CVE-2022-0085 — dompdf

LOWFix: dompdf/dompdf@bb1ef65

CVE-2022-0085 is a low-severity (CVSS 3.7) Server-Side Request Forgery (SSRF) vulnerability in dompdf/dompdf. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for dompdf/dompdf — see the affected versions and patch details below.

Server-Side Request Forgery (SSRF) in dompdf/dompdf

Also known asGHSA-pf6p-25r2-fx45

Published

Jun 28, 2022

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Exploitation data as of Nov 2, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs63th percentile — riskier than 63% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

🐘dompdf/dompdf

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Server-Side Request Forgery (SSRF) in GitHub repository dompdf/dompdf prior to 2.0.0.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`dompdf/dompdf`	all versions	2.0.0`composer require dompdf/dompdf:^2.0.0`

Affected Products

1 product · 1 configurations

Application

dompdfdompdf_project

< 2.0.0

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Server-Side Request Forgery (SSRF) in GitHub repository dompdf/dompdf pr…

huntr.devNVDJul 2022

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for dompdf/dompdf, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update dompdf/dompdf to 2.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-0085 is resolved across your whole dependency graph.
Workarounds
Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

Frequently Asked Questions

Server-Side Request Forgery (SSRF) in GitHub repository dompdf/dompdf prior to 2.0.0.

O3 Security · Impact-Aware SCA

Is CVE-2022-0085 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

3.7/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

High

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

None

Availability

None

Raw vector

CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N

CWE Classification

CWE-918Server-Side Request Forgery (SSRF)

Weaponization

No Nuclei template or Metasploit module yet. 1 public proof-of-concept reference is listed on this page.

Timeline

Disclosed

Jun 28, 2022

First exploit

Jul 7, 2022

Last updated

Oct 28, 2026

Identifiers

CVE-2022-0085

GHSA-pf6p-25r2-fx45

References

Advisorygithub.com · CVE 2022 0085.json Advisorynvd.nist.gov · CVE 2022 0085 Fixgithub.com · bb1ef65011a14730b7cfbe73506b4bb8a03704bd Webhuntr.dev · 73dbcc78 5ba9 492f 9133 13bbc9f31236 Webgithub.com · CVE 2022 0085.yaml Packagegithub.com · dompdf

Related vulnerabilities

This CVE is low severity; 8 of 8 other CVEs affecting dompdf/dompdf are rated as high or higher (top: critical).

CVE-2026-55555CVE-2026-59941CVE-2026-56722CVE-2026-59942CVE-2026-59943CVE-2026-55554CVE-2021-3902CVE-2021-3838

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 28, 2026

CVE-2022-0085 — dompdf

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2022-0085 in your dependencies?