# CVE-2025-11149: @nubosoftware/node-static failure to catch exception can result in server crash

> Attackers can crash the server by sending requests with null bytes, causing a denial of service in the node-static library.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/E:P/RL:O/RC:R`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Sep 2025
- **Updated:** 30 Sep 2025
- **Also known as:** DEBIAN-CVE-2025-11149, GHSA-27w5-gj5q-82fv, UBUNTU-CVE-2025-11149

## What is CVE-2025-11149?

CVE-2025-11149 is a high-severity denial of service vulnerability in @nubosoftware/node-static, published on 30 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

This affects all versions of the package node-static; all versions of the package @nubosoftware/node-static. The package fails to catch an exception when user input includes null bytes. This allows attackers to access http://host/%00 and crash the server.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2025-11149?

2 open source packages ship an affected version, including @nubosoftware/node-static.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@nubosoftware/node-static` | npm | All versions to 0.7.11 | None |
| `@nubosoftware/node-static` | npm | All versions to 0.7.11 | None |

## How do I fix CVE-2025-11149?

No fix has been published for CVE-2025-11149 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-11149 being exploited?

There is no known exploitation of CVE-2025-11149 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-11149 and fix it if it is affected.

What it is: CVE-2025-11149 is a high-severity denial of service vulnerability in @nubosoftware/node-static, published on 30 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-11149 in the wild and no public exploit code.

Affected packages and fixed versions:
- @nubosoftware/node-static (npm): affected all versions up to 0.7.11; no fix listed
- @nubosoftware/node-static (npm): affected all versions up to 0.7.11; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-11149/ (Markdown: https://insights.sbomify.com/CVE-2025-11149/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-11149
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-11149
- OSV: https://osv.dev/vulnerability/CVE-2025-11149

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-11149/
Summaries are generated and may contain mistakes; the official description above is the record.