CVE-2026-116508

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

GHSA-5vj6-9qxv-4h93 ↗EUVD-2026-110471 ↗

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 A950RG 4.1.2cu.5268_B20221104
CWE-121 Stack-based Buffer Overflow
ETK-2026-2696Zero's internal tracking ID, independent of the CVE number., permanent identifier
7h 00msince last run
16mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+0h34m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

TOTOLINK A950RG devices running firmware 4.1.2cu.5268_B20221104 are affected by a stack-based buffer overflow in the Device-Information CGI. A remote attacker who can reach the affected web endpoint may be able to trigger the flaw.

mitigation

Restrict network access to the device web interface to trusted administrative networks and disable or isolate it from untrusted networks. No fixed firmware version is recorded; apply a vendor-provided update when one becomes available.

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.
–
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.
–
agent run time
16m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-26 21:30Z
Δ 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

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

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

  1. 2026-10-26 21:30Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-2696",
  "cve_id": "CVE-2026-116508",
  "display_id": "CVE-2026-116508",
  "ghsa_id": "GHSA-5vj6-9qxv-4h93",
  "euvd_id": "EUVD-2026-110471",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Stack-based buffer overflow in TOTOLINK A950RG Device-Information CGI",
  "summary": "TOTOLINK A950RG devices running firmware 4.1.2cu.5268_B20221104 are affected by a stack-based buffer overflow in the Device-Information CGI. A remote attacker who can reach the affected web endpoint may be able to trigger the flaw.",
  "mitigation": "Restrict network access to the device web interface to trusted administrative networks and disable or isolate it from untrusted networks. No fixed firmware version is recorded; apply a vendor-provided update when one becomes available.",
  "vendor": "TOTOLINK",
  "product": "A950RG",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "4.1.2cu.5268_B20221104"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "A950RG",
      "purl": null
    }
  ],
  "cwes": [
    121
  ],
  "cvss_score": 10,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/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": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 16.45833685,
  "t0_at": "2026-10-26T21:30:18.376000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-26T21:30:18.376000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-26T21:30:18.376000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-116508"
    }
  }
}

published 2026-10-26 21:48Z
last change 2026-10-27 02:22Z

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.