CVE-2026-76499

validatedZero produced an exploit or a check.

GHSA-4mrw-vr59-vgf2 ↗EUVD-2026-94471 ↗

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).kevAttacks confirmed in the real world.
Cisco Application Policy Infrastructure Controller (APIC) 5.2(1g); 5.2(2e); 5.2(2f); 5.2(2g); 5.2(2h); 5.2(3f); 5.2(3e); 5.2(3g); 5.2(4d); 5.2(4e); 5.2(5d); 5.2(5c); 6.0(1g); 5.2(5e); 5.2(4f); 5.2(6e); 6.0(1j); 5.2(6g); 5.2(7f); 5.2(7g); 6.0(2h); 5.2(6h); 5.2(4h); 5.2(8d); 6.0(2j); 5.2(8e); 6.0(3d); 6.0(3e); 5.2(8f); 5.2(8g); 5.3(1d); 5.2(8h); 6.0(4c); 5.3(2a); 5.2(8i); 6.0(5h); 5.3(2b); 6.0(3g); 6.0(5j); 5.3(2c); 6.0(6c); 6.1(1f); 6.0(7e); 5.3(2d); 6.0(8d); 6.0(8e); 6.1(2f); 6.0(8f); 5.3(2e); 6.1(2g); 5.3(2f); 6.0(9c); 6.1(3f); 6.0(9d); 6.0(6g); 6.0(6h); 6.0(8h); 6.1(3g); 6.1(4h); 6.0(9e); 6.1(5e); 6.2(1f); 6.2(1g); 6.0(9f); 6.2(2e)
CWE-707 Improper Neutralization
ETK-2026-893, permanent identifier
+1h04mTTV
7mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
trigger signal (cve.org) +0mcheck available+64magent stopped
0
+15min
+30min
+45min
+60min

description

Cisco Application Policy Infrastructure Controller (APIC) is affected by improper neutralization issues. The available advisory information does not specify the attacker impact or any access preconditions.

mitigation

Apply the applicable Cisco APIC software-hardening releases. No specific fixed version is recorded in the available advisory data.

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.
0.31%22nd percentile
agent run time
7m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-07 16:17Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

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-07 16:17Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-893",
  "cve_id": "CVE-2026-76499",
  "display_id": "CVE-2026-76499",
  "ghsa_id": "GHSA-4mrw-vr59-vgf2",
  "euvd_id": "EUVD-2026-94471",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Improper neutralization in Cisco APIC",
  "summary": "Cisco Application Policy Infrastructure Controller (APIC) is affected by improper neutralization issues. The available advisory information does not specify the attacker impact or any access preconditions.",
  "mitigation": "Apply the applicable Cisco APIC software-hardening releases. No specific fixed version is recorded in the available advisory data.",
  "vendor": "Cisco",
  "product": "Cisco Application Policy Infrastructure Controller (APIC)",
  "affected": [
    {
      "affected_notes": [
        "5.2(1g)",
        "5.2(2e)",
        "5.2(2f)",
        "5.2(2g)",
        "5.2(2h)",
        "5.2(3f)",
        "5.2(3e)",
        "5.2(3g)",
        "5.2(4d)",
        "5.2(4e)",
        "5.2(5d)",
        "5.2(5c)",
        "6.0(1g)",
        "5.2(5e)",
        "5.2(4f)",
        "5.2(6e)",
        "6.0(1j)",
        "5.2(6g)",
        "5.2(7f)",
        "5.2(7g)",
        "6.0(2h)",
        "5.2(6h)",
        "5.2(4h)",
        "5.2(8d)",
        "6.0(2j)",
        "5.2(8e)",
        "6.0(3d)",
        "6.0(3e)",
        "5.2(8f)",
        "5.2(8g)",
        "5.3(1d)",
        "5.2(8h)",
        "6.0(4c)",
        "5.3(2a)",
        "5.2(8i)",
        "6.0(5h)",
        "5.3(2b)",
        "6.0(3g)",
        "6.0(5j)",
        "5.3(2c)",
        "6.0(6c)",
        "6.1(1f)",
        "6.0(7e)",
        "5.3(2d)",
        "6.0(8d)",
        "6.0(8e)",
        "6.1(2f)",
        "6.0(8f)",
        "5.3(2e)",
        "6.1(2g)",
        "5.3(2f)",
        "6.0(9c)",
        "6.1(3f)",
        "6.0(9d)",
        "6.0(6g)",
        "6.0(6h)",
        "6.0(8h)",
        "6.1(3g)",
        "6.1(4h)",
        "6.0(9e)",
        "6.1(5e)",
        "6.2(1f)",
        "6.2(1g)",
        "6.0(9f)",
        "6.2(2e)"
      ],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Cisco Application Policy Infrastructure Controller (APIC)",
      "purl": null
    }
  ],
  "cwes": [
    707
  ],
  "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.0031,
  "epss_percentile": 0.2225,
  "epss_asof": "2026-10-21",
  "automation": "contextual",
  "check": true,
  "check_confidence_basis": "assessed",
  "exploit": false,
  "pipeline_minutes": 7.087679233333334,
  "t0_at": "2026-10-07T16:17:25.662000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-07T17:21:27.842267+00:00",
      "days": 0.0444696790162037,
      "is_lower_bound": false,
      "measured_at": "2026-10-07T16:17:25.662000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-10-07T16:17:25.662000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-07T16:17:25.662000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-76499"
    }
  }
}

published 2026-10-07 17:05Z
last change 2026-10-21 21:36Z

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.