Skip to content
Fencer Vulns
critical 10.0

CVE-2025-52691 kev+ ransomware in the critical feed json

Upload Arbitrary Files

published 2025-12-29 10 mo ago modified 2026-10-07 32 d ago also EUVD-2025-205544

cvss
10.0
version 3.1, CNA
cisa kev
Exploited
added 2026-01-26, used in ransomware
epss
85.7%
EPSS 85.7% chance of exploitation in 30 days, percentile 99.7%
public exploits
1
Metasploit, plus a Nuclei check

Summary

Successful exploitation of the vulnerability could allow an unauthenticated attacker to upload arbitrary files to any location on the mail server, potentially enabling remote code execution.

Patch / fix

cisa required action Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

  • smartertools smartermail 100.0.9413

Timeline

  1. First public exploit (Metasploit exploit/multi/http/smartermail_guid_file_upload)
  2. Published
  3. Added to CISA KEV
  4. CISA SSVC: exploitation active
  5. CISA patch deadline

Known exploited

Added
9 mo ago
Patch by
2026-02-16 (8 mo ago)
Ransomware
Known to be used in ransomware campaigns
Required action
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Vendor, product
SmarterTools, SmarterMail
CISA name
SmarterTools SmarterMail Unrestricted Upload of File with Dangerous Type Vulnerability

CISA SSVC

Exploitation
Active, exploited in the wild
Automatable
yes
Technical impact
total
Assessed
9 mo ago

Exploit prediction

85.66% chance of exploitation in the next 30 days, higher than 99.7% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

CVSS scores

assigned by version score vector
CNA 3.1 10.0 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Affected products

  • SmarterTools SmarterMail

Classification

Weakness
  • CWE-434 Unrestricted Upload of File with Dangerous Type

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.