dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-52186

CRITICAL · 9.8 CVSS v3.1 Published 2026-07-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 8 weeks old

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 · unedited
SQL Injection vulnerability in UTT nv518G nv518GV3v3.2.7-210919-161313 allows a remote attacker to execute arbitrary code via the gohead/sub_463bbc component

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 · moderate confidence

SQL injection vulnerability in the gohead/sub_463bbc component of UTT nv518G router firmware (nv518GV3v3.2.7-210919-161313) allows remote attackers to execute arbitrary code via specially crafted SQL queries.

MitigationApply vendor firmware patch if available; otherwise restrict management interface access to trusted networks or replace end-of-life devices with supported hardware.

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
High

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the router model
    Check the device label or login to the admin interface to confirm the model is UTT nv518G
    Affected if The device is NOT a UTT nv518G router
  2. Check the firmware version
    Login to the router admin interface and look in System Settings or Firmware Upgrade section for the version string, or use the command 'cat /proc/version' or 'cat /etc/version' via telnet/ssh if available
    Affected if The firmware version is V3v3.2.7-210919-161313
  3. Verify the vulnerable component is present
    Access the router via telnet/ssh and check for the existence of the binary or component at path 'gohead' or 'sub_463bbc' if accessible, or look for web endpoints that invoke this component
    Affected if The gohead binary or sub_463bbc component is present on the device
  4. Check management interface exposure
    Determine if the router web management interface (typically HTTP/HTTPS on port 80/443 or custom ports) is accessible from untrusted networks by reviewing firewall rules or network configuration
    Affected if The management interface is exposed to untrusted networks (internet-facing or less-trusted LAN segments)

You are affected if you have a UTT nv518G router running firmware version V3v3.2.7-210919-161313 with the gohead/sub_463bbc component and its management interface is accessible from untrusted networks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor firmware patch if available; otherwise restrict management interface access to trusted networks or replace end-of-life devices with supported hardware.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,940
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,304.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-52186 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-52186 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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