How severe is CVE-2024-43800?

CVE-2024-43800 has a CVSS score of 5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2024-43800?

CVE-2024-43800 affects the following packages: serve-static (npm), serve-static (npm). Ecosystems affected: npm.

How do I fix CVE-2024-43800?

Update serve-static to 1.16.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-43800 is resolved across your whole dependency graph.

How do I detect CVE-2024-43800 in my npm dependencies?

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

How do I mitigate CVE-2024-43800 if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is CVE-2024-43800 actively exploited in the wild?

No public exploit code has been indexed for CVE-2024-43800 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 CVE-2024-43800?

CVE-2024-43800 has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 50th 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 CVE-2024-43800?

CVE-2024-43800 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type 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 CVE-2024-43800 published, and has it been updated?

CVE-2024-43800 was published on September 10, 2024 and was last updated on October 28, 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

MEDIUM severity

CVE-2024-43800 — serve-static

MEDIUMFix: expressjs/serve-static@0c11fad

CVE-2024-43800 is a medium-severity (CVSS 5) Cross-site Scripting (XSS) vulnerability in serve-static. A fix is available for serve-static — see the affected versions and patch details below.

serve-static affected by template injection that can lead to XSS

Also known asGHSA-cm22-4g7w-348p

Published

Sep 10, 2024

Updated

Oct 28, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2024-43800.

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs50th percentile — riskier than 50% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs 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.

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

serve-staticnpm

202.2Mdownloads / week

Description

Impact

passing untrusted user input - even after sanitizing it - to redirect() may execute untrusted code

Patches

this issue is patched in serve-static 1.16.0

Workarounds

users are encouraged to upgrade to the patched version of express, but otherwise can workaround this issue by making sure any untrusted inputs are safe, ideally by validating them against an explicit allowlist

Details

successful exploitation of this vector requires the following:

The attacker MUST control the input to response.redirect()
express MUST NOT redirect before the template appears
the browser MUST NOT complete redirection before:
the user MUST click on the link in the template

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`serve-static`	all versions	1.16.0`npm install serve-static@1.16.0`
📦npm	`serve-static`	≥ 2.0.0&&< 2.1.0	2.1.0`npm install serve-static@2.1.0`

Affected Products

1 product · 2 configurations

Application

serve-staticopenjsf

≥ 2.0.0 && < 2.1.0

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for serve-static, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update serve-static to 1.16.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-43800 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

rhdh-hub-container 1.2 and 1.3 have included patches for this vulnerability.

Workaround published by Red Hat

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

Source: Red Hat security advisory for CVE-2024-43800 (CC BY 4.0)

Product	Fixed in	Advisory
Discovery 1 for RHEL 9	`discovery/discovery-server-rhel9:1.12.0-1`	RHSA-2025:1249
HawtIO 4.0.0 for Red Hat build of Apache Camel 4	`serve-static`	RHSA-2024:11023
NETWORK-OBSERVABILITY-1.7.0-RHEL-9	`network-observability/network-observability-cli-rhel9:v1.7.0-67`	RHSA-2024:8014
Red Hat Developer Hub 1.3 on RHEL 9	`rhdh/rhdh-hub-rhel9:1.3-100`	RHBA-2024:7523
Red Hat Migration Toolkit for Containers 1.8	`rhmtc/openshift-migration-ui-rhel8:v1.8.5-7`	RHSA-2024:10906
Red Hat OpenShift Container Platform 4.17	`openshift4/nmstate-console-plugin-rhel9:v4.17.0-202501301204.p0.gcffdc60.assembly.stream.el9`	RHSA-2025:0875
Red Hat OpenShift GitOps 1.12	`openshift-gitops-1/argocd-rhel8:v1.12.6-2`	RHSA-2024:8677
Red Hat OpenShift GitOps 1.13	`openshift-gitops-1/argocd-rhel8:v1.13.2-4`	RHSA-2024:8581

Frequently Asked Questions

### Impact passing untrusted user input - even after sanitizing it - to `redirect()` may execute untrusted code ### Patches this issue is patched in serve-static 1.16.0 ### Workarounds users are encouraged to upgrade to the patched version of express, but otherwise can workaround this issue by making sure any untrusted inputs are safe, ideally by validating them against an explicit allowlist ### Details successful exploitation of this vector requires the following: 1. The attacker MUST control the input to response.redirect() 1. express MUST NOT redirect before the template appears 1.