Skip to main content

Keil MDK-Middleware CVE-2026-115678

| EUVDEUVD-2026-109919 MEDIUM
Signed to Unsigned Conversion Error (CWE-195)
2026-10-26 Arm GHSA-2rr6-m9fm-xwm8
5.3
CVSS 3.1 · Vendor: Arm
View

Attack ChainAIDerived

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

  1. Access
    Reach device SNMP service on network
  2. Exploit
    Send crafted SNMP message
  3. Execution
    Trigger out-of-bounds read in SNMP parser
  4. Impact
    Degrade or crash service availability

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Signed/unsigned conversion safety
Exploitation Conditions

Exploitation requires that the device firmware be built on Arm Keil MDK-Middleware 8.0.0-8.3.0 with the SNMP component compiled in, enabled, and reachable by the attacker over the network (typically SNMP on UDP 161). The flaw is reached during SNMP processing prior to authentication (PR:N), so no credentials or user interaction are needed once the service is exposed. Limiting factors: only devices that actually deploy and expose this SNMP stack are affected, so devices without SNMP enabled or segmented off untrusted networks are not exploitable; the realistic consequence is availability degradation (A:L), not confidentiality or integrity loss. The specific trigger mechanism beyond 'out-of-bounds read in SNMP processing' is not described in the available sources.

Impact

This is a medium-severity (CVSS 5.3) issue whose signals are internally consistent but point to a limited, denial-of-service-class impact rather than a top-tier emergency. The CVSS vector (AV:N/AC:L/PR:N/UI:N/S:U) indicates a network-reachable, low-complexity, unauthenticated trigger, which is why the pre-authentication framing in the description matches PR:N. However, the impact metrics are C:N/I:N/A:L - only a low availability impact, with no confidentiality or integrity effect. This is notable because an 'out-of-bounds read' often implies potential memory disclosure (a confidentiality concern), yet the scored vector claims no confidentiality impact; this apparent tension between the 'OOB read' description and C:N should be verified with Arm, as it affects whether the real risk is a crash/DoS or also information leakage. SSVC reinforces a measured posture: Exploitation=none (no observed exploitation), Automatable=yes (SNMP is scriptable and network-facing), Technical Impact=partial. There is no CISA KEV listing and no public exploit identified, and no EPSS score was provided in the input, so probabilistic exploitation likelihood cannot be quantified here. Consistent with the vuln.today Decision label of 'this_month' (not act_now/emergency), this is a real but non-urgent priority: schedule remediation within the normal monthly cycle, prioritizing internet- or untrusted-network-facing embedded devices that expose the MDK-Middleware SNMP service.

Exploit ScenarioDerived

An attacker who can reach the SNMP service of an embedded device built on Arm Keil MDK-Middleware (8.0.0-8.3.0) sends a crafted SNMP message to UDP 161 that is parsed before any authentication, triggering an out-of-bounds read. Because the CVSS impact is availability-only (A:L), the realistic outcome is a crash or disruption of the SNMP/network stack on the device rather than code execution or data theft. No public exploit code or PoC is identified in the available sources; exploitation is low-complexity and automatable given network reach to the SNMP endpoint.

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 26, 2026

A pre-authentication out-of-bounds read in the SNMP component of Arm Keil MDK-Middleware 8.0.0 through 8.3.0 lets a remote, unauthenticated attacker reach SNMP parsing code before any credential check and read past the bounds of an internal buffer, with the assessed impact limited to availability (CVSS 5.3, AV:N/AC:L/PR:N/UI:N/C:N/I:N/A:L). Only devices whose firmware is built on the affected middleware with the SNMP component compiled in, enabled and network-reachable (typically SNMP on UDP 161) are exposed; devices that do not ship or expose this stack are not exploitable. Exploitation has not been observed (CISA SSVC Exploitation: none) and no public exploit was identified at time of analysis, so this is a medium-severity denial-of-service-class issue rather than an emergency, though the automatable nature of the flaw warrants patching within the vendor's normal cycle.

RemediationAI

The supplied data does not include a fixed release version, so no vendor-released patch version can be cited here; consult the Arm advisory at https://support.arm.com/documentation/112560 to identify the corrected MDK-Middleware release, then rebuild device firmware against it and reflash affected units, since the flaw lives in statically linked middleware rather than in a patchable host service. Because fielded devices often cannot be reflashed quickly, the effective interim controls are deployment-level: remove or disable the SNMP component in the Network Component build configuration so the parsing code is not linked into the image at all (trade-off: SNMP-based monitoring of those devices stops working and requires alternative telemetry), block or restrict UDP 161 to a small set of trusted management hosts at the network boundary or on the device's own filtering layer (trade-off: it does not remove the flaw and is bypassed if an attacker gains a position on the management segment), and keep affected devices off untrusted or internet-facing networks until rebuilt firmware is deployed (trade-off: limits remote management reachability and may require architectural changes for remote sites).

Affected VersionsENISA

MDK-Middleware 8.0.0 ≤8.3.0

Affected Packages

euvd mdk_middleware no fix

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

Arm Keil MDK-Middleware is the embedded software component bundle shipped for Cortex-M microcontroller development, comprising an RTOS, file system, USB stack and a TCP/IP Network Component that includes an SNMP agent implementation. The vulnerability is therefore not in a host operating system service but in linkable middleware source/object code that becomes part of a device vendor's firmware image; the CPE entry cpe:2.3:a:keil:mdk-middleware:*:*:*:*:*:*:*:* is recorded with a wildcard version, while the affected range is stated as 8.0.0 through 8.3.0. The assigned root-cause class is CWE-195 (Signed to Unsigned Conversion Error), a pattern in which a signed value is converted to an unsigned type and a resulting length or index becomes unexpectedly large or wraps, which in a parsing path can produce an out-of-bounds read rather than a write; the supplied sources do not describe the specific conversion site, the SNMP message field involved, or the exact packet sequence that triggers the over-read, so the precise trigger is not described in the available sources. The CVSS vector places the flaw on the network attack surface with low complexity and no privileges or user interaction, consistent with an SNMP request handled before authentication; confidentiality is scored as none and integrity as none, with only a low availability impact recorded.

Know when Mdk Middleware 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 (Arm) PRIMARY 5.3 MEDIUM
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
vuln.today AI 5.3 MEDIUM

Pre-authentication, network-facing SNMP parsing gives AV:N/AC:L/PR:N/UI:N; out-of-bounds read yields a crash/DoS (A:L) with no confirmed confidentiality or integrity impact.

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

Primary rating from Vendor (Arm).

CVSS VectorVendor: Arm

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
Low

DescriptionCVE.org

Arm Keil MDK-Middleware 8.0.0-8.3.0 may allow pre-authentication out-of-bounds read in SNMP processing

Threat Intelligence Overview

EPSS Score
0.4%
Top 65% exploitable
Prevalence
Low
embedded ARM microcontroller middleware; niche per-device SNMP stack footprint
Data Quality
4 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

26
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +26
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.

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