cve.bz

CVE-2026-114722 roundcube webmail

6.5 mediumEPSS 0.3%Fix available

Medium (6.5) in roundcube webmail. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
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”.

Severity

CVSS 3.1

6.5 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
EPSS
0.3% (unchanged from 0.3% a week ago) estimated probability of exploitation activity in the next 30 days; 17th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-10-28. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-669 Incorrect Resource Transfer Between Spheres
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-114722 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-114722?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-114722?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-114722 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Roundcube Webmailfrom 1.6.0 before 1.6.20
Roundcube Webmailfrom 1.7.0 before 1.7.5

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12roundcube1.6.5+dfsg-1+deb12u13DEBIAN-CVE-2026-114722
Debian13roundcube1.6.20+dfsg-0+deb13u1DEBIAN-CVE-2026-114722
Debian14roundcube1.6.20+dfsg-1DEBIAN-CVE-2026-114722
Ubuntu26.10, Pro:16.04:LTS, Pro:18.04:LTS and 4 moreroundcubeno fix listedUBUNTU-CVE-2026-114722

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This vulnerability is rated as Moderate impact because successful exploitation requires a recipient to open a crafted email message and is limited to visual interface redressing rather than arbitrary code execution or credential theft. While attackers can manipulate styles outside the email display area to mislead users, the underlying server integrity remains unaffected. Furthermore, roundcubemail is not included in supported Red Hat Enterprise Linux releases and is maintained only in community distributions like EPEL and Fedora.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-114722.

References

Check your stackJSON