CVE-2026-14911

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

GHSA-hxj2-954q-rw24 ↗EUVD-2026-94159 ↗

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.
ASUS Router 3.0.0.6.102 series
CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
ETK-2026-836, permanent identifier
10d 07h 05msince last run
12mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+103h16m
0
+2h
+4h
+6h
+8h
+10h

description

ASUS Router modules are affected by a cross-site scripting flaw. An attacker can act through an authenticated user's browser to access page data, alter router configuration, or disrupt service if that user visits a malicious URL.

mitigation

Apply the firmware update identified in the ASUS Security Advisory for the affected router model. Until updated, limit access to the router administration interface and advise administrative users not to open untrusted links while signed in.

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.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.32%23rd percentile
agent run time
12m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-07 02:13Z
Δ 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-07 02:13Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-836",
  "cve_id": "CVE-2026-14911",
  "display_id": "CVE-2026-14911",
  "ghsa_id": "GHSA-hxj2-954q-rw24",
  "euvd_id": "EUVD-2026-94159",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Cross-site scripting in ASUS Router modules",
  "summary": "ASUS Router modules are affected by a cross-site scripting flaw. An attacker can act through an authenticated user's browser to access page data, alter router configuration, or disrupt service if that user visits a malicious URL.",
  "mitigation": "Apply the firmware update identified in the ASUS Security Advisory for the affected router model. Until updated, limit access to the router administration interface and advise administrative users not to open untrusted links while signed in.",
  "vendor": "ASUS",
  "product": "Router",
  "affected": [
    {
      "affected_notes": [
        "3.0.0.6.102 series"
      ],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Router",
      "purl": null
    }
  ],
  "cwes": [
    79
  ],
  "cvss_score": 9.3,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:H",
  "epss_score": 0.0032,
  "epss_percentile": 0.2345,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 12.203724683333334,
  "t0_at": "2026-10-07T02:13:30.254000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-07T02:13:30.254000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-07T02:13:30.254000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-14911"
    }
  }
}

published 2026-10-07 03:07Z
last change 2026-10-21 16:09Z

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.