CVE-2026-35085
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 remote attacker with user privileges can exploit a stack buffer overflow in gdv-serverconfig to gain full system access as root.
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 · high confidenceA stack buffer overflow vulnerability exists in gdv-serverconfig that allows an authenticated remote attacker with standard user privileges to overflow a stack-based buffer and achieve arbitrary code execution as root, resulting in complete system compromise.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 6_00_07CVSS 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 Universal Gateway Firmware versionAccess the device management interface or check /etc/version or /proc/version file on the device to determine the installed firmware versionAffected if version is present and less than 6_00_07
-
Locate gdv-serverconfig binaryRun 'find / -name gdv-serverconfig 2>/dev/null' or check common binary locations like /usr/sbin/, /usr/local/bin/, or /opt/ directoriesAffected if the binary exists on the system
-
Verify gdv-serverconfig is runningRun 'ps aux | grep gdv-serverconfig' or check running processes to see if the service is activeAffected if the service is running and exposed to network
-
Check service exposureReview network configuration, firewall rules, or run 'netstat -tlnp | grep gdv-serverconfig' to determine if gdv-serverconfig is listening on network portsAffected if the service is listening on accessible network interfaces
-
Compare version to affected rangeIf gdv-serverconfig has a version flag, run 'gdv-serverconfig --version', otherwise rely on firmware version comparisonAffected if firmware version is below 6_00_07 or gdv-serverconfig version cannot be determined but firmware is outdated
The environment is affected if Mbs Solutions Universal Gateway Firmware with gdv-serverconfig is installed and the firmware version is below 6_00_07 with the service exposed to network access.
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.
dbcve · scoped6_00_07
Implement proper bounds checking on all user-controlled input, replace unsafe string manipulation functions (strcpy, sprintf, etc.) with secure alternatives (strncpy, snprintf), and apply vendor security patches. Consider implementing stack canaries and enabling compiler-level stack protection.
6_00_07
- Upgrade Universal Gateway Firmware to version 6_00_07 or later to remediate the stack buffer overflow vulnerability in gdv-serverconfig.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-35085 — 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-35085 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