CVE-2026-82391

validatedZero produced an exploit or a check.

GHSA-8jrg-wx88-g75j ↗EUVD-2026-123035 ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
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.
zephyrproject zephyr >= 4.0.0, < 4.3.2; >= 4.4.0, < 4.5.0
fixed in 4.3.2, 4.5.0
CWE-787 Out-of-bounds Write
ETK-2026-4107Zero's internal tracking ID, independent of the CVE number., permanent identifier
+1h13mTTV
41mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
trigger signal (cve.org) +0mcheck available+73magent stopped
0
+15min
+30min
+45min
+60min

description

Zephyr HTTP server configurations using HTTP/2 with static filesystem resources can corrupt memory while serving a static file. An unauthenticated remote client can trigger a device crash or hang and may be able to alter control data. The affected configuration requires the HTTP/2 server front end and static filesystem support.

mitigation

Upgrade Zephyr to 4.3.2 or 4.5.0, as appropriate for the maintained release line. Until upgraded, disable HTTP/2 or remove static filesystem HTTP resources from exposed server configurations.

fixed in 4.3.2, 4.5.0

check
available
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
41m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-10 22:07Z
Δ 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 check: a technique exists and was validated, 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-11-10 22:07Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-4107",
  "cve_id": "CVE-2026-82391",
  "display_id": "CVE-2026-82391",
  "ghsa_id": "GHSA-8jrg-wx88-g75j",
  "euvd_id": "EUVD-2026-123035",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Out-of-bounds write in Zephyr HTTP/2 static file handling",
  "summary": "Zephyr HTTP server configurations using HTTP/2 with static filesystem resources can corrupt memory while serving a static file. An unauthenticated remote client can trigger a device crash or hang and may be able to alter control data. The affected configuration requires the HTTP/2 server front end and static filesystem support.",
  "mitigation": "Upgrade Zephyr to 4.3.2 or 4.5.0, as appropriate for the maintained release line. Until upgraded, disable HTTP/2 or remove static filesystem HTTP resources from exposed server configurations.",
  "vendor": "zephyrproject",
  "product": "zephyr",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 4.0.0, < 4.3.2"
      ],
      "ecosystem": "other",
      "fixed_versions": [
        "4.3.2"
      ],
      "package_name": "zephyr",
      "purl": null
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 4.4.0, < 4.5.0"
      ],
      "ecosystem": "other",
      "fixed_versions": [
        "4.5.0"
      ],
      "package_name": "zephyr",
      "purl": null
    }
  ],
  "cwes": [
    787
  ],
  "cvss_score": 9.1,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": true,
  "check_confidence_basis": "assessed",
  "exploit": false,
  "pipeline_minutes": 40.968275033333335,
  "t0_at": "2026-11-10T22:07:39.047000+00:00",
  "signals": {
    "check": {
      "at": "2026-11-10T23:20:43.040642+00:00",
      "days": 0.05074066715277778,
      "is_lower_bound": false,
      "measured_at": "2026-11-10T22:07:39.047000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-11-10T22:07:39.047000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-10T22:07:39.047000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-82391"
    }
  }
}

published 2026-11-10 22:39Z
last change 2026-11-11 03: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.