Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-94293 – Unauthenticated Remote Read/Write (RCE-level Data Manipulation) – Murrelektronik So

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-94293 is a critical Missing Authentication for Critical Function (CWE-306) vulnerability affecting the Murrelektronik Software AAS Edge Client, an open-source Asset Administration Shell (AAS) reference client originally built as a trade-fair demonstrator. The client’s REST API binds to all network interfaces on TCP port 18000, performs no authentication, and accepts cross-origin requests from any origin, allowing any unauthenticated network attacker to read and modify AAS submodel data. The vulnerability affects all released versions of the product and carries a CVSS v3.1 base score of 9.8 (Critical).

Technical details

  • Root cause: The aas-edge-client exposes a REST API with no authentication or access control mechanism, and the API is bound to all network interfaces rather than being restricted to localhost or a trusted segment.
  • Trigger conditions: No authentication, user interaction, or special privileges are required. The service also accepts cross-origin requests from any origin (no CORS restriction), widening the exposure to browser-based attacks as well as direct network access.
  • Attack vector: Network-based (AV:N). An attacker with network access to TCP port 18000 can directly interact with the exposed GET and PATCH endpoints.
  • Impact: Attackers can read all data exposed via GET endpoints and modify AAS submodel data via PATCH requests. Because modified data can propagate to central AAS servers, the impact extends beyond the local device to downstream systems that consume or trust the AAS data, affecting confidentiality, integrity, and availability.

Affected software

  • Murrelektronik Software AAS Edge Client — all versions (version range: 0.0.0 and later / all released versions)

Severity

  • CVSS v3.1 Base Score: 9.8 (Critical)
  • CVSS v3.1 Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
  • (A CVSS v4.0 score of 9.3 Critical, vector 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, has also been assigned.)

Mitigation and recommended actions

  • No patch is available. The vendor has stated that the aas-edge-client was strictly a trade-fair demonstrator never intended for production use, and it will not be releasing a fix.
  • Immediate action: Discontinue use of the aas-edge-client and remove all existing deployments, along with any copies of the source code and container images.
  • All related repositories for this software have been archived by the vendor and set to private.
  • Organizations unable to immediately remove the software should isolate any running instances from untrusted networks and restrict access to TCP port 18000 at the network perimeter as a temporary compensating control, while planning for full decommissioning.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge