CVE-2026-41503
Unauthenticated over-read in ReadPropertyMultiple, causing device crash.
Is CVE-2026-41503 being exploited?
Not confirmed. CVE-2026-41503 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.41% probability of exploitation in the next 30 days.
How severe is CVE-2026-41503?
CVE-2026-41503 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-41503?
Yes. A fix has been recorded for CVE-2026-41503. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-41503 affect?
CVE-2026-41503 affects BACnet Stack <1.4.3, Embedded BACnet devices, BACnet/IP deployments with ReadPropertyMultiple. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-41503?
Upgrade to 1.4.3+; validate in staging
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote crash of embedded BACnet devices via crafted RPM; denial of service and potential memory corruption.
Patch when possible
- 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.