# CVE-2026-48845: Information disclosure in Webmail

> Attackers can bypass remote image blocking for local URLs in Roundcube Webmail, potentially leading to information disclosure or privilege escalation via crafted emails.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 May 2026
- **Updated:** 27 May 2026
- **Also known as:** DEBIAN-CVE-2026-48845, GHSA-g4h2-2gp2-j3wq, UBUNTU-CVE-2026-48845

## What is CVE-2026-48845?

CVE-2026-48845 is a medium-severity vulnerability in Roundcube Webmail, published on 25 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In Roundcube Webmail 1.6.x between 1.6.14 and 1.6.16 and 1.7.x before 1.7.1, remote image blocking was not honored for URLs pointing to local/private destinations, which may lead to information disclosure or privilege escalation via a text/html email message.

Weakness: CWE-669 (Incorrect Resource Transfer Between Spheres)

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


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

Upgrade to a fixed version.

## Is CVE-2026-48845 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-48845 is a medium-severity vulnerability in Roundcube Webmail, published on 25 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-48845 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-48845/ (Markdown: https://insights.sbomify.com/CVE-2026-48845/index.md)
```

## Sources

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

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