CVE-2026-20133 Google Chronicle · YARA-L

Detect Cisco Catalyst SD-WAN Manager Sensitive Information Exposure (CVE-2026-20133) in Google Chronicle

Detects exploitation attempts targeting CVE-2026-20133, a CWE-200 information disclosure vulnerability in Cisco Catalyst SD-WAN Manager that allows unauthorized actors to access sensitive configuration and credential data. This vulnerability is actively exploited in the wild (CISA KEV) and may be leveraged to pivot into SD-WAN infrastructure.

MITRE ATT&CK

Tactic
Credential Access Discovery Collection

YARA-L Detection Query

Google Chronicle (YARA-L)
yaral
rule cve_2026_20133_sdwan_info_disclosure {
  meta:
    author = "df00tech"
    description = "Detects exploitation of CVE-2026-20133 Cisco SD-WAN Manager information disclosure"
    severity = "CRITICAL"
    priority = "HIGH"
    cve = "CVE-2026-20133"

  events:
    $req.metadata.event_type = "NETWORK_HTTP"
    $req.network.http.method = /GET|POST/
    $req.network.http.response_code = /^(200|201|206)$/
    $req.target.port in (443, 8443, 8080)
    $req.network.http.request_url = /\/dataservice\/|\/auditlog|\/device\/config|\/template\/|\/setting\/configuration|\/admin\/user/
    $src_ip = $req.principal.ip

  match:
    $src_ip over 10m

  condition:
    #req > 5
}
critical severity medium confidence

Chronicle YARAL rule that identifies repeated access to Cisco SD-WAN Manager sensitive REST API paths from a single IP within a 10-minute window. Targets patterns consistent with automated information harvesting as seen in CVE-2026-20133 exploitation.

Data Sources

Google Chronicle UDM HTTP eventsCisco SD-WAN Manager logs ingested via Chronicle forwarder

Required Tables

network_httpudm_events

False Positives & Tuning

  • Legitimate vManage API consumers making burst requests during configuration changes
  • Authorized third-party SD-WAN management platforms querying device templates
  • Health check agents polling multiple SD-WAN configuration endpoints
  • Cisco Crosswork or vAnalytics services accessing vManage data APIs

Other platforms for CVE-2026-20133


Testing Methodology

Validate this detection against 3 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are available with Pro.

  1. Test 1Unauthenticated SD-WAN Manager Device Config Enumeration

    Expected signal: HTTP GET requests to SD-WAN Manager management port (8443) for paths /dataservice/device, /dataservice/device/config, and /dataservice/admin/user from the test host IP. Response codes may be 200 (vulnerable) or 401/403 (patched/mitigated).

  2. Test 2SD-WAN Manager Template and Credential Harvest Simulation

    Expected signal: File creation events in /tmp/sdwan_harvest_test alongside network connections to vManage port 8443. Curl process making multiple sequential HTTP GET requests to /dataservice/template/device, /dataservice/setting/configuration, and /dataservice/auditlog.

  3. Test 3Automated SD-WAN Manager API Endpoint Enumeration with Token Extraction

    Expected signal: Rapid sequential HTTP GET requests (9 requests within ~5 seconds with 0.5s delay) to multiple /dataservice/ subpaths from a single source IP. HTTP status codes logged for each endpoint. Process: bash script executing curl in a loop.

Unlock Pro Content

Get the full detection package for CVE-2026-20133 including response playbook, investigation guide, and atomic red team tests.

Response PlaybookInvestigation GuideHunting QueriesAtomic Red Team TestsTuning Guidance

Related Detections