CVE-2026-76504

validatedZero produced an exploit or a check.

GHSA-xqjc-v467-8fvf ↗EUVD-2026-89950 ↗

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).+6h36mkevAttacks confirmed in the real world.+3h55m
Cisco Catalyst SD-WAN Manager 18.3.6; 18.3.7; 18.3.8; 17.2.10; 18.3.6.1; 18.2.0; 18.4.3; 18.4.1; 17.2.8; 18.3.3.1; 18.4.0; 18.3.1; 17.2.6; 17.2.9; 18.3.4; 17.2.5; 18.3.1.1; 18.3.5; 18.4.0.1; 18.3.3; 17.2.7; 17.2.4; 18.3.0
CWE-177 Improper Handling of URL Encoding (Hex Encoding)
ETK-2026-114, permanent identifier
+2.3dTTV
11mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = cve.org publication
trigger signal (cve.org) +0dkev+0.2dpublic poc+0.3dcheck available+2.3dagent stopped
0
+1d
+2d

description

Cisco Catalyst SD-WAN Manager API session authentication can be bypassed because URI-encoded request paths are handled incorrectly. A remote attacker without credentials may obtain administrator-level API access if they can reach the affected management API.

mitigation

Restrict access to the SD-WAN Manager management API to trusted administrative networks and limit exposed API endpoints. Apply the vendor's update when available; no fixed version is recorded in the 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.
1.8%78th percentile
agent run time
11m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-09-30 13:04Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
+6h36m
Δ to kevAttacks confirmed in the real world.
+3h55m

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-09-30 00:00Z
  2. 2026-09-30 00:00Z
  3. 2026-09-30 13:04Z
    cve_org: trigger signal, started the run
  4. 2026-09-30 22:43Z
  5. 2026-10-01 10:33Z
    CISA Adds Exploited Cisco Catalyst SD-WAN Manager Auth Bypass to KEV
  6. 2026-10-02 00:27Z
    Cisco Warns of Attackers Exploiting Critical Authentication Bypass in SD-WAN Manager
  7. 2026-10-02 05:49Z
    Critical FortiMail Zero-Day Flaw Exploited in Attacks Allows Unauthenticated Arbitrary File Writes

this entry in the feed

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

{
  "etk_id": "ETK-2026-114",
  "cve_id": "CVE-2026-76504",
  "display_id": "CVE-2026-76504",
  "ghsa_id": "GHSA-xqjc-v467-8fvf",
  "euvd_id": "EUVD-2026-89950",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Authentication bypass in Cisco Catalyst SD-WAN Manager API",
  "summary": "Cisco Catalyst SD-WAN Manager API session authentication can be bypassed because URI-encoded request paths are handled incorrectly. A remote attacker without credentials may obtain administrator-level API access if they can reach the affected management API.",
  "mitigation": "Restrict access to the SD-WAN Manager management API to trusted administrative networks and limit exposed API endpoints. Apply the vendor's update when available; no fixed version is recorded in the advisory data.",
  "vendor": "Cisco",
  "product": "Cisco Catalyst SD-WAN Manager",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "18.3.6",
        "18.3.7",
        "18.3.8",
        "17.2.10",
        "18.3.6.1",
        "18.2.0",
        "18.4.3",
        "18.4.1",
        "17.2.8",
        "18.3.3.1",
        "18.4.0",
        "18.3.1",
        "17.2.6",
        "17.2.9",
        "18.3.4",
        "17.2.5",
        "18.3.1.1",
        "18.3.5",
        "18.4.0.1",
        "18.3.3",
        "17.2.7",
        "17.2.4",
        "18.3.0"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Cisco Catalyst SD-WAN Manager",
      "purl": null
    }
  ],
  "cwes": [
    177
  ],
  "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.0182,
  "epss_percentile": 0.7844,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": true,
  "check_confidence_basis": "assessed",
  "exploit": false,
  "pipeline_minutes": 10.795177183333333,
  "t0_at": "2026-09-30T13:04:32.095000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-02T19:19:48.971493+00:00",
      "days": 2.2606119964467593,
      "is_lower_bound": false,
      "measured_at": "2026-09-30T13:04:32.095000+00:00",
      "url": null
    },
    "kev": {
      "at": "2026-09-30T16:59:23.068800+00:00",
      "days": 0.16308997453703702,
      "is_lower_bound": false,
      "measured_at": "2026-09-30T13:04:32.095000+00:00",
      "precision": "exact",
      "url": "https://www.cisa.gov/known-exploited-vulnerabilities-catalog?search_api_fulltext=CVE-2026-76504"
    },
    "public_poc": {
      "at": "2026-09-30T19:40:15+00:00",
      "days": 0.2748021412037037,
      "is_lower_bound": false,
      "measured_at": "2026-09-30T13:04:32.095000+00:00",
      "url": "https://github.com/ShadowForge-Cyber/CVE-2026-76504-Proof-of-concept"
    },
    "trigger_signal": {
      "at": "2026-09-30T13:04:32.095000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-09-30T13:04:32.095000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-76504"
    }
  }
}

published 2026-09-30 14:04Z
last change 2026-10-21 07:48Z

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.