CVE-2026-57495

HIGHPre-NVD 8.28.2—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 71% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
8.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.2Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

AgenticMail gives AI agents real email addresses and phone numbers. In @agenticmail/claudecode prior to version 0.2.39, @agenticmail/codex prior to version 0.1.33, @agenticmail/core prior to version 0.9.43, and @agenticmail/openclaw prior to version 0.5.71, two inbound-mail handlers act on a privileged effect without verifying that the sender is the operator, while a sibling handler in the same repo does. The higher-impact one: any external email routed to the bridge inbox causes the dispatcher to resume the operator's Claude Code session with permissionMode: 'bypassPermissions', embedding the attacker-controlled from/subject/preview verbatim into the prompt the resumed agent reads — an indirect prompt injection into a fully-privileged agent (Bash/Write/Edit/WebFetch + the agenticmail MCP toolbelt) running as the operator's OAuth identity. The sibling operator-query email-reply hook gates the same untrusted-From provenance with isOperatorReplySender(replyFrom, config.operatorEmail) (fail-closed); the bridge-wake path — a strictly higher-privilege effect — has no equivalent. @agenticmail/claudecode 0.2.39, @agenticmail/codex 0.1.33, @agenticmail/core 0.9.43, and @agenticmail/openclaw 0.5.71 contain a fix.

CVSS v3
8.2
EG Score
8.2(medium)
EG Risk
52(Track)
EG Risk 52/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity82% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
30%
KEV
Not listed

Published

July 20, 2026

Last Modified

July 23, 2026

Advisory Details (1)

Auto-updated Jul 20, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

Unauthenticated inbound mail triggers bypassPermissions resume of the operator's Claude Code session (bridge-wake) with no sender gate, while the sibling operator-query hook authenticates the sender (CWE-306) · Advisory · agenticmail/agenticmail · GitHub

https://github.com/agenticmail/agenticmail/security/advisories/GHSA-fq4x-789w-jg5h

Vendor Advisories for CVE-2026-57495(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(4 across 1 ecosystem)
npm(4)
PackageVulnerable rangeFixed inDependents
@agenticmail/claudecode—0.2.39—
@agenticmail/codex—0.1.33—
@agenticmail/core—0.9.43—
@agenticmail/openclaw—0.5.71—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 48× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-11 14:53 UTCEPSS rescore
  2. 2026-09-11 09:18 UTCEG score recompute
  3. 2026-09-10 09:35 UTCEPSS rescore
  4. 2026-09-09 11:46 UTCEG score recompute
  5. 2026-09-08 22:01 UTCEPSS rescore
  6. 2026-09-07 22:47 UTCEG score recompute
  7. 2026-09-07 16:01 UTCEPSS rescore
  8. 2026-09-06 13:47 UTCEPSS rescore
  9. 2026-09-05 21:04 UTCEG score recompute
  10. 2026-09-05 09:20 UTCEG score recompute
  11. 2026-09-04 05:07 UTCEPSS rescore
  12. 2026-09-02 14:12 UTCEPSS rescore
  13. 2026-09-02 01:02 UTCEG score recompute
  14. 2026-09-01 13:54 UTCEPSS rescore
  15. 2026-09-01 04:40 UTCEPSS rescore
  16. 2026-08-31 03:16 UTCEG score recompute
  17. 2026-08-30 19:17 UTCEPSS rescore
  18. 2026-08-30 02:28 UTCEG score recompute
  19. 2026-08-30 01:22 UTCEPSS rescore
  20. 2026-08-28 21:42 UTCEPSS rescore
  21. 2026-08-27 23:18 UTCEG score recompute
  22. 2026-08-27 14:25 UTCEPSS rescore
  23. 2026-08-26 21:41 UTCEG score recompute
  24. 2026-08-26 14:46 UTCEPSS rescore
  25. 2026-08-25 20:21 UTCEG score recompute
Show 74 more
  1. 2026-08-25 13:49 UTCEPSS rescore
  2. 2026-08-24 20:45 UTCEG score recompute
  3. 2026-08-23 09:12 UTCEG score recompute
  4. 2026-08-23 00:19 UTCEPSS rescore
  5. 2026-08-22 09:29 UTCEG score recompute
  6. 2026-08-21 23:49 UTCEPSS rescore
  7. 2026-08-21 10:00 UTCEG score recompute
  8. 2026-08-20 22:55 UTCEPSS rescore
  9. 2026-08-19 22:46 UTCEG score recompute
  10. 2026-08-19 17:04 UTCEPSS rescore
  11. 2026-08-18 21:49 UTCEG score recompute
  12. 2026-08-18 13:48 UTCEPSS rescore
  13. 2026-08-17 21:00 UTCEG score recompute
  14. 2026-08-17 13:47 UTCEPSS rescore
  15. 2026-08-16 20:49 UTCEG score recompute
  16. 2026-08-16 14:56 UTCEPSS rescore
  17. 2026-08-16 09:04 UTCEG score recompute
  18. 2026-08-16 02:14 UTCEPSS rescore
  19. 2026-08-15 09:36 UTCEG score recompute
  20. 2026-08-15 01:30 UTCEPSS rescore
  21. 2026-08-13 22:23 UTCEG score recompute
  22. 2026-08-13 22:00 UTCEPSS rescore
  23. 2026-08-12 22:55 UTCEG score recompute
  24. 2026-08-12 13:51 UTCEPSS rescore
  25. 2026-08-11 23:26 UTCEG score recompute
  26. 2026-08-11 11:42 UTCEG score recompute
  27. 2026-08-11 00:00 UTCEPSS rescore
  28. 2026-08-10 00:29 UTCEG score recompute
  29. 2026-08-09 13:46 UTCEPSS rescore
  30. 2026-08-09 01:01 UTCEG score recompute
  31. 2026-08-08 16:37 UTCEPSS rescore
  32. 2026-08-08 01:32 UTCEG score recompute
  33. 2026-08-06 14:19 UTCEG score recompute
  34. 2026-08-06 13:47 UTCEPSS rescore
  35. 2026-08-06 02:35 UTCEG score recompute
  36. 2026-08-05 19:17 UTCEPSS rescore
  37. 2026-08-05 00:38 UTCEG score recompute
  38. 2026-08-04 15:10 UTCEPSS rescore
  39. 2026-08-04 12:51 UTCEG score recompute
  40. 2026-08-04 10:39 UTCEPSS rescore
  41. 2026-08-03 12:16 UTCEG score recompute
  42. 2026-08-03 10:36 UTCEPSS rescore
  43. 2026-08-02 12:46 UTCEG score recompute
  44. 2026-08-02 02:27 UTCEPSS rescore
  45. 2026-08-01 13:16 UTCEG score recompute
  46. 2026-08-01 04:16 UTCEPSS rescore
  47. 2026-07-31 02:01 UTCEG score recompute
  48. 2026-07-30 16:28 UTCEPSS rescore
  49. 2026-07-30 14:15 UTCEG score recompute
  50. 2026-07-30 02:30 UTCEG score recompute
  51. 2026-07-30 01:30 UTCEPSS rescore
  52. 2026-07-30 01:30 UTCEPSS rescore
  53. 2026-07-29 02:58 UTCEG score recompute
  54. 2026-07-28 15:37 UTCEPSS rescore
  55. 2026-07-27 15:40 UTCEG score recompute
  56. 2026-07-27 14:14 UTCEPSS rescore
  57. 2026-07-26 16:11 UTCEG score recompute
  58. 2026-07-26 14:54 UTCEPSS rescore
  59. 2026-07-26 14:54 UTCEPSS rescore
  60. 2026-07-26 04:25 UTCEG score recompute
  61. 2026-07-25 14:18 UTCEPSS rescore
  62. 2026-07-25 14:18 UTCEPSS rescore
  63. 2026-07-24 14:18 UTCEPSS rescore
  64. 2026-07-24 14:18 UTCEPSS rescore
  65. 2026-07-23 14:18 UTCEPSS rescore
  66. 2026-07-23 14:18 UTCEPSS rescore
  67. 2026-07-23 03:20 UTCEG score recompute
  68. 2026-07-22 23:27 UTCEG score recompute
  69. 2026-07-22 14:08 UTCEPSS rescore
  70. 2026-07-22 14:08 UTCEPSS rescore
  71. 2026-07-21 15:25 UTCEPSS rescore
  72. 2026-07-20 22:42 UTCEG score recompute
  73. 2026-07-20 22:12 UTCEG score recompute
  74. 2026-07-20 22:12 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-57495?
CVE-2026-57495 is a high vulnerability published on July 20, 2026. AgenticMail gives AI agents real email addresses and phone numbers. In @agenticmail/claudecode prior to version 0.2.39, @agenticmail/codex prior to version 0.1.33, @agenticmail/core prior to version 0.9.43, and @agenticmail/openclaw prior to version 0.5.71, two inbound-mail handlers act on a…
When was CVE-2026-57495 disclosed?
CVE-2026-57495 was first published in the National Vulnerability Database on July 20, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-57495 actively exploited?
CVE-2026-57495 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 70.5% of all scored CVEs.
What is the CVSS score of CVE-2026-57495?
CVE-2026-57495 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2026-57495?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-57495, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-57495

Explore →

Is Your Infrastructure Affected by CVE-2026-57495?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs