dbcve.org
WebmailApplication · Roundcube

CVE-2026-35543

MEDIUM · 5.3 CVSS v3.1 Published 2026-04-03
Fix available
A fix is available. Upgrade to 1.5.14 / 1.6.14 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An issue was discovered in Roundcube Webmail before 1.5.14 and 1.6.14. The remote image blocking feature can be bypassed via SVG content (with animate attributes) in an e-mail message. This may lead to information disclosure or access-control bypass.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
WebmailApplication
Affected:< 1.5.14>= 1.6.0, < 1.6.14

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.5.14 / 1.6.14 or later
Fixed in 1.5.141.6.14
Vendor patch github.com →
Recommended fix High confidence

Roundcube Webmail 1.5.14 (for 1.5.x branch) or 1.6.14 (for 1.6.x branch)

  1. Identify your current Roundcube Webmail version by checking the VERSION file or program/include/rcmail.php file
  2. Determine which branch you are on (1.5.x or 1.x) by checking your version number
  3. For 1.5.x branch: Download Roundcube Webmail 1.5.14 or later from https://github.com/roundcube/roundcubemail/releases
  4. For 1.6.x branch: Download Roundcube Webmail 1.6.14 or later from https://github.com/roundcube/roundcubemail/releases
  5. Backup your current Roundcube installation including the config/ directory and any plugins
  6. Extract the new version archive to replace the existing installation
  7. Restore your configuration files from the backup (config/main.inc.php, config/db.inc.php)
  8. Test that login and basic functionality work after the upgrade
Caveat Check release notes for any breaking changes between your current version and the target version; standard upgrade precautions apply (backup before upgrading)

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-35543 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-35543 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data