Cyber Resilience

CVE-2026-40514

Smartertools Smartermail ≤ 100.0.9610

Public PoC
Published
27 April 2026
Modified
04 June 2026
CVSS Score v4 8.2
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0015 5th percentile
Risk Priority 32 floored blend · peak EPSS

Summary

CVE-2026-40514 is a high-severity PRNG (CWE-338) vulnerability in Smartertools Smartermail. Its CVSS base score is 8.2 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Forge Web Credentials (T1606); ranked at the 5th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SC-13 (Cryptographic Protection) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A04:2025 Cryptographic Failures

EU & UK References

Vulnerability Data

SmarterTools SmarterMail builds prior to 9610 contain a cryptographic weakness in the file and email sharing endpoints that use DES-CBC encryption with keys and initialization vectors derived from System.Random seeded with insufficient entropy, reducing the seed space to approximately 19,000…

more

possible values. An unauthenticated attacker can use the attachment download endpoint as an oracle to determine the seed in use and derive encryption keys and initialization vectors to forge sharing tokens for arbitrary emails, attachments, or file storage contents without prior access to the targeted content.

CWE(s)
CWE-338

Related Threats

MITRE ATT&CK Enterprise Techniques

T1606 Forge Web Credentials Credential Access
Adversaries may forge credential materials that can be used to gain access to web applications or Internet services.
attack.mitre.org →
T1606.001 Web Cookies Credential Access
Adversaries may forge web cookies that can be used to gain access to web applications or Internet services.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-7807Same product: Smartertools Smartermail
CVE-2026-23760Same product: Smartertools Smartermail
CVE-2023-48114Same product: Smartertools Smartermail
CVE-2026-24423Same product: Smartertools Smartermail
CVE-2023-48116Same product: Smartertools Smartermail
CVE-2026-25067Same product: Smartertools Smartermail
CVE-2019-7214Same product: Smartertools Smartermail
CVE-2025-52691Same product: Smartertools Smartermail
CVE-2023-48115Same product: Smartertools Smartermail
CVE-2025-26379Shared CWE-338

Affected Assets

smartertools
smartermail
≤ 100.0.9610

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)
  • 3 hardening rules · 3 OS baselines
Validate
Prove the fix (OWASP ASVS)
  • V7.2.3
  • V11.5.1

Mitigating Controls (NIST 800-53 r5) AI

SC-13 Cryptographic Protection good match

Requiring specific approved cryptography for protection directly mandates use of strong PRNGs instead of weak ones.

SA-8 Security and Privacy Engineering Principles partial match

Engineering principles applied during design and development include selection of cryptographically strong random number generation.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices explicitly require cryptographically strong RNG selection and usage in security contexts.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.24 Use of cryptography mostly match
prevents

Mandates use of approved cryptographic controls, directly requiring cryptographically strong RNGs.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect use of weak random number generators.

A.8.25 Secure development life cycle partial match
prevents

Secure SDLC processes should catch weak PRNG usage during design and code review.

A.8.26 Application security requirements partial match
prevents

Application security requirements can specify cryptographically strong random number generation.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure engineering principles include selection of appropriate cryptographic primitives.

A.8.28 Secure coding partial match
prevents

Secure coding standards prohibit use of weak PRNGs in security contexts.

Hardening callouts derived

Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).

Oracle Linux 8 (1 rule)
  • V-248563 The OL 8 SSH server must be configured to use strong entropy. prevents CWE-338
RHEL 8 (1 rule)
  • V-230253 RHEL 8 must ensure the SSH server uses strong entropy. prevents CWE-338
Ubuntu 22.04 (1 rule)
  • V-260650 Ubuntu 22.04 LTS must implement NIST FIPS-validated cryptography to protect classified information and for the following: To provision digital signatures, to generate cryptographic hashes, and to protect unclassified information requiring confidentiality and cryptographic protection in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards. prevents CWE-338

References