# CVE-2026-114722: Roundcube Webmail before 1.6.20 and 1.7.x before 1.7.5 is affected by a CSS scoping bypass in HTML messages.


- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 22 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-114722, GHSA-jg35-cc9w-63m9, UBUNTU-CVE-2026-114722

## What is CVE-2026-114722?

CVE-2026-114722 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 a CSS scoping bypass in HTML messages. rcube_utils::mod_css_styles() did not treat an at-rule prologue such as @layer a; as a selector boundary, and did not handle selectors beginning with ::, so selectors following an at-rule were left unscoped and applied to the whole Roundcube interface instead of being confined to the message body. This allows an HTML message to restyle application chrome for UI redressing and spoofing. Upstream fixed this in the commit “Fix CSS scoping bypass in HTML messages using at-rules”.

Weakness: CWE-669 (Incorrect Resource Transfer Between Spheres)

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


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

Upgrade to a fixed version.

## Is CVE-2026-114722 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-114722 is a medium-severity vulnerability in Roundcube Webmail, published on 22 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-114722 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-114722/ (Markdown: https://insights.sbomify.com/CVE-2026-114722/index.md)
```

## Sources

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

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