# CVE-2026-44985: Dozzle: Cross-Site WebSocket Hijacking (CSWSH) on exec/attach endpoints bypasses authentication

> Attackers can hijack WebSocket connections to gain interactive shell access in Docker containers via cross-site requests.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/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:** Yes
- **Published:** 26 May 2026
- **Updated:** 28 May 2026
- **Also known as:** GHSA-j643-x8pv-8m67, GO-2026-5449

## What is CVE-2026-44985?

CVE-2026-44985 is a high-severity vulnerability in amir20 dozzle, published on 26 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Dozzle is a realtime log viewer for docker containers. Prior to 10.5.2, he WebSocket upgrader for the /exec and /attach endpoints uses CheckOrigin: func(r *http.Request) bool { return true }, accepting upgrade requests from any origin. Combined with the JWT cookie using SameSite: Lax, this enables Cross-Site WebSocket Hijacking (CSWSH). An attacker hosting a page on a same-site origin (e.g., a sibling subdomain, or another service on localhost) can initiate a WebSocket connection to the exec endpoint that carries the victim's valid JWT cookie, gaining interactive shell access in any container the victim is authorized to access. This vulnerability is fixed in 10.5.2.

Weakness: CWE-346 (Origin Validation Error)

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

3 open source packages ship an affected version, including github.com/amir20/dozzle. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/amir20/dozzle` | Go | All versions | None |
| `github.com/amir20/dozzle` | Go | All versions to 10.5.1 | None |
| `github.com/amir20/dozzle` | Go | All versions to 10.5.1 | None |

Products: Amirraminfar Dozzle.

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

Upgrade to a fixed version.

## Is CVE-2026-44985 being exploited?

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

## Other vulnerabilities in amir20 dozzle

- [CVE-2026-24740](https://insights.sbomify.com/CVE-2026-24740/): Dozzle Agent Label-Based Access Control Bypass Allows Unauthorized Container Shell Access (high 8.7)
- [CVE-2026-45298](https://insights.sbomify.com/CVE-2026-45298/): Dozzle: Pre-auth SSRF with response-body reflection via POST /api/notifications/test-webhook (default no-auth deploy) (high 8.6)
- [CVE-2024-47182](https://insights.sbomify.com/CVE-2024-47182/): Dozzle uses unsafe hash for passwords (medium 4.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-44985 is a high-severity vulnerability in amir20 dozzle, published on 26 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44985 exists.

Affected packages and fixed versions:
- github.com/amir20/dozzle (Go): affected all versions; no fix listed
- github.com/amir20/dozzle (Go): affected all versions up to 10.5.1; no fix listed
- github.com/amir20/dozzle (Go): affected all versions up to 10.5.1; 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-2026-44985/ (Markdown: https://insights.sbomify.com/CVE-2026-44985/index.md)
```

## Sources

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

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