# CVE-2026-46357: HAX CMS NodeJS application Vulnerable to Denial of Service using Malicious Import Request

> An authenticated attacker can crash the HAX CMS NodeJS application by sending a malicious site creation request, requiring a manual restart.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Jun 2026
- **Updated:** 9 Jun 2026
- **Also known as:** GHSA-9r33-xhw8-4qqp

## What is CVE-2026-46357?

CVE-2026-46357 is a medium-severity denial of service vulnerability in haxtheweb haxcms-nodejs, published on 5 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

HAX CMS helps manage microsite universe with PHP or NodeJs backends. Prior to version 26.0.0, the HAX CMS NodeJS application crashes when an authenticated attacker sends a specially crafted site creation request to the createSite endpoint. A single request is sufficient to take the entire application offline, requiring a manual server restart to restore service. Version 26.0.0 fixes the issue.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2026-46357?

2 open source packages ship an affected version, including @haxtheweb/haxcms-nodejs.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@haxtheweb/haxcms-nodejs` | npm | All versions | 26.0.0 |
| `@haxtheweb/haxcms-nodejs` | npm | All versions | 26.0.0 |

## How do I fix CVE-2026-46357?

Upgrade @haxtheweb/haxcms-nodejs to 26.0.0 or later.

## Is CVE-2026-46357 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-46357 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-46357 and fix it if it is affected.

What it is: CVE-2026-46357 is a medium-severity denial of service vulnerability in haxtheweb haxcms-nodejs, published on 5 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-46357 exists.

Affected packages and fixed versions:
- @haxtheweb/haxcms-nodejs (npm): affected all versions; fixed in 26.0.0
- @haxtheweb/haxcms-nodejs (npm): affected all versions; fixed in 26.0.0

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-2026-46357/ (Markdown: https://insights.sbomify.com/CVE-2026-46357/index.md)
```

## Sources

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

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