Vulnerability Database · Debian · Package report

roundcube: vulnerability history, versions and safety

roundcube is a package in the Debian ecosystem. Vulert records 173 vulnerabilities for it across 62 releases, from Nov -0001 to Aug 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
173 vulnerabilities recorded U173
i
31 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
36 in the last 12 months

Most recent disclosure 17 Aug 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on roundcube i

Updated on 23 Oct 2026

Careful: 31 of the 173 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 173 vulnerabilities on record across 2026 years, 36 in the last year.

What to do: Plan around the 31 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 173 over 2026 years · 36 in the last year i
  • Latest disclosure 17 Aug 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 31 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for roundcube, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
1.6.18+dfsg-1 U10 No Details →
1.6.17+dfsg-1 U14 No Details →
1.6.16+dfsg-1 U24 No Details →
1.6.15+dfsg-1 U24 No Details →
1.6.14+dfsg-1 U24 No Details →
1.6.13+dfsg-1 U26 No Details →
1.6.12+dfsg-1 U28 No Details →
1.6.11+dfsg-1 U31 No Details →
1.6.10+dfsg-2 U31 No Details →
1.6.10+dfsg-1 U31 No Details →
1.6.9+dfsg-2 U31 No Details →
1.6.9+dfsg-1 U31 No Details →
1.6.8+dfsg-2 U31 No Details →
1.6.8+dfsg-1 U31 No Details →
1.6.7+dfsg-1 U31 No Details →
1.6.6+dfsg-2 U31 No Details →
1.6.6+dfsg-1 U31 No Details →
1.6.5+dfsg-1 U31 No Details →
1.6.5+dfsg-1~deb12u1 U31 No Details →
1.6.4+dfsg-1 U31 No Details →
1.6.4+dfsg-1~deb12u1 U31 No Details →
1.6.3+dfsg-2 U31 No Details →
1.6.3+dfsg-1 U31 No Details →
1.6.3+dfsg-1~deb12u1 U31 No Details →
1.6.2+dfsg-1 U31 No Details →
1.6.1+dfsg-1 U31 No Details →
1.6.0+dfsg-2 U31 No Details →
1.6.0+dfsg-1.1 U31 No Details →
1.6.0+dfsg-1 U31 No Details →
1.6~beta+dfsg-2 U31 No Details →
1.6~rc+dfsg-2 U31 No Details →
1.6~beta+dfsg-1 U31 No Details →
1.6~rc+dfsg-1 U31 No Details →
1.5.1+dfsg-1 U31 No Details →
1.5.0+dfsg.1-2 U31 No Details →
1.5.0+dfsg.1-1 U31 No Details →
1.5~beta+dfsg.1-4 U31 No Details →
1.5~beta+dfsg.1-3 U31 No Details →
1.5~rc+dfsg.1-3 U31 No Details →
1.5~beta+dfsg.1-2 U31 No Details →
1.5~rc+dfsg.1-2 U31 No Details →
1.5~beta+dfsg.1-1 U31 No Details →
1.5~rc+dfsg.1-1 U31 No Details →
1.4.15+dfsg.1-1+deb11u10 U10 No Details →
1.4.15+dfsg.1-1+deb11u9 U16 No Details →
1.4.15+dfsg.1-1+deb11u8 U24 No Details →
1.4.15+dfsg.1-1+deb11u7 U33 No Details →
1.4.15+dfsg.1-1+deb11u6 U36 No Details →
1.4.15+dfsg.1-1+deb11u5 U42 No Details →
1.4.15+dfsg.1-1+deb11u4 U45 No Details →
1.4.15+dfsg.1-1+deb11u3 U52 No Details →
1.4.15+dfsg.1-1~deb11u2 U57 No Details →
1.4.15+dfsg.1-1~deb11u2~bpo10+1 U60 No Details →
1.4.15+dfsg.1-1~deb11u1 U60 No Details →
1.4.15+dfsg.1-1~deb11u1~bpo10+1 U63 No Details →
1.4.14+dfsg.1-1~deb11u1 U63 No Details →
1.4.14+dfsg.1-1~deb11u1~bpo10+1 U65 No Details →
1.4.13+dfsg.1-1~deb11u1 U65 No Details →
1.4.13+dfsg.1-1~deb11u1~bpo10+1 U67 No Details →
1.4.12+dfsg.1-1~deb11u1 U67 No Details →
1.4.12+dfsg.1-1~bpo10+1 U71 No Details →
1.4.11+dfsg.1-4 U71 No Details →

Newest 62 of 62 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 0 3
  • 2007 2
  • 2008 4
  • 2009 6
  • 2010 2
  • 2011 8
  • 2012 6
  • 2013 4
  • 2014 2
  • 2015 6
  • 2016 12
  • 2017 16
  • 2018 8
  • 2019 3
  • 2020 18
  • 2021 10
  • 2022 2
  • 2023 8
  • 2024 12
  • 2025 6
  • 2026 35

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 36 of the 173 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for roundcube

The 5 most severe of 173 vulnerabilities recorded for this package

Search all 173 in the database →

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About roundcube

Is roundcube safe to use?

Vulert records 173 vulnerabilities for roundcube in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 173 not yet rated. 31 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does roundcube have?

173 vulnerabilities are recorded for roundcube in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 173 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new roundcube vulnerabilities disclosed?

36 vulnerabilities were recorded for roundcube in the last 12 months, and the oldest entry in this database dates to 30 Nov -0001. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of roundcube are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor roundcube for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the roundcube version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.