WebmailApplication · Roundcube

CVE-2026-62642

MEDIUM · 6.5 CVSS v3.1 Published 2026-07-14
Fix available
A fix is available. Upgrade to 1.6.17 / 1.7.2 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges 5 weeks old

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
In Roundcube Webmail before 1.6.17 and 1.7.x before 1.7.2, an infinite loop was discovered in the TNEF decoder, which may lead to denial of service upon opening an email with a TNEF attachment.

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 · high confidence

Roundcube Webmail contains an infinite loop vulnerability in its TNEF (Transport Neutral Encapsulation Format) decoder. When a user opens or previews an email containing a specially crafted TNEF attachment, the decoder enters an infinite loop, causing the PHP process to hang and resulting in denial of service.

MitigationUpgrade Roundcube Webmail to version 1.6.17 or 1.7.2 or later to resolve the infinite loop vulnerability in the TNEF decoder.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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.6.0, < 1.6.17>= 1.7.0, < 1.7.2

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
Required
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Roundcube version
    Locate the version file or check the program version constant in your Roundcube installation (typically found in program/include/rcmail.php or a version.php file)
    Affected if The installed version falls within >= 1.6.0 and < 1.6.17, or >= 1.7.0 and < 1.7.2
  2. Compare version to affected ranges
    Compare your identified version number against the vulnerable ranges: 1.6.0 through 1.6.16, and 1.7.0 through 1.7.1
    Affected if Your version is one of the affected versions listed
  3. Verify TNEF processing is in use
    Determine if your Roundcube instance processes TNEF attachments (used for winmail.dat attachments). This is typically handled by the tnef plugin or built-in handling for email attachments
    Affected if TNEF attachment decoding is enabled and your Roundcube version is affected

You are affected if your installed Roundcube Webmail version is between 1.6.0 and 1.6.16, or between 1.7.0 and 1.7.1, and TNEF attachment processing is active.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.6.17 / 1.7.2 or later
Fixed in 1.6.171.7.2
Interim mitigation

Upgrade Roundcube Webmail to version 1.6.17 or 1.7.2 or later to resolve the infinite loop vulnerability in the TNEF decoder.

Recommended fix High confidence

Upgrade to Roundcube Webmail 1.6.17 or 1.7.2 (or latest stable 1.7.x)

  1. Identify the currently installed Roundcube Webmail version by checking the version file or admin interface
  2. For versions 1.6.0 through 1.6.16: upgrade to version 1.6.17
  3. For versions 1.7.0 through 1.7.1: upgrade to version 1.7.2
  4. Backup the current installation and database before upgrading
  5. Follow the standard Roundcube upgrade procedure: download the new version, extract to web directory, run database migrations if needed, clear caches
  6. Restart web server if required
  7. Verify the upgrade was successful by checking the Roundcube version and testing email functionality
Caveat Standard Roundcube minor version upgrades typically have minimal breaking changes; review release notes for any plugin or configuration incompatibilities

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

Fix this in Webmail Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-62642 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