# CVE-2026-82973: Improper Neutralization of CRLF Sequences ('CRLF Injection') in docker-mailbox

> Remote attackers can inject IMAP commands into authenticated sessions if bearer-token authentication is disabled, allowing unauthorized mailbox access.

- **Severity:** Critical 9.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Sep 2026
- **Updated:** 29 Sep 2026
- **Also known as:** GHSA-j4qm-pqjf-933v

## What is CVE-2026-82973?

CVE-2026-82973 is a critical vulnerability in psyb0t docker-mailbox, published on 29 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Improper neutralization of CRLF sequences in IMAP command construction in psyb0t/docker-mailbox before 0.4.13 allows a remote unauthenticated attacker, when bearer-token authentication is not configured, to inject additional IMAP commands into an authenticated upstream mailbox connection via crafted folder, UID, or search values.

Weakness: CWE-93 (Improper Neutralization of CRLF Sequences)

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


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

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

## Is CVE-2026-82973 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-82973 is a critical vulnerability in psyb0t docker-mailbox, published on 29 Sep 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-82973 in the wild and no public exploit code.

Affected product: psyb0t docker-mailbox. 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-82973/ (Markdown: https://insights.sbomify.com/CVE-2026-82973/index.md)
```

## Sources

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

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