CVE-2026-35082
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 · uneditedThe ugw-logread method allows a remote attacker with user privileges to access arbitrary local files due to insufficient validation of user-supplied input.
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 confidenceThe ugw-logread method contains a path traversal vulnerability that allows authenticated remote attackers with user privileges to read arbitrary local files on the system due to insufficient validation of user-supplied input used to specify log file paths.
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 the product and firmware versionAccess the gateway's web interface or administrative console, or run 'fwprintenv' or check /etc/version on the device to obtain the installed firmware versionAffected if The firmware version is Universal Gateway and is earlier than 6_00_07
-
Locate the ugw-logread method or binarySearch for the ugw-logread executable or script on the system using 'find / -name "ugw-logread" 2>/dev/null' or check common CGI/bin directoriesAffected if The ugw-logread method exists and is executable on the system
-
Verify remote access authentication settingsCheck the gateway's configuration for remote management access and authentication settings, typically found in the web interface under 'Remote Access' or in /etc/config filesAffected if Remote authentication is enabled, allowing authenticated users to access the ugw-logread method
-
Test for path traversal vulnerabilityIf you have access to the ugw-logread method, attempt a controlled test by passing a path traversal sequence like '../../etc/passwd' as input to see if arbitrary file reading is possibleAffected if The method accepts and processes path traversal sequences without proper validation, allowing access to files outside the intended directory
Your environment is affected if you are running Mbs Solutions Universal Gateway firmware version earlier than 6_00_07 with the ugw-logread method accessible to remote authenticated users.
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 strict input validation, path canonicalization, and allowlist-based filtering on file path parameters in the logread functionality to prevent directory traversal attacks.
Universal Gateway Firmware version 6_00_07 or later
- 1. Backup the current Universal Gateway configuration before upgrading
- 2. Obtain the fixed firmware version 6_00_07 or later from the vendor (certvde.com or official vendor channels)
- 3. Access the device administration interface and navigate to the firmware update section
- 4. Upload and install the firmware version 6_00_07
- 5. After rebooting, verify the upgrade was successful by checking the firmware version in the system info
- 6. Confirm the vulnerability is remediated by verifying the ugw-logread method now properly validates input and prevents path traversal
Generated from the published advisory — verify against the referenced sources before acting.
- 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-35082 — 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-35082 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