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

> Authenticated users can probe mailbox existence and hijack push notifications in Cyrus IMAP, leaking metadata about other users' mailboxes.

- **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-47081, GHSA-w8cp-9j4g-wc9p, UBUNTU-CVE-2026-47081

## What is CVE-2026-47081?

CVE-2026-47081 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 an XAPPLEPUSHSERVICE folder existence oracle and push hijack. An authenticated IMAP user could probe for the existence of arbitrary mailboxes on other users' accounts via the XAPPLEPUSHSERVICE command and then create Apple Push Notification Service notifications for new mail in those mailboxes to their own APNS device. This did not leak any data about the content of mailboxes. Instead, a "mailbox has changed" notice would be pushed when the mailbox modseq changed.

Weakness: CWE-863 (Incorrect Authorization)

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


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

Upgrade to a fixed version.

## Is CVE-2026-47081 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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