Skip to main content
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Reach device network/protocol service
  2. Exploit
    Send crafted packet with out-of-bounds length
  3. Execution
    Trigger read beyond packet buffer
  4. Impact
    Leak adjacent memory contents

Vulnerability Assessment

Weakness
CWE
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.

Exploitation Conditions

No authentication and no user interaction are required (PR:N/UI:N), but exploitation requires network-level access to the affected device's packet-processing/communication service - these are Siemens Desigo PXC BACnet/building-automation controllers and Capital Embedded AR Classic (AUTOSAR) components typically deployed on segmented OT/building-management networks rather than internet-facing. The specific trigger is a malformed packet whose bounds are not validated before the packet data is accessed. Limiting factors: impact is confined to out-of-bounds memory READ with low confidentiality impact only (C:L, I:N, A:N) - no code execution, data modification, or denial of service - and reachability depends on network exposure of the device's protocol interface, which network segmentation of control systems normally restricts.

Impact

This is a moderate-severity out-of-bounds read (CWE-125) in Siemens Desigo PXC building-automation controllers and Capital Embedded AR Classic software. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N = 5.3) is internally consistent with the description: a remote, unauthenticated attacker can trigger reads past packet boundaries, yielding only a low-confidentiality impact with no integrity or availability effect. All exploitation signals point AWAY from urgent priority: no EPSS score was provided, the CVE is NOT listed in CISA KEV, and no public proof-of-concept is referenced - so there is no public exploit identified at the time of analysis. The low confidentiality-only impact means this is an information-disclosure/memory-leak primitive, not a code-execution or crash bug, which is why the score sits at Medium despite being network-reachable and unauthenticated. The realistic risk is therefore lower than the 'unauthenticated + network' framing suggests: it is most valuable as a reconnaissance or chaining primitive (e.g., leaking memory to defeat ASLR or expose secrets) rather than a standalone high-impact flaw. Key missing data: no EPSS, no SSVC decision record, no POC, and no vendor-stated automatable/technical-impact classification were supplied - these should be retrieved from the two Siemens ProductCERT advisories (SSA-055299, SSA-333035) to refine prioritization.

Exploit ScenarioDerived

An attacker with network reachability to an exposed Desigo PXC controller or an AR Classic communication stack sends a crafted protocol packet whose length/offset fields exceed the actual buffer. Because input bounds are not validated before the packet data is accessed, the device reads adjacent memory and may return it in a response, leaking fragments of process memory. No public exploit code is referenced, so an attacker would need to develop the packet themselves; the low complexity (AC:L) and lack of authentication (PR:N) make this straightforward once protocol access is obtained.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.4% exploitation probability (EPSS)

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

Alert me

AnalysisAIv1 – Oct 13, 2026

Out-of-bounds memory reads in Siemens Desigo PXC building-automation controllers (all versions >= V2.3) and Capital Embedded AR Classic (431-422 all versions; R20-11 versions before V2303) allow an unauthenticated, remote attacker who can reach the device's packet-processing/communication service to read memory outside the intended packet boundaries by sending a malformed packet. Per the assessed CVSS 3.1 vector AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N (score 5.3), the impact is limited to low confidentiality loss - no integrity or availability impact, and no code execution - because the flaw is a pure out-of-bounds read (CWE-125). There is no public exploit identified at time of analysis and no CISA KEV listing; the practical risk is governed by network exposure of these typically segmented OT/building-management interfaces.

RemediationAI

The primary action is to apply the fixed firmware/software releases documented by Siemens in advisories SSA-055299 (https://cert-portal.siemens.com/productcert/html/ssa-055299.html) and SSA-333035 (https://cert-portal.siemens.com/productcert/html/ssa-333035.html); for Capital Embedded AR Classic R20-11 the affected range is stated as all versions before V2303, indicating V2303 as the baseline to update to, while Capital Embedded AR Classic 431-422 and Desigo PXC controllers at V2.3 or later should be moved to the corrected release specified by the vendor for each model. Because patch status and exact fixed versions are not confirmed in the provided data, verify the current patch level against those advisories rather than assuming a build is remediated. Compensating controls, if immediate update is not possible: restrict network access to the controllers' protocol/packet-processing interfaces by placing them on isolated building-management/OT VLANs and blocking the relevant automation protocol ports (for example BACnet/IP UDP 47808 and any vendor-specific management ports) at the IT/OT boundary, allowing only known engineering workstations - the trade-off is reduced remote manageability and the need to maintain firewall rule hygiene; disable or firewall unused network services on the controllers to shrink the attack surface, accepting that some diagnostics functions may become unavailable; and monitor for anomalous or malformed traffic to the controllers. Note that this issue is an information-disclosure read only, so segmentation and access control reduce exposure but do not modify the low-confidentiality impact once an attacker has network reachability; there is no public exploit code identified that would justify emergency-only measures beyond normal OT patch prioritization.

Affected VersionsENISA

Capital Embedded AR Classic 431-422 0 <*
Desigo PXC36.1-E.D V2.3 <*
Desigo PXC00-E.D V2.3 <*
Desigo PXC128-U V2.3 <*
Capital Embedded AR Classic R20-11 0 <V2303
Desigo PXC64-U V2.3 <*
Desigo PXC12-E.D V2.3 <*
Desigo PXC22.1-E.D V2.3 <*
Desigo PXC50-E.D V2.3 <*
Desigo PXM20-E V2.3 <*
Desigo PXC001-E.D V2.3 <*
Desigo PXC200-E.D V2.3 <*
Desigo PXC100-E.D V2.3 <*
Desigo PXC22-E.D V2.3 <*
Desigo PXC00-U V2.3 <*

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 CWE-125 out-of-bounds read: the affected code fails to validate input bounds before accessing packet data, so a crafted packet with inconsistent length/offset fields causes reads past the end of the intended buffer. The underlying components are AUTOSAR Classic-based embedded software (Capital Embedded AR Classic) that is also deployed in Siemens Desigo PXC automation controllers (PXC00/PXC001/PXC100/PXC12/PXC128/PXC200/PXC22/PXC22.1/PXC36.1/PXC50/PXC64 and PXM20-E), which handle building-automation protocol traffic such as BACnet. CPE data confirms the affected stack spans both the standalone Capital Embedded AR Classic product (cpe:2.3:a:siemens:capital_embedded_ar_classic_431-422, capital_embedded_ar_classic_r20-11) and each Desigo PXC controller model. From a memory-safety standpoint, an OOB read of this class can leak adjacent memory contents (potentially including pointers or configuration data) but by itself does not corrupt memory, so the assessed consequence is information disclosure only. Exploitation requires network-level reachability of the device's packet-processing interface; authentication and user interaction are not required (PR:N/UI:N), but the vulnerable controllers are normally deployed on segmented BACnet/building-management networks rather than the public internet.

Know when Capital Embedded Ar Classic 431 422 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

Vendor (siemens) PRIMARY 6.9 MEDIUM
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
vuln.today AI 5.3 MEDIUM

Crafted packet is network-deliverable with low complexity and no auth or interaction (AV:N/AC:L/PR:N/UI:N); an out-of-bounds read leaks memory giving limited confidentiality impact only (C:L/I:N/A:N).

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (siemens).

CVSS VectorVendor: siemens

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
Low
Vulnerable system: Integrity
None
Vulnerable system: Availability
None
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

1
CVSS changed
Oct 13, 2026 - 10:22 NVD
5.3 (MEDIUM) 6.9 (MEDIUM)

DescriptionCVE.org

A vulnerability has been identified in Capital Embedded AR Classic 431-422 (All versions), Capital Embedded AR Classic R20-11 (All versions < V2303), Desigo PXC00-E.D (All versions >= V2.3), Desigo PXC00-U (All versions >= V2.3), Desigo PXC001-E.D (All versions >= V2.3), Desigo PXC100-E.D (All versions >= V2.3), Desigo PXC12-E.D (All versions >= V2.3), Desigo PXC128-U (All versions >= V2.3), Desigo PXC200-E.D (All versions >= V2.3), Desigo PXC22-E.D (All versions >= V2.3), Desigo PXC22.1-E.D (All versions >= V2.3), Desigo PXC36.1-E.D (All versions >= V2.3), Desigo PXC50-E.D (All versions >= V2.3), Desigo PXC64-U (All versions >= V2.3), Desigo PXM20-E (All versions >= V2.3). The affected product does not properly validate input bounds before accessing packet data. This could allow an unauthenticated remote attacker to trigger memory reads outside the intended packet boundaries.

Threat Intelligence Overview

EPSS Score
0.4%
Top 65% exploitable
Prevalence
Low
niche building-automation controllers and embedded AUTOSAR software, industry-specific OT footprint
Social Media
1
Sightings
Data Quality
5 sources
Confidence: Medium

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 MEDIUM
CISA KEV No
Public POC No
EPSS 0.4%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.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
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

34
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +34
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

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.

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

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy