CVE-2026-119756

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

GHSA-6g2f-6p9p-vvm8 ↗EUVD-2026-120125 ↗

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.
arendst Tasmota <= 16.0.0
CWE-805 Buffer Access with Incorrect Length Value
ETK-2026-3978Zero's internal tracking ID, independent of the CVE number., permanent identifier
1d 10h 28msince last run
2h 43mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+2h49m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Tasmota through 16.0.0 is affected by an out-of-bounds heap write while processing Device Groups UDP traffic. An unauthenticated attacker able to reach UDP port 4447 from the local network may corrupt device memory, causing a crash or potentially executing code.

mitigation

Update to a Tasmota build that includes commit e97e1e4. Until that is applied, restrict UDP port 4447 to trusted management and device networks.

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
2h 43m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-09 17:28Z
Δ 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-09 17:28Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-3978",
  "cve_id": "CVE-2026-119756",
  "display_id": "CVE-2026-119756",
  "ghsa_id": "GHSA-6g2f-6p9p-vvm8",
  "euvd_id": "EUVD-2026-120125",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Heap out-of-bounds write in Tasmota Device Groups handling",
  "summary": "Tasmota through 16.0.0 is affected by an out-of-bounds heap write while processing Device Groups UDP traffic. An unauthenticated attacker able to reach UDP port 4447 from the local network may corrupt device memory, causing a crash or potentially executing code.",
  "mitigation": "Update to a Tasmota build that includes commit e97e1e4. Until that is applied, restrict UDP port 4447 to trusted management and device networks.",
  "vendor": "arendst",
  "product": "Tasmota",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 16.0.0"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Tasmota",
      "purl": null
    }
  ],
  "cwes": [
    805
  ],
  "cvss_score": 9.3,
  "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:N/SI:N/SA:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 163.09973233333332,
  "t0_at": "2026-11-09T17:28:33.128000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-09T17:28:33.128000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-09T17:28:33.128000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-119756"
    }
  }
}

published 2026-11-09 17:34Z
last change 2026-11-11 05:45Z

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.