dbcve.org
Classic Buffer OverflowWeakness · CWE-120

CVE-2026-52191

HIGH · 7.5 CVSS v3.1 Published 2026-07-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click 7 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
Buffer Overflow vulnerability in UTT nv518G nv518GV3v3.2.7-210919-161313 allows a remote attacker to cause a denial of service via the gohead/sub_444C8C 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

A buffer overflow vulnerability exists in the UTT nv518G router firmware (nv518GV3v3.2.7-210919-161313) within the gohead/sub_444C8C component. A remote attacker can trigger this flaw to cause a denial of service, likely by sending specially crafted input that overflows a buffer in the affected component.

MitigationApply any vendor-supplied firmware update if available; otherwise, isolate the device behind a firewall or restrict network access to mitigate remote exploitation.

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 checks

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

  1. Identify the router model
    Access the router admin interface or check the device label to confirm the model is UTT nv518G
    Affected if The device is not an UTT nv518G router
  2. Determine the firmware version
    Log into the router web interface (typically at 192.168.1.1) and navigate to Status or System section to view the firmware version, or use telnet/SSH to access the device and run 'cat /proc/version' or check /etc/version if accessible
    Affected if The installed firmware version matches nv518GV3v3.2.7-210919-161313 or falls within the affected version range
  3. Verify the gohead service is active
    If you have shell access via telnet/SSH, run 'ps | grep gohead' or check for the gohead process to confirm the vulnerable component is running
    Affected if The gohead process is running on the device
  4. Check for the affected sub_444C8C component
    If filesystem access is available, search for the binary or library containing 'sub_444C8C' using 'find / -name *gohead*' or inspect the firmware image for the mentioned component
    Affected if The sub_444C8C component is present in the firmware

The device is affected if it is an UTT nv518G router running firmware version nv518GV3.2.7-210919-161313 with the gohead service active.

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 any vendor-supplied firmware update if available; otherwise, isolate the device behind a firewall or restrict network access to mitigate remote exploitation.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-52191 — 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-52191 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