GHSA-HP3V-MFQW-H74C

@astrojs/netlify generates an overly-broad Netlify Image CDN allowlist because remotePatterns.pathname metacharacters are not escaped

regexStr += hostname.replace(/\./g, '\\.');

regexStr += `(\\${pathname})`;

// astro.config.mjs
image: {
  remotePatterns: [{
    protocol: 'https',
    hostname: 'cdn.example.com',
    pathname: '/img/v1.0/file',
  }],
}

https://cdn\.example\.com(:[0-9]+)?(\/img/v1.0/file)([?][^#]*)?$

Netlify's Image CDN accepts optimization requests for URLs on the allowed host that the developer's remotePatterns entry was intended to exclude. The hostname remains correctly anchored, so the broadening is confined to the pathname dimension on an already-allowed host. Realistic impact depends on whether other images the developer meant to keep out of their CDN exist at metacharacter-adjacent paths on that host. This affects reasonable, non-permissive configurations, since any pathname containing a . (file extensions, version segments) is affected.

GHSA-HP3V-MFQW-H74C has a CVSS score of 3.7 (Low). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (8.1.2); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

A fix will escape all regex metacharacters in the literal portions of each remotePatterns component before interpolation, applying only Astro's documented wildcard semantics explicitly. A regression corpus validates the generated Netlify regexes against @astrojs/internal-helpers' matchPattern().

1. What is GHSA-HP3V-MFQW-H74C? GHSA-HP3V-MFQW-H74C is a low-severity security vulnerability in @astrojs/netlify (npm), affecting versions < 8.1.2. It is fixed in 8.1.2.
2. How severe is GHSA-HP3V-MFQW-H74C? GHSA-HP3V-MFQW-H74C has a CVSS score of 3.7 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of @astrojs/netlify are affected by GHSA-HP3V-MFQW-H74C? @astrojs/netlify (npm) versions < 8.1.2 is affected.
4. Is there a fix for GHSA-HP3V-MFQW-H74C? Yes. GHSA-HP3V-MFQW-H74C is fixed in 8.1.2. Upgrade to this version or later.
5. Is GHSA-HP3V-MFQW-H74C exploitable, and should I be worried? Whether GHSA-HP3V-MFQW-H74C is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether GHSA-HP3V-MFQW-H74C is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix GHSA-HP3V-MFQW-H74C? Upgrade @astrojs/netlify to 8.1.2 or later.

Other vulnerabilities in @astrojs/netlify