# CVE-2026-114730: 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.


- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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-114730, GHSA-8f6h-w7cq-8q8h, UBUNTU-CVE-2026-114730

## What is CVE-2026-114730?

CVE-2026-114730 is a high-severity vulnerability in Roundcube Webmail, published on 22 Oct 2026. 

### Official description

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

Weakness: CWE-918 (Server-Side Request Forgery)

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


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

Upgrade to a fixed version.

## Is CVE-2026-114730 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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