Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-112371 Overview
CVE-2026-112371 is a code injection vulnerability affecting the H3C Magic NX15 router running firmware version NX15V100R017. The flaw resides in the write function of the /api/esps endpoint within the device's RPC Interface component. Attackers can manipulate the path argument to inject arbitrary code remotely. The exploit has been publicly disclosed through a GitHub proof-of-concept repository, raising the risk of opportunistic exploitation against exposed devices. The vendor was notified prior to public disclosure.
Critical Impact
Authenticated remote attackers can inject code into the H3C Magic NX15 router's RPC Interface, leading to root-level remote code execution and complete compromise of the networking device.
Affected Products
- H3C Magic NX15 router
- Firmware version NX15V100R017
- RPC Interface component exposing /api/esps
Discovery Timeline
- 2026-10-19 - CVE-2026-112371 published to NVD
- 2026-10-20 - Last updated in NVD database
Technical Details for CVE-2026-112371
Vulnerability Analysis
The vulnerability is classified under [CWE-74] (Improper Neutralization of Special Elements in Output Used by a Downstream Component). It affects the write function exposed through the /api/esps RPC endpoint on the H3C Magic NX15 router. The endpoint accepts a path parameter that is passed to a downstream file-write routine without adequate sanitization. By controlling the path argument, an attacker can inject attacker-controlled content into a location interpreted and executed by the device, resulting in remote code execution with root privileges on the embedded Linux platform.
The attack is executed over the network. Based on the CVSS vector, exploitation requires low privileges and no user interaction, which aligns with scenarios where attackers already possess a valid session or reach the RPC interface through weak credentials or exposed management interfaces.
Root Cause
The root cause is improper neutralization of input used by a downstream component. The write handler in /api/esps trusts caller-supplied values for the path argument and writes content to the filesystem without validating that the destination is within an allowed directory or that the content is non-executable. This design permits adversaries to drop or overwrite scripts, configuration files, or startup resources used by the router's firmware.
Attack Vector
An authenticated attacker reachable over the network sends a crafted RPC request to /api/esps invoking the write function with a manipulated path. The request causes the router to write attacker-controlled data to a privileged location, which is then executed by the device, yielding root-level command execution. Public exploit material is available in a GitHub PoC repository, and additional context is published in the VulDB Vulnerability Report.
No verified exploit code is reproduced here. Technical details are available in the referenced advisories.
Stop Remote Code Execution Before It Runs
Singularity™ Endpoint detects and blocks exploit attempts at machine speed, including zero-days and novel attack techniques.
Stop Exploit AttemptsDetection Methods for CVE-2026-112371
Indicators of Compromise
- Unexpected HTTP or RPC requests targeting the /api/esps endpoint, particularly those invoking the write function with unusual path values.
- New or modified files in system directories on the router, including startup scripts, cron entries, or web root content.
- Outbound connections initiated by the router to unknown external hosts following administrative access events.
- Unauthorized administrative sessions preceding file-system changes on the device.
Detection Strategies
- Inspect router web and management traffic for POST requests to /api/esps containing path traversal characters or references outside expected working directories.
- Correlate authentication logs with subsequent RPC calls to identify low-privilege accounts invoking file-write operations.
- Compare firmware file hashes against known-good baselines to detect post-exploitation persistence.
Monitoring Recommendations
- Forward router syslog and administrative access logs to a centralized collector for retention and correlation.
- Monitor north-south traffic for connections from router management interfaces to unexpected destinations.
- Alert on configuration changes applied outside sanctioned change windows.
How to Mitigate CVE-2026-112371
Immediate Actions Required
- Restrict access to the router's management and RPC interfaces to trusted administrative networks only.
- Disable remote management from WAN interfaces unless strictly required for operations.
- Rotate credentials for all accounts with access to the H3C Magic NX15 management plane.
- Review the device for signs of file-system tampering, unauthorized startup entries, and unknown processes.
Patch Information
No vendor patch URL is listed in the public references at the time of writing. H3C was contacted prior to disclosure. Administrators should monitor H3C security bulletins for firmware updates addressing the /api/espswrite handler and apply updates to affected NX15V100R017 deployments as soon as they are published.
Workarounds
- Place the router behind a network ACL that permits management traffic only from a dedicated administrative subnet.
- Enforce strong, unique credentials and multi-factor authentication where supported to limit the pool of accounts that satisfy the low-privilege requirement.
- Segment the router from untrusted internal networks to reduce the attack surface available to authenticated users.
- Monitor the VulDB CVE Details page for vendor advisory updates and apply firmware patches promptly.
# Example: restrict management access to a trusted admin subnet
# (adapt to your network boundary device syntax)
deny tcp any any eq 80
deny tcp any any eq 443
permit tcp 10.10.0.0/24 any eq 80
permit tcp 10.10.0.0/24 any eq 443
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

