CVE-2026-47255
HIGHSeverity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L
Primary rating from Vendor (https://github.com/agenticmail/agenticmail) · only source for this CVE.
CVSS VectorVendor: https://github.com/agenticmail/agenticmail
Lifecycle Timeline
5DescriptionCVE.org
The current upstream main branch at commit 7e0206d was reviewed, and the fix-first patch set was rebased on 2026-05-18. The patches cover: validated and bound inactive-agent hour filtering; storage SQL identifier validation; metadata-backed ownership checks for raw storage SQL; blocking direct storage metadata access through raw SQL; fail-closed outbound worker secret handling; SMTP envelope/header control-character validation before command construction; and TLS certificate verification as the default for MailSender with an explicit opt-out for local development. Validation completed locally with targeted API/Core security tests plus API/Core builds. The security patch branch was not published publicly because te repository's SECURITY.md asks reporters not to open public vulnerability issues.
AnalysisAI
Improper input validation in AgenticMail's storage API (npm @agenticmail/api <= 0.9.31 and @agenticmail/core <= 0.9.9) lets callers reach storage tables and clauses that bypass tenant ownership enforcement. The bundled hardening set fixes a raw-interpolated SQL HAVING clause, a comma-join table-reference parsing gap that let cross-tenant tables (e.g. agt_victim) escape ownership checks, plus SMTP header control-character injection and a MailSender that did not verify TLS certificates by default. EPSS is very low (0.01%, 3rd percentile) and there is no public exploit identified at time of analysis, so this is a disclosed-and-patched supply-chain library issue rather than an actively exploited one.
Same weakness CWE-20 – Improper Input Validation
View allSame technique Information Disclosure
View allShare
External POC / Exploit Code
Leaving vuln.today
GHSA-wjjv-3mj2-39hf