Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unratedamended

AgenticMail API/storage and outbound relay hardening fixes

CVE-2026-47255GHSA-wjjv-3mj2-39hf

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (@agenticmail/api 0.9.32; @agenticmail/core 0.9.10), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
  • CVE-2026-47255: 0.25% estimated exploitation activity in the next 30 days; percentile 16.72 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-wjjv-3mj2-39hf

  2. Revision 1 · created ·

    Published from osv record GHSA-wjjv-3mj2-39hf

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-47255

Advisory: AgenticMail API/storage and outbound relay hardening fixes
IDs: CVE-2026-47255, GHSA-wjjv-3mj2-39hf
Record: https://patchnext.com/advisories/cve-2026-47255 (revision 2, source checked 26 Oct 2026, 12:52 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @agenticmail/api 0.9.32; @agenticmail/core 0.9.10. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @agenticmail/api: affected <= 0.9.31; fixed in 0.9.32
- npm @agenticmail/core: affected <= 0.9.9; fixed in 0.9.10

## Suggested inspection (read-only)
- `npm ls @agenticmail/api --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
- `npm ls @agenticmail/core --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @agenticmail/api, @agenticmail/core.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-wjjv-3mj2-39hf (OSV record GHSA-wjjv-3mj2-39hf lists affected ranges: npm @agenticmail/api >=0 =0 <0.9.10 (fixed))
- Verified: https://github.com/advisories/GHSA-wjjv-3mj2-39hf (GitHub-reviewed advisory GHSA-wjjv-3mj2-39hf lists affected ranges: npm @agenticmail/api >=0 =0 <=0.9.9)

Commands are suggestions: review each one before running it.

Loading voting…