CVE-2026-52788

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

GHSA-rf83-3rr5-v4mj ↗EUVD-2026-125533 ↗

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.
bacnet-stack < 1.6.0
fixed in 1.4.5, 1.5.1, 1.6.0
CWE-787 Out-of-bounds Write
ETK-2026-4404Zero's internal tracking ID, independent of the CVE number., permanent identifier
12h 36msince last run
20mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+1h10m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

BACnet Stack releases before 1.4.5, 1.5.1, and 1.6.0 mishandle WebSocket URI lists in BACnet/SC Address Resolution ACK messages. An attacker able to supply a malformed ACK message to the affected parser may cause memory corruption through out-of-bounds writes.

mitigation

Upgrade BACnet Stack to 1.4.5, 1.5.1, or 1.6.0. Until upgraded, restrict exposure of BACnet/SC messaging to trusted peers.

fixed in 1.4.5, 1.5.1, 1.6.0

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

this entry in the feed

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

{
  "etk_id": "ETK-2026-4404",
  "cve_id": "CVE-2026-52788",
  "display_id": "CVE-2026-52788",
  "ghsa_id": "GHSA-rf83-3rr5-v4mj",
  "euvd_id": "EUVD-2026-125533",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Out-of-bounds write in BACnet Stack BACnet/SC URL parser",
  "summary": "BACnet Stack releases before 1.4.5, 1.5.1, and 1.6.0 mishandle WebSocket URI lists in BACnet/SC Address Resolution ACK messages. An attacker able to supply a malformed ACK message to the affected parser may cause memory corruption through out-of-bounds writes.",
  "mitigation": "Upgrade BACnet Stack to 1.4.5, 1.5.1, or 1.6.0. Until upgraded, restrict exposure of BACnet/SC messaging to trusted peers.",
  "vendor": "bacnet-stack",
  "product": "bacnet-stack",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "< 1.6.0"
      ],
      "ecosystem": "other",
      "fixed_versions": [
        "1.4.5",
        "1.5.1",
        "1.6.0"
      ],
      "package_name": "bacnet-stack",
      "purl": null
    }
  ],
  "cwes": [
    787
  ],
  "cvss_score": 8.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/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": 20.025387916666666,
  "t0_at": "2026-11-13T15:56:05.655000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-13T15:56:05.655000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-13T15:56:05.655000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-52788"
    }
  }
}

published 2026-11-13 16:45Z
last change 2026-11-14 05:26Z

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.