cve.bz

CVE-2026-114728 roundcube webmail: Incomplete List of Disallowed Inputs

5.3 mediumEPSS 0.4%Fix available

Medium (5.3) in roundcube webmail. EPSS 0.4% 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 remote content blocking bypass in the handling of FuncIRI attributes. rcube_washtml detected the CSS url() token with a pattern that enumerated only some of its escaped spellings, so values using other CSS escape sequences, for example \000075rl( or u\72 l(, were not recognized and remote content was loaded from an HTML message without the user's consent. Upstream fixed this in the commit “Fix remote content blocking bypass via CSS escapes in FuncIRI attributes (again)”, which resolves CSS escapes before matching and also inspects the `to`, `from` and `by` attributes.

Severity

CVSS 3.1

5.3 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
EPSS
0.4% (unchanged from 0.4% a week ago) estimated probability of exploitation activity in the next 30 days; 32nd 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-26. 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-184 Incomplete List of Disallowed Inputs
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-114728 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-114728?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-114728?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-114728 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-114728
Debian13roundcube1.6.20+dfsg-0+deb13u1DEBIAN-CVE-2026-114728
Debian14roundcube1.6.20+dfsg-1DEBIAN-CVE-2026-114728
Ubuntu26.10, Pro:16.04:LTS, Pro:18.04:LTS and 4 moreroundcubeno fix listedUBUNTU-CVE-2026-114728

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 flaw is rated as Moderate severity rather than Important because successful exploitation is confined to unauthorized retrieval of external web resources, resulting in limited information exposure without code execution or database compromise. In standard Red Hat Enterprise Linux environments, Roundcube Webmail is not distributed as a supported core product and is only packaged through community repositories such as EPEL. The issue occurs when the webmail sanitizer fails to process obfuscated styling tokens, which allows incoming messages to circumvent client privacy safeguards and trigger outbound network requests upon display.

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-114728.

Attack patterns (CAPEC)

  • CAPEC-3 Using Leading 'Ghost' Character Sequences to Bypass Input Filters Likelihood: Medium · Severity: Medium
  • CAPEC-6 Argument Injection Likelihood: High · Severity: High
  • CAPEC-15 Command Delimiters Likelihood: High · Severity: High
  • CAPEC-43 Exploiting Multiple Input Interpretation Layers Likelihood: Medium · Severity: High
  • CAPEC-71 Using Unicode Encoding to Bypass Validation Logic Likelihood: Medium · Severity: High
  • CAPEC-73 User-Controlled Filename Likelihood: High · Severity: High
  • CAPEC-85 AJAX Footprinting Likelihood: High · Severity: Low
  • CAPEC-120 Double Encoding Likelihood: Low · Severity: Medium
  • CAPEC-182 Flash Injection Likelihood: High · Severity: Medium

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON