# CVE-2026-47088: Information disclosure in Cyrus IMAP

> An authenticated user can read heap memory by crafting a specific email message, potentially exposing sensitive data.

- **Severity:** Low 3.1 (`CVSS:3.1/AV:N/AC:H/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:** 16 Jul 2026
- **Updated:** 16 Jul 2026
- **Also known as:** DEBIAN-CVE-2026-47088, GHSA-f77j-qm5m-p6cw, UBUNTU-CVE-2026-47088

## What is CVE-2026-47088?

CVE-2026-47088 is a low-severity vulnerability in cyrusimap Cyrus IMAP, published on 16 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered in cyrus-imapd in Cyrus IMAP through 3.12.2. There is heap exposure in nested MIME comment parsing. An authenticated IMAP user could craft an email message containing an RFC 822 comment ending with a backslash. When parsing the message, the server would read past the message's end in memory, and read into the heap, returning the read content to the user.

Weakness: CWE-126 (Buffer Over-read)

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


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

Upgrade to a fixed version.

## Is CVE-2026-47088 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-47088 is a low-severity vulnerability in cyrusimap Cyrus IMAP, published on 16 Jul 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-47088 in the wild and no public exploit code.

Affected product: cyrusimap Cyrus IMAP. 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-47088/ (Markdown: https://insights.sbomify.com/CVE-2026-47088/index.md)
```

## Sources

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

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