CVE-2026-76519

CRITICALPre-NVD 9.89.8
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score elevated to 9.8 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2026-10-14), indicating real-world exploitation has been confirmed by US federal agencies. A secondary CVSS source baseline 9.8 retained for reference (NVD's own analysis pending). Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: CISA Known Exploited Vulnerabilities catalog, EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this weekExploited in the wild

Also known asEUVD-2026-101420 (ENISA EUVD) · GHSA-6rc3-jwq8-jm3v (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictMitigate nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV) — the reason this is sooner than the SSVC decision on this page at low mission impact
CISA-KEV: ExploitedEPSS PROB: 2.2%CVSS: 9.8Exploit: No code on recordExposed services: Not assessed

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

A vulnerability in the Advanced Malware Protection (AMP) feature of Cisco Secure Email Gateway could allow an unauthenticated, remote attacker to write arbitrary files on the underlying operating system. This vulnerability is due to improper handling of email attachments when the file reputation service is enabled. An attacker could exploit this vulnerability by sending an email that contains a crafted attachment through an affected device. A successful exploit could allow the attacker to write arbitrary files and execute commands with root privileges on the underlying operating system.

CVSS v3
9.8
EG Score
9.8CRITICALhigh confidence
EG Risk
99
EG Risk 99/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation100% × 40%
Fixed at 100% for a CISA KEV listing: EchelonGraph's rule.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Attend at low mission impact; Act at medium or high.
Exploitation active (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Check the vendor's advisory for a fixed release; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation sooner than your normal schedule at low mission impact and as soon as possible at medium or high.
EPSS PROB
2.2%
EPSS %ILE
82nd
KEV
⚠ Exploited

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
2.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
CISA KEV and EG-KEV Tier 1 (exploited in the wild)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Act at medium mission impactAttend at low mission impact; Act at medium or high.CISA BOD 26-04: 3 days & forensic triage if the affected system is publicly exposed; 3 days & forensic triage if it is not.No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: this CVE is in CISA's KEV catalog, and CISA's required action for it, quoted below, applies whether or not a fix is released.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Attend at low mission impact; Act at medium or high.

No fix is confirmed yet. Check the vendor's advisory for a fixed release; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation sooner than your normal schedule at low mission impact and as soon as possible at medium or high.

Exploitation active (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days & forensic triage if the affected system is publicly exposed; 3 days & forensic triage if it is not.

No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: this CVE is in CISA's KEV catalog, and CISA's required action for it, quoted below, applies whether or not a fix is released.

The score's inputs: In CISA KEV yes (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

CISA required action“Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.”

Quoted verbatim from CISA's Known Exploited Vulnerabilities catalog. CISA directs it at US federal civilian executive branch agencies under Binding Operational Directive (BOD) 26-04, which replaced BOD 22-01 on 10 June 2026; it is not EchelonGraph's advice. CISA's notes: https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-esa-afw-zqYJkjxp · https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk · https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk · https://nvd.nist.gov/vuln/detail/CVE-2026-76519

Published

October 14, 2026

Last Modified

October 15, 2026

Advisory Details (2)

Auto-updated Oct 30, 2026
⚠️ Actively exploited (CISA KEV, CISA Vulnrichment). No fix on record yet. Sources: cisa.
CISA🔴 Active Exploitation

Known Exploited Vulnerabilities Catalog | CISA

Known Exploited Vulnerabilities Catalog | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.

https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-76519
Web page

Cisco Secure Email Gateway Arbitrary File Write Vulnerability

https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-esa-afw-zqYJkjxp

Vendor Advisories for CVE-2026-76519(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 18× in last 7d / 66× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-11-01 16:35 UTCEPSS rescoreEPSS 2.2% · 82nd percentile
  2. 2026-11-01 12:49 UTCEG score recompute
  3. 2026-11-01 12:49 UTCGHSA enrichmentGHSA-6rc3-jwq8-jm3v · GitHub severity CRITICAL · GitHub CVSS 9.8
  4. 2026-10-31 16:33 UTCEPSS rescoreEPSS 2.2% · 82nd percentile
  5. 2026-10-31 11:24 UTCEG score recompute
  6. 2026-10-31 11:24 UTCGHSA enrichmentGHSA-6rc3-jwq8-jm3v · GitHub severity CRITICAL · GitHub CVSS 9.8
  7. 2026-10-30 16:35 UTCEPSS rescoreEPSS 2.2% · 82nd percentile
  8. 2026-10-30 09:59 UTCEG score recompute
  9. 2026-10-30 09:59 UTCGHSA enrichmentGHSA-6rc3-jwq8-jm3v · GitHub severity CRITICAL · GitHub CVSS 9.8
  10. 2026-10-29 16:34 UTCEPSS rescoreEPSS 2.2% · 82nd percentile
  11. 2026-10-29 08:35 UTCEG score recompute
  12. 2026-10-29 08:35 UTCGHSA enrichmentGHSA-6rc3-jwq8-jm3v · GitHub severity CRITICAL · GitHub CVSS 9.8
  13. 2026-10-28 16:33 UTCEPSS rescoreEPSS 2.2% · 82nd percentile
  14. 2026-10-28 07:10 UTCEG score recompute
  15. 2026-10-28 07:10 UTCGHSA enrichmentGHSA-6rc3-jwq8-jm3v · GitHub severity CRITICAL · GitHub CVSS 9.8
  16. 2026-10-27 16:32 UTCEPSS rescoreEPSS 2.2% · 82nd percentile
  17. 2026-10-27 05:45 UTCEG score recompute
  18. 2026-10-27 05:45 UTCGHSA enrichmentGHSA-6rc3-jwq8-jm3v · GitHub severity CRITICAL · GitHub CVSS 9.8
  19. 2026-10-26 04:19 UTCEG score recompute
  20. 2026-10-26 04:19 UTCGHSA enrichmentGHSA-6rc3-jwq8-jm3v · GitHub severity CRITICAL · GitHub CVSS 9.8
  21. 2026-10-25 16:34 UTCEPSS rescoreEPSS 2.2% · 82nd percentile
  22. 2026-10-25 14:02 UTCEG score recompute
  23. 2026-10-25 02:53 UTCEG score recompute
  24. 2026-10-25 02:53 UTCGHSA enrichmentGHSA-6rc3-jwq8-jm3v · GitHub severity CRITICAL · GitHub CVSS 9.8
  25. 2026-10-24 16:33 UTCEPSS rescoreEPSS 1.6% · 75th percentile
Show 41 more
  1. 2026-10-24 01:29 UTCEG score recompute
  2. 2026-10-24 01:29 UTCGHSA enrichmentGHSA-6rc3-jwq8-jm3v · GitHub severity CRITICAL · GitHub CVSS 9.8
  3. 2026-10-23 16:32 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  4. 2026-10-23 00:04 UTCEG score recompute
  5. 2026-10-23 00:04 UTCGHSA enrichmentGHSA-6rc3-jwq8-jm3v · GitHub severity CRITICAL · GitHub CVSS 9.8
  6. 2026-10-22 16:35 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  7. 2026-10-21 22:38 UTCEG score recompute
  8. 2026-10-21 22:38 UTCGHSA enrichmentGHSA-6rc3-jwq8-jm3v · GitHub severity CRITICAL · GitHub CVSS 9.8
  9. 2026-10-21 16:33 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  10. 2026-10-20 21:14 UTCEG score recompute
  11. 2026-10-20 21:14 UTCGHSA enrichmentGHSA-6rc3-jwq8-jm3v · GitHub severity CRITICAL · GitHub CVSS 9.8
  12. 2026-10-20 16:33 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  13. 2026-10-19 19:49 UTCEG score recompute
  14. 2026-10-19 19:49 UTCGHSA enrichmentGHSA-6rc3-jwq8-jm3v · GitHub severity CRITICAL · GitHub CVSS 9.8
  15. 2026-10-19 16:33 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  16. 2026-10-18 18:23 UTCEG score recompute
  17. 2026-10-18 18:22 UTCGHSA enrichmentGHSA-6rc3-jwq8-jm3v · GitHub severity CRITICAL · GitHub CVSS 9.8
  18. 2026-10-18 16:32 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  19. 2026-10-18 03:12 UTCEG score recompute
  20. 2026-10-17 16:58 UTCEG score recompute
  21. 2026-10-17 16:58 UTCGHSA enrichmentGHSA-6rc3-jwq8-jm3v · GitHub severity CRITICAL · GitHub CVSS 9.8
  22. 2026-10-17 16:35 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  23. 2026-10-16 16:44 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  24. 2026-10-16 15:32 UTCEG score recompute
  25. 2026-10-16 15:32 UTCGHSA enrichmentGHSA-6rc3-jwq8-jm3v · GitHub severity CRITICAL · GitHub CVSS 9.8
  26. 2026-10-15 16:32 UTCEPSS rescoreEPSS 1.7% · 77th percentile
  27. 2026-10-15 14:07 UTCGHSA enrichmentGHSA-6rc3-jwq8-jm3v · GitHub severity CRITICAL · GitHub CVSS 9.8
  28. 2026-10-15 04:26 UTCEG score recompute
  29. 2026-10-15 04:26 UTCGHSA enrichmentGHSA-6rc3-jwq8-jm3v · GitHub severity CRITICAL · GitHub CVSS 9.8
  30. 2026-10-15 04:01 UTCEG score recompute
  31. 2026-10-15 04:01 UTCGHSA enrichmentGHSA-6rc3-jwq8-jm3v · GitHub severity CRITICAL · GitHub CVSS 9.8
  32. 2026-10-14 20:26 UTCEG score recompute
  33. 2026-10-14 20:26 UTCGHSA enrichmentGHSA-6rc3-jwq8-jm3v · GitHub severity CRITICAL · GitHub CVSS 9.8
  34. 2026-10-14 19:45 UTCEG score recompute
  35. 2026-10-14 19:44 UTCGHSA enrichmentGHSA-6rc3-jwq8-jm3v · GitHub severity CRITICAL · GitHub CVSS 9.8
  36. 2026-10-14 19:38 UTCEG score recompute
  37. 2026-10-14 19:37 UTCGHSA enrichmentGHSA-6rc3-jwq8-jm3v · GitHub severity CRITICAL · GitHub CVSS 9.8
  38. 2026-10-14 19:35 UTCCISA KEV update
  39. 2026-10-14 17:29 UTCEG score recompute
  40. 2026-10-14 16:34 UTCEG score recomputeFirst assessed: 9.8 CRITICAL
  41. 2026-10-14 16:29 UTCMITRE cvelistV5first tracked

Frequently asked(6)

What is CVE-2026-76519?
CVE-2026-76519 is a critical-severity vulnerability; its CVE record was published on October 14, 2026. A vulnerability in the Advanced Malware Protection (AMP) feature of Cisco Secure Email Gateway could allow an unauthenticated, remote attacker to write arbitrary files on the underlying operating system. This vulnerability is due to improper handling of email attachments when the file reputation…
When was the CVE record for CVE-2026-76519 published?
The CVE record for CVE-2026-76519 was published on October 14, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 15, 2026; the record at its source may have been updated since.
Is CVE-2026-76519 actively exploited?
Yes. CISA added CVE-2026-76519 to the Known Exploited Vulnerabilities catalog on October 14, 2026, affecting Cisco Secure Email Gateway. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate attention. No fix is confirmed yet. Check the vendor's advisory for a fixed release; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation.
What is the CVSS score of CVE-2026-76519?
CVE-2026-76519 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
Which products are affected by CVE-2026-76519?
CVE-2026-76519 affects Cisco Secure Email Gateway.
How do I remediate CVE-2026-76519?
No fix for CVE-2026-76519 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-76519 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-76519

Explore →

Is Your Infrastructure Affected by CVE-2026-76519?

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