CVE-2026-132141

validatingZero is analyzing and reversing it now.

GHSA-jj9q-m8rj-v848 ↗EUVD-2026-129229 ↗

no check availablenot proven exploitable
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.
DrayTek Vigor2960 1.5.1.0; 1.5.1.1; 1.5.1.2; 1.5.1.3; 1.5.1.4; 1.5.1.5; 1.5.1.6
ETK-2026-4869Zero's internal tracking ID, independent of the CVE number., permanent identifier
–running
startingcurrent stage
timeline
0 = cve.org publication
trigger signal (cve.org) +0h
0
+2h
+4h
+6h
+8h
+10h
+12h

description

DrayTek Vigor2960 devices running firmware 1.5.1.6 or earlier are affected by a stack-based buffer overflow in the Jsonstatus CGI handling. A remote attacker able to reach the device's management interface may trigger the flaw and potentially compromise device availability or operation.

Still under analysis: more detail becomes available as the pipeline runs.

mitigation

Upgrade affected Vigor2960 devices to firmware 1.5.1.7 or later. Restrict access to the management interface to trusted administrative networks until upgrades are complete.

check
building now
exploit
not yet
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.
–
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
–
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-18 21:15Z
Δ 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

Run in progress: no artifact yet.

source signals

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

  1. 2026-11-18 21:15Z
    ghsa: trigger signal, started the run
  2. 2026-11-18 21:15Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-4869",
  "cve_id": "CVE-2026-132141",
  "display_id": "CVE-2026-132141",
  "ghsa_id": "GHSA-jj9q-m8rj-v848",
  "euvd_id": "EUVD-2026-129229",
  "status": "in_pipeline",
  "anchor_state": "anchored",
  "title": "Stack buffer overflow in DrayTek Vigor2960 Jsonstatus",
  "summary": "DrayTek Vigor2960 devices running firmware 1.5.1.6 or earlier are affected by a stack-based buffer overflow in the Jsonstatus CGI handling. A remote attacker able to reach the device's management interface may trigger the flaw and potentially compromise device availability or operation.",
  "mitigation": "Upgrade affected Vigor2960 devices to firmware 1.5.1.7 or later. Restrict access to the management interface to trusted administrative networks until upgrades are complete.",
  "vendor": "DrayTek",
  "product": "Vigor2960",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "1.5.1.0",
        "1.5.1.1",
        "1.5.1.2",
        "1.5.1.3",
        "1.5.1.4",
        "1.5.1.5",
        "1.5.1.6"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Vigor2960",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 9.9,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": null,
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": null,
  "t0_at": "2026-11-18T21:15:13.882000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-18T21:15:13.882000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-18T21:15:13.882000+00:00",
      "url": "https://github.com/advisories/GHSA-jj9q-m8rj-v848"
    }
  }
}

published 2026-11-19 02:04Z
last change 2026-11-19 03:01Z

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.