# CVE-2026-114732: Roundcube Webmail before 1.6.20 and 1.7.x before 1.7.5 is affected by an improper authentication vulnerability in multi-host installations.


- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 22 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-114732, GHSA-qc6m-xxcv-cwh2, UBUNTU-CVE-2026-114732

## What is CVE-2026-114732?

CVE-2026-114732 is a medium-severity vulnerability in Roundcube Webmail, published on 22 Oct 2026. 

### Official description

Roundcube Webmail before 1.6.20 and 1.7.x before 1.7.5 is affected by an improper authentication vulnerability in multi-host installations. When a user logs in with an alias address, rcube_user::query() matched the address against identity records without qualifying the lookup by IMAP host, so a login could be resolved to a user account belonging to a different IMAP host. Upstream fixed this in the commit “Fix bug where an alias login wasn’t qualified by IMAP host”.

Weakness: CWE-288 (Authentication Bypass Using an Alternate Path or Channel)

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


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

Upgrade to a fixed version.

## Is CVE-2026-114732 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-114732 is a medium-severity vulnerability in Roundcube Webmail, published on 22 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-114732 in the wild and no public exploit code.

Affected product: Roundcube Webmail. 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-114732/ (Markdown: https://insights.sbomify.com/CVE-2026-114732/index.md)
```

## Sources

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

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