How severe is GHSA-5p98-wpc9-g498?

No CVSS score has been assigned to GHSA-5p98-wpc9-g498 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-5p98-wpc9-g498?

GHSA-5p98-wpc9-g498 affects the following packages: html-pdf-chrome (npm). Ecosystems affected: npm.

How do I fix GHSA-5p98-wpc9-g498?

Update html-pdf-chrome to 0.6.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5p98-wpc9-g498 is resolved across your whole dependency graph.

How do I detect GHSA-5p98-wpc9-g498 in my npm dependencies?

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

How do I mitigate GHSA-5p98-wpc9-g498 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 GHSA-5p98-wpc9-g498 actively exploited in the wild?

No public exploit code has been indexed for GHSA-5p98-wpc9-g498 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-5p98-wpc9-g498 published, and has it been updated?

GHSA-5p98-wpc9-g498 was published on September 4, 2020 and was last updated on June 22, 2022. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

Server-Side Request Forgery in html-pdf-chromeGHSA-5p98-wpc9-g498

GHSA-5p98-wpc9-g498 is a security vulnerability in html-pdf-chrome. A fix is available for html-pdf-chrome — see the affected versions and patch details below.

Published

Sep 4, 2020

Updated

Jun 22, 2022

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Jun 22, 2022 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

16other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

html-pdf-chromenpm

2Kdownloads / week

Description

Recommendation

This package is working as intended. A Security section has been added since v0.6.1 to detail proper usage of this library. Npm has revoked their advisory altogether.

Original Advisory

All versions of html-pdf-chrome are vulnerable to Server-Side Request Forgery (SSRF). The package executes HTTP requests if the parsed HTML contains external references to resources, such as <iframe src="http://localhost" height="800px" width="800px"></iframe>. This allows attackers to access resources through HTTP that are accessible to the server, including private resources in the hosting environment.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`html-pdf-chrome`	all versions	0.6.1`npm install html-pdf-chrome@0.6.1`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for html-pdf-chrome, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update html-pdf-chrome to 0.6.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5p98-wpc9-g498 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

## Recommendation This package is working as intended. A [Security](https://github.com/westy92/html-pdf-chrome#security) section has been added since v0.6.1 to detail proper usage of this library. Npm has revoked their advisory altogether. ## Original Advisory All versions of `html-pdf-chrome` are vulnerable to Server-Side Request Forgery (SSRF). The package executes HTTP requests if the parsed HTML contains external references to resources, such as `<iframe src="http://localhost" height="800px" width="800px"></iframe>`. This allows attackers to access resources through HTTP that are accessib

O3 Security · Impact-Aware SCA

Is GHSA-5p98-wpc9-g498 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works