# CVE-2026-53977: OpenChamber 1.11.7 Unauthenticated DoS via /api/system/shutdown

> Unauthenticated attackers can shut down the OpenChamber server by exploiting route registration order, causing denial of service for all users.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Aug 2026
- **Updated:** 6 Aug 2026
- **Also known as:** GHSA-hw79-7vhm-4hc6

## What is CVE-2026-53977?

CVE-2026-53977 is a high-severity authentication bypass vulnerability in Bohdan Triapitsyn OpenChamber, published on 6 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

OpenChamber 1.11.7 contains an authentication bypass vulnerability that allows unauthenticated remote attackers to terminate the server process by sending a POST request to the /api/system/shutdown endpoint, which is registered before the authentication middleware in the Express route handler chain. Attackers can exploit the route registration order in bootstrap-runtime.js to reach the shutdown handler before auth middleware executes, causing denial of service to all active AI coding sessions and locking out legitimate remote users regardless of whether UI_PASSWORD is configured.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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


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

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

## Is CVE-2026-53977 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-53977 is a high-severity authentication bypass vulnerability in Bohdan Triapitsyn OpenChamber, published on 6 Aug 2026. 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-2026-53977 in the wild and no public exploit code.

Affected product: Bohdan Triapitsyn OpenChamber. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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