CVE-2026-36356
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe GoAhead web server on MeiG Smart FORGE_SLT711 devices (firmware MDM9607.LE.1.0-00110-STD.PROD-1) allows unauthenticated OS command injection via the /action/SetRemoteAccessCfg endpoint.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe GoAhead web server on MeiG Smart FORGE_SLT711 devices (firmware MDM9607.LE.1.0-00110-STD.PROD-1) contains an unauthenticated OS command injection vulnerability in the /action/SetRemoteAccessCfg endpoint. An attacker can send specially crafted requests to execute arbitrary OS commands without any authentication credentials, achieving remote code execution at the operating system level.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify device model and firmware versionCheck the device label or system information for the model number FORGE_SLT711 and firmware version MDM9607.LE.1.0-00110-STD.PROD-1. On the device, run 'cat /proc/version' or check the web server banner if accessible.Affected if The device is a MeiG Smart FORGE_SLT711 running firmware MDM9607.LE.1.0-00110-STD.PROD-1 or earlier versions.
-
Confirm GoAhead web server is runningCheck for the GoAhead HTTP server process by running 'ps | grep goahead' or 'ps aux' on the device. Alternatively, probe the HTTP service banner if exposed.Affected if The GoAhead web server process is running on the device.
-
Verify the vulnerable endpoint existsAttempt to access the URI /action/SetRemoteAccessCfg on the device's web server (e.g., curl http://<device-ip>/action/SetRemoteAccessCfg). Check if the endpoint responds or returns an error indicating it exists.Affected if The /action/SetRemoteAccessCfg endpoint is present and accessible without authentication.
-
Inspect web server configurationExamine the GoAhead web server configuration files (typically webs.conf or goahead.conf in /etc or /etc/web) to see if the SetRemoteAccessCfg handler is defined and enabled.Affected if The SetRemoteAccessCfg handler is enabled in the web server configuration.
-
Check for signs of unauthorized command executionReview system logs (/var/log/messages, /var/log/syslog) and shell history files for unexpected commands, especially those involving network callbacks, shell spawns, or suspicious utilities. Look for anomalies in /proc/<pid>/cmdline for web server child processes.Affected if Logs or process information shows unexpected command execution originating from the web server.
A defender is affected if they operate a MeiG Smart FORGE_SLT711 device with the specified firmware where the GoAhead web server exposes the unauthenticated /action/SetRemoteAccessCfg endpoint.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply vendor-provided firmware updates when available; as an interim measure, disable or restrict network access to the vulnerable web server endpoint and implement network segmentation to limit exposure of affected devices.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-36356 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-36356 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data