Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.7amended

Nuxt Icon affected by a Server-Side Request Forgery (SSRF)

CVE-2024-42352GHSA-cxgv-px37-4mp2

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (@nuxt/icon 1.4.5), 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 4.0
7.7 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N · score source
EPSS
  • CVE-2024-42352: 0.65% estimated exploitation activity in the next 30 days; percentile 51.11 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary nuxt/icon provides an API to allow client side icon lookup. This endpoint is at /api/nuxticon/[name]. The proxied request path is improperly parsed, allowing an attacker to change the scheme and host of the request. This leads to SSRF, and could potentially lead to sensitive data exposure. Details The new URL constructor is used to parse the final path. This constructor can be passed a relative scheme or path in order to change the host the request is sent to. This constructor is also very tolerant of poorly formatted URLs. As a result we can pass a path prefixed with the string http:. This has the effect of changing the scheme to HTTP. We can then subsequently pass a new host, for example http:127.0.0.1:8080. This would allow us to send requests to a local server. PoC Make a request to /api/nuxticon/http:example.com, observe the data returned has been fetched from a different resource than intended. I typically try to find an example within Nuxt infrastructure that is…

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

    Amended from ghsa record GHSA-cxgv-px37-4mp2

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-cxgv-px37-4mp2

Agent brief

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

# Patch Next advisory brief: CVE-2024-42352

Advisory: Nuxt Icon affected by a Server-Side Request Forgery (SSRF)
IDs: CVE-2024-42352, GHSA-cxgv-px37-4mp2
Record: https://patchnext.com/advisories/cve-2024-42352 (revision 3, source checked 26 Oct 2026, 12:31 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @nuxt/icon 1.4.5. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @nuxt/icon: affected <= 1.4.4; fixed in 1.4.5

## Suggested inspection (read-only)
- `npm ls @nuxt/icon --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 @nuxt/icon.
- 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-cxgv-px37-4mp2 (OSV record GHSA-cxgv-px37-4mp2 lists affected ranges: npm @nuxt/icon >=0 <1.4.5 (fixed))
- Verified: https://github.com/advisories/GHSA-cxgv-px37-4mp2 (GitHub-reviewed advisory GHSA-cxgv-px37-4mp2 lists affected ranges: npm @nuxt/icon >=0 <=1.4.4)

Commands are suggestions: review each one before running it.

Loading voting…