CVE-2026-11517
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 vulnerability was determined in UTT HiPER 2610G up to 3.0.0-171107. This impacts the function strcpy of the file /goform/formConfigDnsFilterGlobal. Executing a manipulation of the argument GroupName can lead to buffer overflow. The attack can be executed remotely. The exploit has been publicly disclosed and may be utilized.
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 UTT HiPER 2610G router (versions up to 3.0.0-171107) in the /goform/formConfigDnsFilterGlobal web interface function. The strcpy function is used unsafely to copy the GroupName HTTP parameter without length validation, allowing remote attackers to overflow a fixed-size buffer and potentially achieve code execution.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 modelAccess the router web interface or check the device label/menu to confirm the model is UTT HiPER 2610GAffected if Device is not a UTT HiPER 2610G router - not affected by this specific CVE
-
Check the firmware versionIn the router web interface, navigate to System Status or Firmware Upgrade page to view the current firmware version. Compare against 3.0.0-171107Affected if Firmware version is 3.0.0-171107 or lower (any version up to and including that release)
-
Verify the web management interface is accessibleAttempt to access the router HTTP interface at the default gateway IP (typically 192.168.1.1) on port 80 or 443Affected if The /goform/formConfigDnsFilterGlobal endpoint is reachable over the network
-
Confirm DNS Filter feature is enabledIn the router web interface, navigate to the DNS Filter or Content Filtering settings section and check if this feature is turned onAffected if DNS Filter feature is enabled and the GroupName parameter can be submitted via the vulnerable form handler
A UTT HiPER 2610G router running firmware version 3.0.0-171107 or earlier, with the web interface accessible and DNS Filter feature enabled, is affected by this buffer overflow vulnerability in the formConfigDnsFilterGlobal handler.
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 firmware update if available; otherwise implement network-level mitigations such as restricting access to the device's web management interface via ACLs or placing the device behind a WAF/IPS capable of detecting and blocking abnormally long HTTP parameter values.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-11517 — 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-11517 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