Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unratedamended

Server-Side Request Forgery in html-pdf-chrome

GHSA-5p98-wpc9-g498

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (html-pdf-chrome 0.6.1), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

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.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-5p98-wpc9-g498

  2. Revision 1 · created ·

    Published from osv record GHSA-5p98-wpc9-g498

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-5p98-wpc9-g498

Advisory: Server-Side Request Forgery in html-pdf-chrome
IDs: GHSA-5p98-wpc9-g498
Record: https://patchnext.com/advisories/ghsa-5p98-wpc9-g498 (revision 2, source checked 26 Oct 2026, 12:16 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: html-pdf-chrome 0.6.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm html-pdf-chrome: affected < 0.6.1; fixed in 0.6.1

## Suggested inspection (read-only)
- `npm ls html-pdf-chrome --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on html-pdf-chrome.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-5p98-wpc9-g498 (OSV record GHSA-5p98-wpc9-g498 lists affected ranges: npm html-pdf-chrome >=0 <0.6.1 (fixed))
- Verified: https://github.com/advisories/GHSA-5p98-wpc9-g498 (GitHub-reviewed advisory GHSA-5p98-wpc9-g498 lists affected ranges: npm html-pdf-chrome >=0 <0.6.1)

Commands are suggestions: review each one before running it.

Loading voting…