CVE-2026-104611

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

GHSA-5xvg-86hf-5h5q ↗EUVD-2026-91579 ↗

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.
Tenda AC9 15.03.02.13
ETK-2026-351, permanent identifier
11d 02h 21msince last run
51mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+183h10m
0
+2h
+4h
+6h
+8h
+10h

description

Tenda AC9 15.03.02.13 is affected by a stack-based buffer overflow in a web-management POST handler. A remote attacker able to reach and submit requests to that handler may cause memory corruption; exposure depends on access to the device's management interface.

mitigation

Restrict the AC9 management interface to trusted administrative networks and disable remote administration where possible. Apply a vendor-provided firmware 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.
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.
0.49%41st percentile
agent run time
51m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-02 12: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

Contextual: an exploit technique exists, 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-10-02 12:15Z
    ghsa: trigger signal, started the run
  2. 2026-10-02 12:15Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-351",
  "cve_id": "CVE-2026-104611",
  "display_id": "CVE-2026-104611",
  "ghsa_id": "GHSA-5xvg-86hf-5h5q",
  "euvd_id": "EUVD-2026-91579",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Stack-based buffer overflow in Tenda AC9 POST handler",
  "summary": "Tenda AC9 15.03.02.13 is affected by a stack-based buffer overflow in a web-management POST handler. A remote attacker able to reach and submit requests to that handler may cause memory corruption; exposure depends on access to the device's management interface.",
  "mitigation": "Restrict the AC9 management interface to trusted administrative networks and disable remote administration where possible. Apply a vendor-provided firmware update when one becomes available.",
  "vendor": "Tenda",
  "product": "AC9",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "15.03.02.13"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "AC9",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 9.1,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H",
  "epss_score": 0.0049,
  "epss_percentile": 0.411,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 50.79428561666667,
  "t0_at": "2026-10-02T12:15:15.494000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-02T12:15:15.494000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-02T12:15:15.494000+00:00",
      "url": "https://github.com/advisories/GHSA-5xvg-86hf-5h5q"
    }
  }
}

published 2026-10-02 15:38Z
last change 2026-10-21 05:31Z

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.