What is the CVSS score of CVE-2025-66624?

CVE-2025-66624 has a CVSS 3.1 base score of 7.5 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. EPSS exploitation probability: 0.1%.

Is there a public PoC exploit available for CVE-2025-66624?

Yes, a public proof-of-concept exploit is available for CVE-2025-66624. Prioritise patching immediately. EPSS: 0.1%.

How to fix or mitigate CVE-2025-66624?

Within 24 hours: Identify all systems and applications using BACnet Protocol Stack library versions prior to 1.5.0.rc2; document inventory and assess business criticality. Within 7 days: Develop and test patch deployment plan in non-production environment; prioritize critical infrastructure and customer-facing systems. Within 30 days: Deploy vendor patch (v1.5.0.rc2 or later) across all affected systems; verify functionality post-patch and confirm vulnerability remediation through security scanning.

Bacnet Stack CVE-2025-66624

Q: Which versions of Bacnet Stack are affected by CVE-2025-66624?

A critical vulnerability in BACnet Protocol Stack library (CVE-2025-66624) allows remote attackers to trigger denial-of-service attacks against systems using affected versions prior to 1.5.0.rc2.. A patch is available.

EUVD-2025-201496 HIGH

Out-of-bounds Read (CWE-125)

2025-12-05 security-advisories@github.com

Buffer Overflow Information Disclosure Bacnet Stack Bacnetstack

7.5

CVSS 3.1 · GitHub Advisory

View

Vulnerability Assessment

Weakness	CWE CWE-125 OWASP Top 10:2025 A06:2021 - Vulnerable and Outdated Components ASVS 5.0 V15 - Secure Coding and Architecture Bounds checking, read limits MITRE ATT&CK 1 technique across 1 tactic: Collection The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. Sign in to read
Impact	Out-of-bounds reads can leak sensitive information from memory, while out-of-bounds writes can corrupt data or enable code execution. With a CVSS score of 7.5 (HIGH), this represents a significant risk.
Exploit ScenarioDerived	An attacker provides a crafted input that causes the application to read or write beyond buffer boundaries, potentially leaking memory contents or hijacking control flow.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).

Patch available 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 15, 2026

BACnet Protocol Stack library provides a BACnet application layer, network layer and media access (MAC) layer communications services. Prior to 1.5.0.rc2, The npdu_is_expected_reply function in src/bacnet/npdu.c indexes request_pdu[offset+2/3/5] and reply_pdu[offset+1/2/4] without verifying that those APDU bytes exist. bacnet_npdu_decode() can return offset == 2 for a 2-byte NPDU, so tiny PDUs pass the version check and then get read out of bounds. On ASan/MPU/strict builds this is an immediate crash (DoS). On unprotected builds it is undefined behavior and can mis-route replies; RCE is unlikely because only reads occur, but DoS is reliable.

Earlier versions of this analysis (1)

v1 Mar 15, 2026 - 17:08 CVSS 7.5

RemediationAI

A vendor patch is available — apply it immediately. Implement proper bounds checking on all array and buffer accesses. Use memory-safe languages or static analysis tools to detect OOB issues.

Affected VersionsENISA

bacnet-stack < 1.5.0.rc2

Affected Packages

euvd bacnet_stack fix: 1.5.0.rc2

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

An out-of-bounds memory access occurs when code reads from or writes to memory locations outside the intended buffer boundaries. This vulnerability is classified as Out-of-bounds Read (CWE-125).

Know when Bacnet Stack gets its next vulnerability

Watch products and get an email when something new is published
Check this CVE against your own stack and servers
Exploit and PoC references, threat intelligence from 22 sources

Continue with Google Continue with GitHub

No credit card · 7-day full trial

Severity by source

GitHub Advisory PRIMARY 7.5 HIGH

AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Primary rating from GitHub Advisory · only source for this CVE.

CVSS VectorGitHub Advisory

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

High

Lifecycle Timeline

Patch released

Mar 15, 2026 - 17:08 nvd

Patch available

PoC Detected

Feb 18, 2026 - 18:21 vuln.today

Public exploit code

CVE Published

Dec 05, 2025 - 19:15 nvd

HIGH 7.5

Executive ViewAI

Why It Matters

A critical vulnerability in BACnet Protocol Stack library (CVE-2025-66624) allows remote attackers to trigger denial-of-service attacks against systems using affected versions prior to 1.5.0.rc2. Organizations operating building automation, HVAC, or industrial control systems relying on BACnet protocol are at risk of service disruption. Immediate patching is required to prevent operational outages.

Business Impact: High

Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score

0.1%

Top 76% exploitable

Exploit

POC

Public exploit code exists

Data Quality

5 sources

Confidence: Medium

EUVD

NVD

CVE.org

EPSS

GitHub

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue

Severity HIGH

CISA KEV No

Public POC Yes

EPSS 0.1%

Patch available Yes

Active threat No

Deciding rule

HIGH severity (CVSS 7.0-8.9)

What every action level means

Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.

Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.

This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.

This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.

Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived

Out-of-Cycle

Exploitation· derived

Poc

System Exposure· derived

Open

Automatable· derived

Yes

Human Impact

High

Priority Score

Low Medium High Critical

KEV: 0

EPSS: 0

CVSS: +38

PoC: +20

Weaponized: 0

Threat intel: 0

Gov advisory: 0

Attack Technique

Buffer Overflow HIGH

A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.

Information Disclosure MEDIUM

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.