cve.bz

CVE-2026-114730 roundcube webmail: SSRF

7.2 highEPSS 0.4%Fix available

High (7.2) in roundcube webmail. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
Roundcube Webmail 1.6.14 before 1.6.20 and 1.7.0 before 1.7.5 is affected by a server-side request forgery filter bypass. The network blocklist used by rcube_utils::is_local_url() omitted the RFC 6052 NAT64 prefix 64:ff9b::/96, the RFC 8215 local-use NAT64 prefix 64:ff9b:1::/48 and the unspecified address ::/128, so URLs such as http://[64:ff9b::7f00:1]/ passed the filter and reached loopback, link-local and cloud metadata addresses. Upstream fixed this in the commit “Fix SSRF filter (is_local_url()) bypass via NAT64 64:ff9b::/96”.

Severity

CVSS 3.1

7.2 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/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-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-918 Server-Side Request Forgery (SSRF)
OWASP Top 10
A01:2025 Broken Access Control
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-114730 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-114730?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-114730?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-114730 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.14 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-114730
Debian13roundcube1.6.20+dfsg-0+deb13u1DEBIAN-CVE-2026-114730
Debian14roundcube1.6.20+dfsg-1DEBIAN-CVE-2026-114730
Ubuntu26.10, Pro:16.04:LTS, Pro:18.04:LTS and 4 moreroundcubeno fix listedUBUNTU-CVE-2026-114730

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

Red Hat's statement

This vulnerability is rated as an Important severity flaw because an unauthenticated remote attacker can bypass destination host restrictions and query internal services or cloud instance metadata. Such cross-boundary requests can expose sensitive deployment details and internal endpoints directly from the host application. Roundcube is not included in supported Red Hat Enterprise Linux offerings or enterprise products, and is distributed solely via community projects such as Fedora and EPEL.

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

Attack patterns (CAPEC)

  • CAPEC-664 Server Side Request Forgery Likelihood: High · Severity: High

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

References

Check your stackJSON