CVE-2026-127275

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

GHSA-vwp2-w658-9xx8 ↗EUVD-2026-124804 ↗

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.
Linksys EA8100 1.0.3.216940
CWE-306 Missing Authentication for Critical Function
ETK-2026-4333Zero's internal tracking ID, independent of the CVE number., permanent identifier
3h 28msince last run
11mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+0h45m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Linksys EA8100 firmware 1.0.3.216940 is affected by missing authentication in JNAP API settings functions. A remote attacker may change remote-management or unsecured-Wi-Fi warning settings without authentication when the affected JNAP API is accessible.

mitigation

Disable or restrict remote management and JNAP access, and permit router administration only from trusted networks. No fixed firmware version is recorded; monitor Linksys guidance for an update.

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
11m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-12 23:45Z
Δ 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-11-12 23:45Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-4333",
  "cve_id": "CVE-2026-127275",
  "display_id": "CVE-2026-127275",
  "ghsa_id": "GHSA-vwp2-w658-9xx8",
  "euvd_id": "EUVD-2026-124804",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Missing authentication in Linksys EA8100 JNAP API",
  "summary": "Linksys EA8100 firmware 1.0.3.216940 is affected by missing authentication in JNAP API settings functions. A remote attacker may change remote-management or unsecured-Wi-Fi warning settings without authentication when the affected JNAP API is accessible.",
  "mitigation": "Disable or restrict remote management and JNAP access, and permit router administration only from trusted networks. No fixed firmware version is recorded; monitor Linksys guidance for an update.",
  "vendor": "Linksys",
  "product": "EA8100",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "1.0.3.216940"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "EA8100",
      "purl": null
    }
  ],
  "cwes": [
    306
  ],
  "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": 11.253660116666667,
  "t0_at": "2026-11-12T23:45:21.417000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-12T23:45:21.417000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-12T23:45:21.417000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-127275"
    }
  }
}

published 2026-11-13 00:19Z
last change 2026-11-13 03:49Z

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.