CVE-2026-92853

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

GHSA-893m-9g4r-4992 ↗EUVD-2026-105133 ↗

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.
Eclipse Foundation Eclipse ThreadX - NetX Duo <= 6.5.1.202602
fixed in 6.5.2.202603
CWE-125 Out-of-bounds Read
ETK-2026-2191Zero's internal tracking ID, independent of the CVE number., permanent identifier
11h 48msince last run
16mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+1h50m
0
+4h
+6h
+8h
+10h
+12h

description

NetX Duo installations using NetX Secure TLS 1.3 certificate-message processing are affected. A remote peer can cause the parser to read beyond its packet buffer before authentication by submitting a malformed Certificate message.

mitigation

Upgrade NetX Duo to version 6.5.2.202603 or later. Until upgraded, reduce exposure by limiting untrusted access to TLS 1.3 endpoints using the affected stack.

fixed in 6.5.2.202603

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
16m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-20 15:10Z
Δ 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: an exploit technique exists, 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-10-20 15:10Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-2191",
  "cve_id": "CVE-2026-92853",
  "display_id": "CVE-2026-92853",
  "ghsa_id": "GHSA-893m-9g4r-4992",
  "euvd_id": "EUVD-2026-105133",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Out-of-bounds read in NetX Secure TLS 1.3 parsing",
  "summary": "NetX Duo installations using NetX Secure TLS 1.3 certificate-message processing are affected. A remote peer can cause the parser to read beyond its packet buffer before authentication by submitting a malformed Certificate message.",
  "mitigation": "Upgrade NetX Duo to version 6.5.2.202603 or later. Until upgraded, reduce exposure by limiting untrusted access to TLS 1.3 endpoints using the affected stack.",
  "vendor": "Eclipse Foundation",
  "product": "Eclipse ThreadX - NetX Duo",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "<= 6.5.1.202602"
      ],
      "ecosystem": "eclipse threadx",
      "fixed_versions": [
        "6.5.2.202603"
      ],
      "package_name": "NetX Duo",
      "purl": null
    }
  ],
  "cwes": [
    125
  ],
  "cvss_score": 8.7,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 16.49958438333333,
  "t0_at": "2026-10-20T15:10:08.102000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-20T15:10:08.102000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-20T15:10:08.102000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-92853"
    }
  }
}

published 2026-10-20 16:43Z
last change 2026-10-21 03:59Z

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.