# CVE-2026-47089: Missing authorization in Cyrus IMAP

> Authenticated users can improperly view access rights for any mailbox, exposing sensitive permission data to unauthorized parties.

- **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:** 16 Jul 2026
- **Updated:** 16 Jul 2026
- **Also known as:** DEBIAN-CVE-2026-47089, GHSA-fx86-vr4x-grgq, UBUNTU-CVE-2026-47089

## What is CVE-2026-47089?

CVE-2026-47089 is a medium-severity missing authorization 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. LISTRIGHTS os not limited to users with admin access. An authenticated user could call IMAP LISTRIGHTS against any mailbox they could name and learn what principals had what access to it. (This action should have been restricted to users with admin access on the target mailbox.)

Weakness: CWE-862 (Missing Authorization)

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


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

Apply the vendor's patch.

## Is CVE-2026-47089 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-47089 is a medium-severity missing authorization 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-47089 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-47089/ (Markdown: https://insights.sbomify.com/CVE-2026-47089/index.md)
```

## Sources

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

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