CVE-2026-41502
Unauth remote OOB read in bacnet-stack ReadPropertyMultiple can crash devices.
Is CVE-2026-41502 being exploited?
Not confirmed. CVE-2026-41502 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.40% probability of exploitation in the next 30 days.
How severe is CVE-2026-41502?
CVE-2026-41502 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-41502?
Yes. A fix has been recorded for CVE-2026-41502. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-41502 affect?
CVE-2026-41502 affects BACnet Stack <= 1.4.2, Embedded BACnet devices using bacnet-stack. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-41502?
Upgrade to bacnet-stack 1.4.3 or newer.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Crash/DoS on embedded BACnet devices via crafted RPM; potential remote compromise.
Immediate action required
- affected>= 1.4.0 and < 1.4.3
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.