# CVE-2026-25916: Information disclosure in Webmail

> Attackers can bypass remote image blocking in Roundcube Webmail to track users via SVG feImage elements when the feature is enabled.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 9 Feb 2026
- **Updated:** 9 Feb 2026
- **Also known as:** DEBIAN-CVE-2026-25916, GHSA-q3rv-p5xv-cfpq, UBUNTU-CVE-2026-25916

## What is CVE-2026-25916?

CVE-2026-25916 is a medium-severity vulnerability in Roundcube Webmail, published on 9 Feb 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Roundcube Webmail before 1.5.13 and 1.6 before 1.6.13, when "Block remote images" is used, does not block SVG feImage.

Weakness: CWE-420 (Unprotected Alternate Channel)

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


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

Upgrade to a fixed version.

## Is CVE-2026-25916 being exploited?

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

Public exploit code:

- https://github.com/mbanyamer/CVE-2026-25916-Roundcube-Webmail-DOM-based-XSS-Exploit-via-SVG-href-Attribute (github_poc): https://github.com/mbanyamer/CVE-2026-25916-Roundcube-Webmail-DOM-based-XSS-Exploit-via-SVG-href-Attribute

## Fix prompt for AI coding agents

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

What it is: CVE-2026-25916 is a medium-severity vulnerability in Roundcube Webmail, published on 9 Feb 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-25916 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-25916/ (Markdown: https://insights.sbomify.com/CVE-2026-25916/index.md)
```

## Sources

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

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