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

> A user can bypass ACL restrictions to save vacation auto-reply copies into unauthorized mailboxes using the Sieve :fcc feature.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L`)
- **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-47082, GHSA-pwfr-vrq6-chw9, UBUNTU-CVE-2026-47082

## What is CVE-2026-47082?

CVE-2026-47082 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. The vacation "fcc" feature skips the destination-mailbox ACL. A user whose vacation Sieve script used :fcc (to save a copy of the sent message) could deliver vacation auto-reply copies into any mailbox the script could name, regardless of whether the script owner had insert permissions on the destination mailbox.

Weakness: CWE-863 (Incorrect Authorization)

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


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

Apply the vendor's patch.

## Is CVE-2026-47082 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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