@netlify/ipx vulnerable to Full Response SSRF and Stored XSS via Cache Poisoning and Improper Host Validation

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

EPSS

• CVE-2022-39239: 0.46% estimated exploitation activity in the next 30 days; percentile 40.28 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact By sending specially crafted headers an attacker can bypass the source image domain allowlist, causing the handler to load and return arbitrary images. Because the response is cached globally, this image will then be served to visitors without requiring those headers to be set. XSS can be achieved by requesting a malicious SVG with embedded scripts, which would then be served from the site domain. Note that this does not apply to images loaded in <img tags, as scripts do not execute in this context. The image URL can be set in the header independently of the request URL, meaning any site images that have not previously been cached can have their cache poisoned. Patches This problem has been fixed in version 1.2.3 Workarounds The problem is no longer exploitable on Netlify as the CDN now sanitizes the relevant header. Cached content can be cleared by re-deploying the site.

Published by the source

21 Sep 2022, 21:42 UTC

Last modified by the source

8 Nov 2023, 04:10 UTC

Source last checked

26 Oct 2026, 12:16 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-9jjv-524m-jm98

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-9jjv-524m-jm98

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

# Patch Next advisory brief: CVE-2022-39239

Advisory: @netlify/ipx vulnerable to Full Response SSRF and Stored XSS via Cache Poisoning and Improper Host Validation
IDs: CVE-2022-39239, GHSA-9jjv-524m-jm98
Record: https://patchnext.com/advisories/cve-2022-39239 (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: Medium (CVSS 6.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @netlify/ipx 1.2.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @netlify/ipx: affected < 1.2.3; fixed in 1.2.3

## Suggested inspection (read-only)
- `npm ls @netlify/ipx --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 @netlify/ipx.
- 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-9jjv-524m-jm98 (OSV record GHSA-9jjv-524m-jm98 lists affected ranges: npm @netlify/ipx >=0 <1.2.3 (fixed))
- Verified: https://github.com/advisories/GHSA-9jjv-524m-jm98 (GitHub-reviewed advisory GHSA-9jjv-524m-jm98 lists affected ranges: npm @netlify/ipx >=0 <1.2.3)

Commands are suggestions: review each one before running it.