Email data disclosure via retained send state
Published Feb 21, 2026 · Updated Feb 21, 2026
Data exposure in Lettermint Node.js SDK before 1.5.1 allows local users to disclose prior email fields to unintended recipients. EmailEndpoint.send posts the retained payload but does not clear recipient, content, attachment, header, metadata, or idempotency state afterward. Exploitation requires application-level access and a shared client instance used for sequential messages; disclosure is limited to fields carried from an earlier send.
Summary
What happened
Data exposure in Lettermint Node.js SDK before 1.5.1 allows local users to disclose prior email fields to unintended recipients. EmailEndpoint.send posts the retained payload but does not clear recipient, content, attachment, header, metadata, or idempotency state afterward. Exploitation requires application-level access and a shared client instance used for sequential messages; disclosure is limited to fields carried from an earlier send.
The record
- CVE
- CVE-2026-27492
- Published
- Feb 21, 2026
- Updated
- Feb 21, 2026
- Vendor
- Lettermint
- Product
- Lettermint Node.js SDK
- Classifications
- CWE-488
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 21, 2026CVE publishedPublication date reported by the CVE source.
- Feb 21, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.5.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo