Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach controller web service over network
-
ExploitSend crafted multipart HTTP request
-
ExecutionTrigger stack buffer overflow in multipart parser
-
ImpactCrash web service / cause denial of service
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Stack buffer bounds checking
MITRE ATT&CK
1 technique across 1 tactic: Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires network reachability to the affected controller's HTTP web service and the ability to send a crafted multipart request; per CVSS PR:N/UI:N no authentication or user interaction is needed, and it works against default configurations. The practical limiting factor is exposure of the web management interface - these are OT building-automation controllers typically expected to reside on segmented/isolated networks, so risk is sharply reduced where the web service is not reachable from untrusted networks. Version-bounded products (APOGEE PXC Compact/Modular, TALON TC) are only affected below the listed fixed versions, whereas APOGEE MBC/MEC (PPC) variants are affected in all versions. |
| Impact | This is a credible operational-technology risk for exposed devices but not a confirmed widespread-exploitation emergency. The Siemens-provided CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N) describes a network-reachable, low-complexity, unauthenticated attack with no user interaction, which is why the base score is high at 8.7. However, impact is confined to availability (VA:H) with no confidentiality or integrity impact (VC:N/VI:N), so this is strictly a denial-of-service issue, not code execution. Notably, the CWE is CWE-121 (stack-based buffer overflow) and tags include 'Stack Overflow' and 'Buffer Overflow' - which often carry RCE potential - yet Siemens scored only availability impact; this signal conflict should be verified against the vendor advisory, as the practical ceiling may be a controller crash/reboot rather than memory-corruption-driven execution. No EPSS score, no CISA KEV listing, and no public POC are present in the provided data, so there is no evidence of active or automated exploitation; the real-world urgency therefore depends almost entirely on whether a given controller's web service is network-reachable. For OT/building-automation assets that are properly segmented, real risk is moderate despite the high CVSS; for internet- or flat-network-exposed controllers it is materially higher. |
| Exploit ScenarioDerived | An attacker with network access to an APOGEE/TALON controller's web service sends a malformed multipart HTTP request whose crafted input is not properly validated, overflowing a stack buffer and crashing the controller's web service. This can take the building-automation controller offline (loss of monitoring/control of HVAC or facility functions) without any credentials or user interaction. No public exploit code has been identified in the provided data, so exploitation would currently require an attacker to develop the request independently. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv2 – Oct 13, 2026
Denial of service in the embedded web service of Siemens APOGEE MBC/MEC (PPC), APOGEE PXC Compact/Modular, and TALON TC building-automation controllers, caused by improper validation of multipart input that can crash the service via a stack buffer overflow (CWE-121). An unauthenticated remote attacker with network reachability to the controller's HTTP interface (CVSS PR:N/UI:N) can send a crafted multipart request and take the web service down; the assessed impact is availability-only (C:N/I:N/A:H), with no confidentiality or integrity loss demonstrated. Exploitation is bounded by exposure: these are OT field panels normally expected on segmented building networks, and no public exploit code has been identified at time of analysis - this is a credible OT risk for internet- or IT-reachable controllers, not a confirmed widespread-exploitation emergency. All-version APOGEE MBC/MEC (PPC) models carry the highest residual risk because no fixed version is listed for them, whereas APOGEE PXC Compact/Modular (BACnet) and TALON TC are fixed at V3.5.7 and the P2 Ethernet PXC Compacts at V2.8.21.
Earlier versions of this analysis (1)
Stack-based buffer overflow in the web service of Siemens APOGEE and TALON building automation controllers allows an unauthenticated remote attacker to crash the device by sending a crafted multipart HTTP request, producing a denial of service (CVSS 3.1 base 7.5, AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H). Affected models include APOGEE PXC Compact and PXC Modular (BACnet builds below V3.5.7, P2 Ethernet builds below V2.8.21), TALON TC Compact and TC Modular (BACnet, below V3.5.7), plus APOGEE MBC (PPC) and MEC (PPC) in both BACnet and P2 Ethernet variants, which are listed as affected in all versions with no fixed build confirmed in the supplied data. No public exploit code has been identified at time of analysis and the issue is not listed as confirmed actively exploited (CISA KEV), but exploitation only requires network reachability to the controller's web interface, which makes segmentation the decisive risk control. There is no data disclosure or integrity impact - the outcome is limited to device crash/reboot and loss of availability of the affected controller.
RemediationAI
Apply the vendor firmware upgrades identified for the version-bounded families: APOGEE PXC Compact and PXC Modular (BACnet) and TALON TC Compact and TALON TC Modular (BACnet) should be updated to V3.5.7 or later, and APOGEE PXC Compact and PXC Modular (P2 Ethernet) should be updated to V2.8.21 or later; obtain the firmware and applicable update procedure from Siemens SSA-333035 (https://cert-portal.siemens.com/productcert/html/ssa-333035.html). For APOGEE MBC (PPC) and APOGEE MEC (PPC) in both BACnet and P2 Ethernet variants, the provided data lists all versions as affected and identifies no fixed version, so no vendor-released patch can be confirmed for those models at time of analysis - treat them as unpatchable in the interim and rely on compensating controls. Because the only confirmed vector is the controller's HTTP web service, the highest-value mitigation is to remove reachability to that service from untrusted networks: place the controllers behind a firewall or managed switch ACL that blocks inbound TCP to the web management ports (HTTP/HTTPS) from IT, guest, wireless, and internet segments, allowing access only from a dedicated engineering VLAN or jump host; the trade-off is that remote browser-based configuration and diagnostics must then be performed from inside that segment or over a VPN. Where remote engineering access is required, terminate it on a VPN with MFA rather than publishing the web interface, and rate-limit or deep-inspect multipart POST traffic at the boundary - noting that DPI for OT protocols can add latency and false positives on legitimate BACnet/IP or P2 traffic. Segment the building-automation network from business systems (per IEC 62443 zoning practices), monitor controller logs and network telemetry for repeated HTTP 5xx responses, service restarts, or malformed multipart requests as an early indicator of attempted exploitation, and maintain spare/recovery procedures for controllers that require a manual restart after a crash so that a successful DoS does not leave HVAC or access functions offline. Note that no public exploit code has been identified, so prioritization should be driven by actual exposure of the web interface rather than by imminent exploitation.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The defect is a stack-based buffer overflow (CWE-121) in the multipart/form-data parsing logic of the HTTP web service embedded in Siemens APOGEE and TALON field panels - the same web interface used for configuration and diagnostics on BACnet/IP and P2 Ethernet controller families. Because the parser fails to bound user-supplied multipart content before copying it onto the stack, an oversized or malformed part can overwrite stack memory and terminate the service process, producing a denial of service. Siemens rates this CVSS 4.0 base 8.7 (AV:N/AC:L/AT:N/PR:N/UI:N/VA:H), and the independent assessment maps it to CVSS 3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - both agree that the vector is network-reachable, unauthenticated, and availability-only, with no scope change and no demonstrated integrity or confidentiality impact. The affected CPE set confirms the scope is purely Siemens building-automation controllers: apogee_mbc_(ppc)_(bacnet), apogee_mbc_(ppc)_(p2_ethernet), apogee_mec_(ppc)_(bacnet), apogee_mec_(ppc)_(p2_ethernet), apogee_pxc_compact_(bacnet), apogee_pxc_compact_(p2_ethernet), apogee_pxc_modular_(bacnet), apogee_pxc_modular_(p2_ethernet), talon_tc_compact_(bacnet), and talon_tc_modular_(bacnet). Note that CVSS 4.0 N/A for VC/VI/SC/SI confirms the same availability-only picture; there is no evidence in the supplied data of remote code execution or persistence, so consequences should be scoped to loss of web management availability and the operational disruption of whatever supervisory functions depend on that interface.
Know when Apogee Mbc Ppc Bacnet 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
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
Web service is remotely reachable and the flaw triggers without auth or interaction (AV:N/AC:L/PR:N/UI:N); impact is limited to a service crash, so only A:H with C:N/I:N.
Primary rating from Vendor (siemens).
CVSS VectorVendor: siemens
Lifecycle Timeline
2DescriptionCVE.org
A vulnerability has been identified in APOGEE MBC (PPC) (BACnet) (All versions), APOGEE MBC (PPC) (P2 Ethernet) (All versions), APOGEE MEC (PPC) (BACnet) (All versions), APOGEE MEC (PPC) (P2 Ethernet) (All versions), APOGEE PXC Compact (BACnet) (All versions < V3.5.7), APOGEE PXC Compact (P2 Ethernet) (All versions < V2.8.21), APOGEE PXC Modular (BACnet) (All versions < V3.5.7), APOGEE PXC Modular (P2 Ethernet) (All versions < V2.8.21), TALON TC Compact (BACnet) (All versions < V3.5.7), TALON TC Modular (BACnet) (All versions < V3.5.7). The affected product web service does not properly validate user input in multipart handling. This could allow an unauthenticated remote attacker to cause a denial of service.
Executive ViewAI
Siemens APOGEE MBC/MEC (PPC), APOGEE PXC Compact/Modular, and TALON TC building-automation controllers are affected by a high-severity availability flaw in their embedded web service that an unauthenticated remote attacker with network reachability could use to take the service offline. The main organizational concern is disruption to building-automation monitoring and control for facilities relying on these panels, particularly where controllers are reachable from IT or internet-facing networks; no public exploit identified at time of analysis and no vendor-released patch identified at time of analysis. Leadership should prioritize exposure reduction and patching plans because these are OT field devices and the APOGEE MBC/MEC (PPC) line carries the highest residual risk with no fixed version listed.
No vendor-released patch identified at time of analysis; interim mitigations include isolating affected controllers on segmented OT/building-automation VLANs, blocking the embedded HTTP interface from untrusted networks, restricting management access via VPN and allowlisted hosts, disabling the web service where not required, monitoring for web-service crashes or reboots, and engaging Siemens for advisory-specific workarounds.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
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.
A stack-based buffer overflow occurs when a program writes more data to a buffer located on the stack than it was allocated to hold.
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
More in Apogee Mbc Ppc Bacnet
View allUnauthenticated remote attackers can read portions of device memory or cause a denial-of-service condition in Siemens AP
A stack-based buffer overflow in the web service upload-handling code of Siemens APOGEE and TALON building-automation co
Unauthenticated remote attackers can cause a denial of service on Siemens APOGEE MBC/MEC, PXC, and TALON building automa
EUVD-2026-98408
GHSA-rfwr-2392-4m8w
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB