Is this vulnerability remotely exploitable?

Yes. If the esm.sh service is publicly accessible, an attacker can exploit the SSRF remotely by sending crafted HTTP requests to the exposed endpoints.

Does exploitation require authentication or special privileges?

In typical CDN usage, no special privileges are required beyond the ability to make HTTP requests to the service. If the deployment restricts access via authentication or IP allowlists, those controls would limit who can attempt exploitation but not the underlying flaw.

What is the safest general fix pattern?

The most robust fix is to enforce strict outbound request policies: restrict requests to a curated allowlist of safe domains, block all internal IP ranges and sensitive hostnames, and validate/normalize URLs before use. Coupling this with network-level egress restrictions significantly reduces the attack surface.

Severity:

HIGH RISK

(7.5)

Server-Side Request Forgery (CWE-918) in esm.sh CDN Response Handling

CVE-2025-50180

Published:

Feb 25, 2026

Status:

Analyzed

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

NDV

Recent Vulnerabilities

CWE-78

CRITICAL RISK

CRITICAL

(9.9)

Command Injection in MCP Stdio Configuration Validation (CWE-78) in WeKnora

Remote Code Execution

March 7, 2026

CWE-89

CRITICAL RISK

CRITICAL

(9.9)

SQL Injection via PostgreSQL Array/Row Expressions (CWE-89) in WeKnora Query Engine

Remote Code Execution via SQL Injection on the Database Server

March 7, 2026

Vulnerability Type

Category:

Server-Side Request Forgery (SSRF)

CWE:

CWE-918

Impact:

Information Disclosure via Full-Response SSRF

Severity:

HIGH RISK

(7.5)

CVSS Version:

3.1

Vulnerability Type

Category:

Server-Side Request Forgery (SSRF)

CWE:

CWE-918

Impact:

Information Disclosure via Full-Response SSRF

Severity:

HIGH RISK

(7.5)

CVSS Version:

3.1

Catch This CVE While Code Is Being Written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Get Started

Ship clean & secure code faster

START 14 DAYS FREE TRIAL

BOOK A DEMO

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Server-Side Request Forgery (CWE-918) in esm.sh CDN Response Handling

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

Recent Vulnerabilities

CRITICAL RISK

CRITICAL

(9.9)

Command Injection in MCP Stdio Configuration Validation (CWE-78) in WeKnora

CRITICAL RISK

CRITICAL

(9.9)

SQL Injection via PostgreSQL Array/Row Expressions (CWE-89) in WeKnora Query Engine

Vulnerability Type

Vulnerability Type

Vulnerability Type

Catch This CVE While Code Is Being Written

Ship clean & secure code faster

Product

Pricing

Company

Legal

Developers

Compare

Product

Pricing

Company

Legal

Developers

Compare

Product

Pricing

Company

Legal

Developers

Compare