# CVE-2026-42392: Information disclosure in OX Dovecot CE

> Authenticated attackers can disclose process memory via invalid IMAP URLFETCH commands, potentially exposing sensitive data in Dovecot servers.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **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:** 28 Aug 2026
- **Updated:** 28 Aug 2026
- **Also known as:** ALPINE-CVE-2026-42392, AZL-98277, DEBIAN-CVE-2026-42392, GHSA-cq8p-2j3r-5hxq, UBUNTU-CVE-2026-42392

## What is CVE-2026-42392?

CVE-2026-42392 is a medium-severity vulnerability in Open-Xchange GmbH OX Dovecot CE, published on 28 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An attacker that has valid credentials can send an invalid IMAP URLFETCH command, which causes uninitialized memory to be included in the error response returned to the client. Process memory contents can be disclosed to the client, which may include sensitive data. Disable the IMAP URLAUTH functionality. Update to non-vulnerable version. No publicly available exploits are known.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

Upgrade to a fixed version.

## Is CVE-2026-42392 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-42392 is a medium-severity vulnerability in Open-Xchange GmbH OX Dovecot CE, published on 28 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-42392 in the wild and no public exploit code.

Affected product: Open-Xchange GmbH OX Dovecot CE. 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-42392/ (Markdown: https://insights.sbomify.com/CVE-2026-42392/index.md)
```

## Sources

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

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