CVE-2026-52187
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 · uneditedBuffer Overflow vulnerability in UTT nv518G nv518GV3v3.2.7-210919-161313 allows a remote attacker to cause a denial of service via the gohead/sub_483ba0 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 confidenceA buffer overflow vulnerability exists in the gohead/sub_483ba0 component of UTT nv518G routers (firmware v3.2.7-210919-161313). A remote attacker can send specially crafted input to trigger the overflow, causing denial of service. The CVSS 7.5 score indicates network-exploitable without authentication.
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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 router modelAccess the router's web administration interface or CLI and check the device model information. Look for 'nv518G' or 'UTT' branding in the status or system information page.Affected if The device is not a UTT nv518G router, then it is not affected by this specific CVE.
-
Retrieve the firmware versionIn the router's admin interface, navigate to System Status or Firmware Information page. Alternatively, use the CLI command 'cat /proc/version' or 'version' if available via telnet/SSH. Note the full firmware version string.Affected if The firmware version cannot be determined - the check is inconclusive.
-
Compare firmware to affected versionCompare your installed firmware version string to 'v3.2.7-210919-161313'. The format follows YYMMDD-HHMMSS pattern.Affected if Your firmware version is v3.2.7-210919-161313 exactly, or any version earlier than this build date (210919 indicates September 19, 2021).
-
Check gohead service exposureProbe network access to the gohead service on the router. This may run on a proprietary port. Use 'nmap' or 'netcat' to scan common ports or check the router's port forwarding/NAT settings for gohead-related services exposed to the WAN.Affected if The gohead service is directly accessible from an untrusted network (WAN/Internet) without firewall protection.
You are affected if you have a UTT nv518G router running firmware version v3.2.7-210919-161313 or earlier, and the gohead service is network-accessible.
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 any vendor-supplied firmware update for the nv518G model. If no patch is available, consider network segmentation to limit exposure to the affected device and monitor for anomalous traffic patterns to the gohead service.
- Consultation2.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 $2,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-52187 — 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-52187 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