{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-26264 exists.","fix":"No fix has been published for CVE-2026-26264 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-26264 is a high-severity vulnerability in bacnet-stack, published on 13 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-26264 and fix it if it is affected.\n\nWhat it is: CVE-2026-26264 is a high-severity vulnerability in bacnet-stack, published on 13 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-26264 exists.\n\nAffected product: bacnet-stack. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-26264/ (Markdown: https://insights.sbomify.com/CVE-2026-26264/index.md)","id":"CVE-2026-26264","markdown":"https://insights.sbomify.com/CVE-2026-26264/index.md","name":"CVE-2026-26264","record":{"aliases":["GHSA-phjh-v45p-gmjj"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"BACnet protocol stack","requires_auth":"none","summary":"A malformed BACnet WriteProperty request causes an integer underflow leading to an out-of-bounds read and crash, requiring an upgrade to the BACnet Stack library.","user_interaction":"not_required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"bacnet_stack","vendor":"bacnetstack"}],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:H/SC:N/SI:N/SA:N/E:P","version":"4.0"},"cwes":[{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"BACnet Stack is a BACnet open source protocol stack C library for embedded systems. Prior to 1.5.0rc4 and 1.4.3rc2, a malformed WriteProperty request can trigger a length underflow in the BACnet stack, leading to an out‑of‑bounds read and a crash (DoS). The issue is in wp.c within wp_decode_service_request. When decoding the optional priority context tag, the code passes apdu_len - apdu_size to bacnet_unsigned_context_decode without validating that apdu_size \u003c= apdu_len. If a truncated APDU reaches this path, apdu_len - apdu_size underflows, resulting in a large size being used for decoding and an out‑of‑bounds read. This vulnerability is fixed in 1.5.0rc4 and 1.4.3rc2.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"BACnet Stack WriteProperty decoding length underflow leads to OOB read and crash","id":"CVE-2026-26264","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"integer_overflow","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Discourse has IDOR vulnerability in the directory items endpoint","id":"CVE-2026-26265"},"packages":[],"prev":{"headline":"GLPI has an Unauthenticated SQL Injection via Search engine","id":"CVE-2026-26263"},"products":["bacnet-stack"],"published":"2026-02-13","related":[{"cvss_score":9.1,"headline":"Memory corruption in n/a","id":"CVE-2023-51773","kev_date_added":null,"published":"2023-12-25"},{"cvss_score":8.7,"headline":"BACnet Stack: Out-of-Bounds Read in WritePropertyMultiple Decoder via Deprecated Tag Parser","id":"CVE-2026-41475","kev_date_added":null,"published":"2026-04-24"},{"cvss_score":8.7,"headline":"BACnet Stack: Off-by-One Out-of-Bounds Read in ReadPropertyMultiple Object ID Decoder","id":"CVE-2026-41502","kev_date_added":null,"published":"2026-04-24"},{"cvss_score":8.7,"headline":"BACnet Stack: Out-of-Bounds Read in ReadPropertyMultiple Property Decoder via Deprecated Tag Parser","id":"CVE-2026-41503","kev_date_added":null,"published":"2026-04-24"},{"cvss_score":7.5,"headline":"BACnet Stack Improperly Limits Pathnames to a Restricted Directory","id":"CVE-2026-21878","kev_date_added":null,"published":"2026-02-13"},{"cvss_score":7.5,"headline":"BACnet-stack MS/TP reply matcher OOB read","id":"CVE-2025-66624","kev_date_added":null,"published":"2025-12-05"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-02-13","vendors":["bacnet-stack"]},"summary":"A malformed BACnet WriteProperty request causes an integer underflow leading to an out-of-bounds read and crash, requiring an upgrade to the BACnet Stack library.","url":"https://insights.sbomify.com/CVE-2026-26264/"}