CVE-2026-52190
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_448384 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_448384 component of UTT nv518G router firmware (nv518GV3v3.2.7-210919-161313). A remote attacker can exploit this by sending specially crafted input to overflow a buffer, causing the device to crash and result in denial of service. The CVSS 7.5 score indicates high severity due to the network attack vector and complete availability impact.
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 device modelLog into the router admin interface or check the device label to confirm the model is UTT nv518GAffected if Device is not an UTT nv518G router, then it is not affected
-
Check firmware versionAccess router administration panel, look for firmware/version information in system settings or status page, or use command line if accessible (e.g., cat /proc/version or vendor-specific command)Affected if Firmware version is nv518GV3v3.2.7-210919-161313 or falls within the same release branch (v3.2.7 series)
-
Confirm gohead service is activeCheck if the gohead process or sub_448384 component is running on the device via process list (ps command) or by examining exposed network services on the routerAffected if The gohead service is enabled and listening on network interfaces
-
Assess network exposureReview firewall rules and WAN interface configuration to determine if the router or its management interfaces are directly accessible from untrusted networksAffected if The router management interface or gohead service is exposed to the internet or untrusted LAN segments without proper access controls
The device is affected if it is an UTT nv518G router running firmware nv518GV3v3.2.7-210919-161313 (or equivalent v3.2.7 branch) with the gohead component active and accessible from a network where an attacker could send malicious input.
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 patches when available. If no patch exists, consider network segmentation to limit exposure to untrusted networks and implement input validation/filtering at upstream network devices.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-52190 — 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-52190 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