CVE-2026-95823

validatedZero produced an exploit or a check.

GHSA-5g8m-jj22-82f5 ↗EUVD-2026-128891 ↗

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 >= 2.3.0, < 4.3.2; >= 4.4.0, < 4.5.0
fixed in 4.3.2, 4.5.0
CWE-416 Use After Free
ETK-2026-4808Zero's internal tracking ID, independent of the CVE number., permanent identifier
+1h12mTTV
50mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
trigger signal (cve.org) +0mcheck available+72magent stopped
0
+15min
+30min
+45min
+60min

description

Zephyr TCP receive processing can mishandle fragmented TCP headers, causing receive-buffer leaks and potentially memory corruption. An unauthenticated remote attacker able to send traffic to a device with a listening TCP service may disrupt network reception; affected packet layouts require the TCP header to cross network-buffer boundaries.

mitigation

Update Zephyr to version 4.3.2 or 4.5.0, as appropriate for the deployed release branch. Until upgraded, reduce exposure by limiting untrusted access to TCP services.

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

this entry in the feed

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

{
  "etk_id": "ETK-2026-4808",
  "cve_id": "CVE-2026-95823",
  "display_id": "CVE-2026-95823",
  "ghsa_id": "GHSA-5g8m-jj22-82f5",
  "euvd_id": "EUVD-2026-128891",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Use-after-free in Zephyr TCP header processing",
  "summary": "Zephyr TCP receive processing can mishandle fragmented TCP headers, causing receive-buffer leaks and potentially memory corruption. An unauthenticated remote attacker able to send traffic to a device with a listening TCP service may disrupt network reception; affected packet layouts require the TCP header to cross network-buffer boundaries.",
  "mitigation": "Update Zephyr to version 4.3.2 or 4.5.0, as appropriate for the deployed release branch. Until upgraded, reduce exposure by limiting untrusted access to TCP services.",
  "vendor": "zephyrproject",
  "product": "zephyr",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 2.3.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": [
    416
  ],
  "cvss_score": 7.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": true,
  "check_confidence_basis": "assessed",
  "exploit": false,
  "pipeline_minutes": 50.453788233333334,
  "t0_at": "2026-11-18T14:23:00.179000+00:00",
  "signals": {
    "check": {
      "at": "2026-11-18T15:34:32.725054+00:00",
      "days": 0.04968224599537037,
      "is_lower_bound": false,
      "measured_at": "2026-11-18T14:23:00.179000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-11-18T14:23:00.179000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-18T14:23:00.179000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-95823"
    }
  }
}

published 2026-11-18 14:44Z
last change 2026-11-18 20:42Z

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.