How severe is GHSA-4233-jc72-56c5?

No CVSS score has been assigned to GHSA-4233-jc72-56c5 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-4233-jc72-56c5?

GHSA-4233-jc72-56c5 affects the following packages: @astrojs/netlify (npm). Ecosystems affected: npm.

How do I fix GHSA-4233-jc72-56c5?

Update @astrojs/netlify to 8.2.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4233-jc72-56c5 is resolved across your whole dependency graph.

How do I detect GHSA-4233-jc72-56c5 in my npm dependencies?

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

How do I mitigate GHSA-4233-jc72-56c5 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-4233-jc72-56c5 actively exploited in the wild?

No public exploit code has been indexed for GHSA-4233-jc72-56c5 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.

What is the EPSS score for GHSA-4233-jc72-56c5?

GHSA-4233-jc72-56c5 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 23th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-4233-jc72-56c5?

GHSA-4233-jc72-56c5 is classified as CWE-625 (CWE-625), Server-Side Request Forgery (SSRF) (CWE-918). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-4233-jc72-56c5 published, and has it been updated?

GHSA-4233-jc72-56c5 was published on September 30, 2026 and was last updated on September 30, 2026. 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

Astro: Netlify Image CDN allowlist bypass enables SSRFGHSA-4233-jc72-56c5

Fix: withastro/astro#17752

GHSA-4233-jc72-56c5 is a CWE-625 vulnerability in @astrojs/netlify. A fix is available for @astrojs/netlify — see the affected versions and patch details below.

Also known asCVE-2026-102983

Published

Sep 30, 2026

Updated

Sep 30, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 22, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk-0.23%

Lower risk than most CVEs23th percentile — riskier than 23% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from 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.

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

@astrojs/netlifynpm

35Kdownloads / week

Description

Summary

The @astrojs/netlify adapter generated regular expressions for Netlify Image CDN remote-image allowlists without anchoring them to the beginning of the URL. Netlify evaluates these expressions with RegExp.test(), so an allowed image origin appearing anywhere in a URL, including its path or query string, could satisfy the allowlist.

For example, an application allowing images.example.com could accept a source URL such as:

http://127.0.0.1:6379/?url=https://images.example.com/image.png

The allowlist matched the approved origin in the query string, but Netlify parsed and fetched the URL whose actual host was 127.0.0.1.

Impact

An unauthenticated attacker can bypass the configured image.domains or image.remotePatterns allowlist through the public /.netlify/images endpoint and cause Netlify Image CDN to make requests to attacker-selected URLs. This may allow probing or reaching internal services, depending on Netlify's network-level egress protections.

The Image CDN attempts to transform responses as images, which limits direct response exfiltration. No confidentiality or integrity impact has been demonstrated.

Affected versions

@astrojs/netlify versions from 5.2.0 through 8.2.3.

Patches

Fixed in @astrojs/netlify 8.2.4. Generated remote-image allowlist expressions are now anchored to both the beginning and end of the source URL.

Workarounds

Upgrade to @astrojs/netlify 8.2.4 or later. Before upgrading, disable Netlify Image CDN by setting imageCDN: false in the adapter configuration, or remove remote image allowlist entries.

Credits

Reported by @pacocartones.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@astrojs/netlify`	≥ 5.2.0&&< 8.2.4	8.2.4`npm install @astrojs/netlify@8.2.4`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @astrojs/netlify, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @astrojs/netlify to 8.2.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4233-jc72-56c5 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

## Summary The `@astrojs/netlify` adapter generated regular expressions for Netlify Image CDN remote-image allowlists without anchoring them to the beginning of the URL. Netlify evaluates these expressions with `RegExp.test()`, so an allowed image origin appearing anywhere in a URL, including its path or query string, could satisfy the allowlist. For example, an application allowing `images.example.com` could accept a source URL such as: ```text http://127.0.0.1:6379/?url=https://images.example.com/image.png ``` The allowlist matched the approved origin in the query string, but Netlify par

O3 Security · Impact-Aware SCA

Is GHSA-4233-jc72-56c5 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works