cve.bz

CVE-2026-114723 roundcube webmail

5.3 mediumEPSS 0.5%Fix available

Medium (5.3) in roundcube webmail. EPSS 0.5% 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 allows the ImageMagick resource limits to be bypassed during thumbnail generation. When rcube_image falls back to GD, the available-memory check was applied only on Windows, so on other platforms a crafted image with large dimensions was processed by GD without any resource limit and could exhaust server memory. Upstream fixed this in the commit “Fix ImageMagick resource limits bypass by GD fallback during thumbnail generation”, which applies the memory check on all platforms.

Severity

CVSS 3.1

5.3 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
EPSS
0.5% (unchanged from 0.5% a week ago) estimated probability of exploitation activity in the next 30 days; 40th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-770 Allocation of Resources Without Limits or Throttling
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-114723 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-114723?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-114723?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-114723 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-114723
Debian13roundcube1.6.20+dfsg-0+deb13u1DEBIAN-CVE-2026-114723
Debian14roundcube1.6.20+dfsg-1DEBIAN-CVE-2026-114723
Ubuntu26.10, Pro:16.04:LTS, Pro:18.04:LTS and 4 moreroundcube, imagemagickno fix listedUBUNTU-CVE-2026-114723
UbuntuPro:14.04:LTSimagemagickno fix listedUBUNTU-CVE-2026-114723

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

Red Hat's statement

A low-severity denial-of-service flaw was found in Roundcube Webmail. When thumbnail generation falls back to the GD graphics library on non-Windows platforms, the available-memory check is not enforced, so a remote attacker can submit a crafted image with excessively large dimensions and exhaust server memory. Update to Roundcube Webmail 1.6.20 or 1.7.5, or backport the upstream one-line fix that applies the memory check on all platforms.

Red Hat's mitigation

Update to Roundcube Webmail 1.6.20 or 1.7.5, which apply the available-memory check on all platforms during GD fallback thumbnail generation. For EPEL 9's roundcubemail 1.5.15 (no upstream 1.5.x fix released), backport the one-line fix from upstream commits 0bea8112 / d28a5703 that removes the Windows-only condition around mem_check(), or update to a fixed version. Alternatively, ensure ImageMagick is configured to handle image conversion so the GD fallback path is not taken.

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

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-770 (20).

References

Check your stackJSON