CVE-2026-12197
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 · uneditedA security flaw has been discovered in Ruijie EG105G-P 2.340. The impacted element is the function nslookup of the file /cgi-bin/luci/api/diagnose of the component JSON-RPC Diagnose Endpoint. Performing a manipulation of the argument params.target results in command injection. It is possible to initiate the attack remotely. The exploit has been released to the public and may be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.
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 confidenceCommand injection vulnerability in Ruijie EG105G-P router firmware 2.340 where the nslookup function in /cgi-bin/luci/api/diagnose does not sanitize the params.target parameter, allowing remote attackers to inject arbitrary shell commands via the JSON-RPC Diagnose Endpoint.
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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
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 the device modelCheck the router label, web management interface system info, or CLI output for the exact model number (e.g., via 'show version' or checking the web UI dashboard)Affected if The device is not a Ruijie EG105G-P router, then it is not affected by this specific CVE
-
Check the firmware versionAccess the router's web management interface and navigate to System > Firmware or Status > Overview to view the installed firmware version; alternatively, check via CLI if availableAffected if The firmware version is not 2.340 (the specific version listed as affected)
-
Verify web interface exposureCheck router firewall settings or network configuration to determine if the web management interface (HTTP/HTTPS on port 80/443) is accessible from untrusted networks or the WAN interfaceAffected if The management interface is exposed to untrusted networks, increasing the attack surface for authenticated exploitation
-
Confirm authentication is requiredAttempt to access the /cgi-bin/luci/api/diagnose endpoint without credentials or verify that the router requires valid login credentials before allowing access to diagnostic functionsAffected if The endpoint is accessible without authentication (the CVE requires authenticated attackers)
-
Inspect diagnostic function availabilityIf you have access, examine the router's web UI or luci API to determine if the nslookup diagnostic function is present and enabled under the diagnose APIAffected if The nslookup function in the diagnose API is not available or disabled in the firmware
The device is affected only if it is specifically a Ruijie EG105G-P router running firmware version 2.340, with the web management interface accessible to untrusted users and the nslookup diagnostic function enabled.
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 network segmentation to isolate the router management interface from untrusted networks; if possible, disable or restrict access to the diagnostic API endpoint until vendor supplies a patch.
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-12197 — 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-12197 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