CVE-2026-116838

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

GHSA-jjjq-27hc-2q7x ↗EUVD-2026-110578 ↗

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.
Ubiquiti Inc airMAX M < 6.3.26
fixed in 6.3.26
CWE-352 Cross-Site Request Forgery (CSRF)
ETK-2026-2715Zero's internal tracking ID, independent of the CVE number., permanent identifier
1h 46msince last run
45mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+4h45m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

airMAX M devices before version 6.3.26 are affected by a cross-site request forgery issue that can result in command injection. An attacker must induce an authenticated user to visit an attacker-controlled web page.

mitigation

Upgrade airMAX M to version 6.3.26 or later. Until upgraded, restrict access to the device management interface and avoid using it from untrusted web sessions.

fixed in 6.3.26

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.
–
agent run time
45m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-27 00:48Z
Δ 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-10-27 00:48Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-2715",
  "cve_id": "CVE-2026-116838",
  "display_id": "CVE-2026-116838",
  "ghsa_id": "GHSA-jjjq-27hc-2q7x",
  "euvd_id": "EUVD-2026-110578",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Cross-site request forgery leading to command injection in airMAX M",
  "summary": "airMAX M devices before version 6.3.26 are affected by a cross-site request forgery issue that can result in command injection. An attacker must induce an authenticated user to visit an attacker-controlled web page.",
  "mitigation": "Upgrade airMAX M to version 6.3.26 or later. Until upgraded, restrict access to the device management interface and avoid using it from untrusted web sessions.",
  "vendor": "Ubiquiti Inc",
  "product": "airMAX M",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 6.3.26"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "6.3.26"
      ],
      "package_name": "airMAX M",
      "purl": null
    }
  ],
  "cwes": [
    352
  ],
  "cvss_score": 8.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 45.020155333333335,
  "t0_at": "2026-10-27T00:48:17.932000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-27T00:48:17.932000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-27T00:48:17.932000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-116838"
    }
  }
}

published 2026-10-27 01:46Z
last change 2026-10-27 07:10Z

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.