CVE-2026-76519

validatedZero produced an exploit or a check.

GHSA-6rc3-jwq8-jm3v ↗EUVD-2026-101420 ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).+3h59mkevAttacks confirmed in the real world.+3h20m
Cisco Secure Email 14.0.0-698; 13.5.1-277; 13.0.0-392; 14.2.0-620; 13.0.5-007; 13.5.4-038; 14.2.1-020; 14.3.0-032; 15.0.0-104; 15.0.1-030; 15.5.0-048; 15.5.1-055; 15.5.2-018; 16.0.0-050; 15.0.3-002; 16.0.0-054; 15.5.3-022; 16.0.1-017; 15.5.4-012; 16.0.4-016; 15.0.5-016; 16.0.2-112; 16.0.3-044
CWE-23 Relative Path Traversal
ETK-2026-1595Zero's internal tracking ID, independent of the CVE number., permanent identifier
+2h25mTTV
14mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
trigger signal (cve.org) +0hcheck available+2h25magent stoppedkev+3h20mpublic poc+3h59m
0
+1h
+2h
+3h

description

Cisco Secure Email Gateway deployments using the AMP file reputation service are affected by an attachment-handling flaw. A remote unauthenticated attacker may be able to send a malicious attachment that writes files to the appliance and can lead to commands running as root.

mitigation

Disable the AMP file reputation service where operationally feasible until vendor guidance is applied. No fixed version is recorded; monitor Cisco's advisory and update affected appliances when a corrected release is provided.

check
available
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
1.6%75th percentile
agent run time
14m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-14 16:07Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
+3h59m
Δ to kevAttacks confirmed in the real world.
+3h20m

outcome

Contextual check: a technique exists and was validated, but no deterministic check could cover this one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-14 00:00Z
  2. 2026-10-14 00:00Z
  3. 2026-10-14 16:07Z
    cve_org: trigger signal, started the run
  4. 2026-10-14 18:38Z
    Cisco Warns of Active Attacks Exploiting New Critical Secure Email Gateway Vulnerability
  5. 2026-10-15 06:17Z
    Palo Alto Networks Patches PAN-OS Authenticated RCE Flaw Amid Active Exploitation
  6. 2026-10-15 09:15Z

this entry in the feed

GET /api/v1/feed/CVE-2026-76519

{
  "etk_id": "ETK-2026-1595",
  "cve_id": "CVE-2026-76519",
  "display_id": "CVE-2026-76519",
  "ghsa_id": "GHSA-6rc3-jwq8-jm3v",
  "euvd_id": "EUVD-2026-101420",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Arbitrary file write in Cisco Secure Email AMP",
  "summary": "Cisco Secure Email Gateway deployments using the AMP file reputation service are affected by an attachment-handling flaw. A remote unauthenticated attacker may be able to send a malicious attachment that writes files to the appliance and can lead to commands running as root.",
  "mitigation": "Disable the AMP file reputation service where operationally feasible until vendor guidance is applied. No fixed version is recorded; monitor Cisco's advisory and update affected appliances when a corrected release is provided.",
  "vendor": "Cisco",
  "product": "Cisco Secure Email",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "14.0.0-698",
        "13.5.1-277",
        "13.0.0-392",
        "14.2.0-620",
        "13.0.5-007",
        "13.5.4-038",
        "14.2.1-020",
        "14.3.0-032",
        "15.0.0-104",
        "15.0.1-030",
        "15.5.0-048",
        "15.5.1-055",
        "15.5.2-018",
        "16.0.0-050",
        "15.0.3-002",
        "16.0.0-054",
        "15.5.3-022",
        "16.0.1-017",
        "15.5.4-012",
        "16.0.4-016",
        "15.0.5-016",
        "16.0.2-112",
        "16.0.3-044"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Cisco Secure Email",
      "purl": null
    }
  ],
  "cwes": [
    23
  ],
  "cvss_score": 9.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": 0.0157,
  "epss_percentile": 0.7507,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": true,
  "check_confidence_basis": "assessed",
  "exploit": false,
  "pipeline_minutes": 13.970223566666666,
  "t0_at": "2026-10-14T16:07:51.466000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-14T18:32:23.473061+00:00",
      "days": 0.10037045209490741,
      "is_lower_bound": false,
      "measured_at": "2026-10-14T16:07:51.466000+00:00",
      "url": null
    },
    "kev": {
      "at": "2026-10-14T19:27:28.010500+00:00",
      "days": 0.13861741319444446,
      "is_lower_bound": false,
      "measured_at": "2026-10-14T16:07:51.466000+00:00",
      "precision": "exact",
      "url": "https://www.cisa.gov/known-exploited-vulnerabilities-catalog?search_api_fulltext=CVE-2026-76519"
    },
    "public_poc": {
      "at": "2026-10-14T20:06:47+00:00",
      "days": 0.1659205324074074,
      "is_lower_bound": false,
      "measured_at": "2026-10-14T16:07:51.466000+00:00",
      "url": "https://github.com/Mickysalivan/CVE-2026-76519-Proof-of-concept"
    },
    "trigger_signal": {
      "at": "2026-10-14T16:07:51.466000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-14T16:07:51.466000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-76519"
    }
  }
}

published 2026-10-14 18:21Z
last change 2026-10-21 03:59Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.