Skip to main content

AAS Edge Client EUVDEUVD-2026-92985

| CVE-2026-94293 CRITICAL
Missing Authentication for Critical Function (CWE-306)
2026-10-06 CERTVDE GHSA-38w2-7jv3-258f
9.3
CVSS 4.0 · Vendor: CERTVDE
View

Attack ChainAIDerived

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

  1. Access
    Reach AAS Edge Client API endpoint
  2. Delivery
    Send unauthenticated GET requests
  3. Exploit
    Read all exposed submodel data
  4. Execution
    Send crafted PATCH request
  5. Persist
    Modify submodel data
  6. Impact
    Corrupt digital-twin / asset state

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Authentication required for critical functions
MITRE ATT&CK

1 technique across 1 tactic: Initial Access

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 AAS Edge Client's REST API that serves Asset Administration Shell submodel data; the attacker needs no credentials, no user interaction, and the flaw affects the product's GET and PATCH endpoints because they lack authentication (CWE-306). The input lists the product as 'all versions,' implying no version is known to be safe. The primary limiting factor is network exposure: risk is high where the API is reachable from untrusted or OT networks and substantially lower where the Edge Client is segmented behind firewalls or accessible only on isolated industrial networks. Authentication requirements are confirmed (PR:N) - no auth is needed.

Impact

This is a genuine high-priority issue, not an inflated high-CVSS score. The provided CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N) describes network-reachable, low-complexity, unauthenticated exploitation with no user interaction, which is fully consistent with the description ('unauthenticated remote attacker') and the CWE-306 (Missing Authentication for Critical Function) classification - the signals agree with each other rather than conflicting. The impact claim is strong: attackers can both read all GET-exposed data (confidentiality) and modify submodel data via PATCH (integrity), mapping cleanly to VC:H/VI:H. The input's availability claim (VA:H) is not directly supported by the description, which mentions only read and modify operations - I have down-weighted availability in my own assessment and flag it as an inference rather than a confirmed impact. No EPSS score, SSVC decision, KEV listing, or POC indicator was supplied, so exploitation-probability and in-the-wild signals are absent; the current status is 'no public exploit identified at time of analysis.' The dominant risk driver is therefore the trivial exploitability (no auth, no interaction) against an industrial/IIoT component, tempered by the fact that real-world exposure depends heavily on whether the Edge Client's API is reachable from untrusted networks, which is unknown from the data.

Exploit ScenarioDerived

An attacker with network access to the Murrelektronik AAS Edge Client API issues unauthenticated GET requests to harvest all exposed Asset Administration Shell data, then sends crafted PATCH requests to alter submodel values - potentially corrupting the digital-twin state that drives downstream industrial processes. Because no authentication is required and complexity is low, any party able to reach the endpoint can perform this; no public exploit code is identified at time of analysis, but the attack requires only standard HTTP tooling.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
No patch listed yet 0.3% exploitation probability (EPSS)

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

Alert me

AnalysisAIv1 – Oct 06, 2026

Unauthenticated attackers who can reach the Murr Elektronik AAS Edge Client (all versions) REST API can read every data set exposed by its GET endpoints and alter Asset Administration Shell submodel data through PATCH requests, because those endpoints were deployed without any authentication (CWE-306). The issue is scored 9.3 under CVSS 4.0 and 9.1 under our CVSS 3.1 assessment (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N), reflecting trivial network-only reachability, no credential requirement, and high confidentiality and integrity impact; availability is not affected in our assessment. No public exploit code and no CISA KEV listing were identified at time of analysis, so actual risk is driven almost entirely by exposure: high where the Edge Client API sits on an untrusted or flat OT network, substantially lower where it is segmented behind firewalls or confined to isolated industrial networks.

RemediationAI

No vendor-released patch was identified at time of analysis, so remediation must start with compensating controls while tracking CERT@VDE advisory VDE-2026-108 (https://www.certvde.com/en/advisories/VDE-2026-108/) for a fixed build. The highest-value action is to stop the unauthenticated REST API from being reachable by untrusted clients: place the Edge Client on a dedicated management/OT VLAN, and add firewall or ACL rules that permit TCP access to its API port only from known engineering hosts, which immediately removes the remote, no-credential attack path - at the cost of breaking any legitimate cross-segment integrations until those source addresses are whitelisted. Where the API cannot be fully isolated, front it with a reverse proxy that enforces HTTP Basic, an API key, or mutual TLS and forwards only authenticated traffic; this preserves the PATCH workflow but introduces credential management and can break consumer tools that currently speak to the endpoint unauthenticated, so test in a lab first. If the deployment only needs read access, disable or block PATCH at the proxy or host firewall so submodel data cannot be modified even if reads remain open - the trade-off is loss of remote configuration capability. In parallel, restrict outbound trust so downstream systems do not act on AAS submodel values from an unauthenticated source, and enable request logging on the API to detect enumeration-style GET sweeps or unexpected PATCH calls, which is detection rather than prevention and must not be relied on alone. Given the assessed CVSS 3.1 score of 9.1 and no confirmed public exploit, prioritization should follow network exposure rather than urgency of active compromise.

Affected VersionsENISA

Software AAS Edge Client all versions 0.0.0

Affected Packages

euvd software_aas_edge_client_all_versions 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

The Asset Administration Shell (AAS) is the standardized digital-twin representation used in Industrie 4.0 / IEC 63278 and IDTA specifications, in which each asset is described by one or more submodels (nameplate, technical data, operational parameters) exposed through REST-style interfaces. The Murr Elektronik AAS Edge Client acts as a gateway that surfaces shop-floor asset data into that AAS layer, and CPE cpe:2.3:a:murrelektronik:software_aas_edge_client_all_versions indicates the vendor's software family is affected across every released version, with no known-safe build. The root cause is CWE-306, Missing Authentication for Critical Function: the GET endpoints that enumerate submodel content and the PATCH endpoints that mutate submodel properties are served without any authentication or authorization check, so the HTTP methods themselves become the only requirement for interaction. This is a design/deployment flaw rather than a memory-safety or injection bug - there is no exploit chain, obfuscation, or payload needed; a single crafted request returns or rewrites data. Because the same unauthenticated surface governs both read and write, an attacker can enumerate the full data model first (reconnaissance via GET) and then tamper with it (integrity loss via PATCH), which is particularly dangerous in OT/ICS contexts where AAS submodel values may feed downstream engineering, monitoring, or orchestration systems that trust the Edge Client as an authoritative source.

Know when Software Aas Edge Client All Versions 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 (CERTVDE) PRIMARY 9.3 CRITICAL
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
vuln.today AI 9.1 CRITICAL

Unauthenticated network API with no interaction gives AV:N/AC:L/PR:N/UI:N; full data read and modify yield C:H/I:H, but no availability impact is described so A:N.

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

Primary rating from Vendor (CERTVDE).

CVSS VectorVendor: CERTVDE

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

DescriptionCVE.org

An unauthenticated remote attacker can modify Asset Administration Shell submodel data via PATCH requests and can read all data exposed by the GET endpoints.

Executive ViewAI

Why It Matters

Murr Elektronik's AAS Edge Client (all versions) is affected by a critical authentication bypass that allows unauthenticated network attackers to read and alter sensitive industrial asset data. This vulnerability poses a significant risk to organizations using this product in operational technology environments, as it could lead to unauthorized data manipulation and potential disruption of industrial processes. With no vendor patch available, leadership should prioritize immediate mitigation to protect data integrity and confidentiality.

Business Impact: High
Compensating Controls

Network segmentation, restrict API access to trusted IPs, deploy authenticated reverse proxy, monitor logs for anomalous GET and PATCH requests.

Threat Intelligence Overview

EPSS Score
0.3%
Top 74% exploitable
Prevalence
Low
niche industrial IIoT edge client, limited vendor-specific deployment footprint
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 CRITICAL
CISA KEV No
Public POC No
EPSS 0.3%
Patch available No
Active threat No
Deciding rule
CRITICAL severity
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
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact
High
Technical Impact
Total

Priority Score

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

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

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