Skip to content
Fencer Intel
high 8.2

CVE-2026-47255 json

AgenticMail API/storage and outbound relay hardening

published 5mo ago modified 2mo ago also GHSA-wjjv-3mj2-39hf , EUVD-2026-46121

cvss
8.2
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 16%
public exploits
0
none known

Summary

AgenticMail gives AI agents real email addresses and phone numbers. @agenticmail/api prior to version 0.9.32 and @agenticmail/core prior to version 0.9.10 had weakness related to validation and and binding of 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. @agenticmail/api prior to version 0.9.32 and @agenticmail/core prior to version 0.9.10 are patched.

Patch / fix

  • npm @agenticmail/api 0.9.32
  • npm @agenticmail/core 0.9.10

Is CVE-2026-47255 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
3mo ago

Exploit prediction

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

CVSS scores

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

Affected packages

ecosystem package affected fixed in
npm @agenticmail/api
<0.9.32
0.9.32
npm @agenticmail/core
<0.9.10
0.9.10

Affected products

  • agenticmail @agenticmail/api
  • agenticmail @agenticmail/core

Classification

Weakness
  • CWE-20 Improper Input Validation
  • CWE-89 Improper Neutralization of Special Elements used in an SQL Command
  • CWE-284 Improper Access Control
  • CWE-319 Cleartext Transmission of Sensitive Information
  • CWE-798 Use of Hard-coded Credentials

References

Sources

Fencer Intel 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.