CVE-2026-124059

waiting for further signalsZero needs more public information before it can validate it.

GHSA-cfx7-8946-rr3x ↗EUVD-2026-119326 ↗

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.
TOTOLINK CA300-PoE 6.2c.884
CWE-120 Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')
ETK-2026-3861Zero's internal tracking ID, independent of the CVE number., permanent identifier
2h 39msince last run
13mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+3h15m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

TOTOLINK CA300-PoE firmware 6.2c.884 has a buffer-overflow flaw in a web-management CGI handler. An authenticated remote attacker with access to the management interface could compromise confidentiality, integrity, or availability.

mitigation

Restrict the web-management interface to trusted administrators and isolate it from untrusted networks. Apply a vendor firmware update when available; no fixed version is recorded.

check
no
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.
yes, high privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
13m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-07 19:00Z
Δ 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, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

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

  1. 2026-11-07 19:00Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-3861",
  "cve_id": "CVE-2026-124059",
  "display_id": "CVE-2026-124059",
  "ghsa_id": "GHSA-cfx7-8946-rr3x",
  "euvd_id": "EUVD-2026-119326",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Buffer overflow in TOTOLINK CA300-PoE web management",
  "summary": "TOTOLINK CA300-PoE firmware 6.2c.884 has a buffer-overflow flaw in a web-management CGI handler. An authenticated remote attacker with access to the management interface could compromise confidentiality, integrity, or availability.",
  "mitigation": "Restrict the web-management interface to trusted administrators and isolate it from untrusted networks. Apply a vendor firmware update when available; no fixed version is recorded.",
  "vendor": "TOTOLINK",
  "product": "CA300-PoE",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "6.2c.884"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "CA300-PoE",
      "purl": null
    }
  ],
  "cwes": [
    120
  ],
  "cvss_score": 9.4,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:P",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 13.175568016666666,
  "t0_at": "2026-11-07T19:00:18.491000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-07T19:00:18.491000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-07T19:00:18.491000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-124059"
    }
  }
}

published 2026-11-07 19:43Z
last change 2026-11-08 00:08Z

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.