CVE-2025-34118
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 path traversal vulnerability exists in Linknat VOS Manager versions prior to 2.1.9.07, including VOS2009 and early VOS3000 builds, that allows unauthenticated remote attackers to read arbitrary files on the server. The vulnerability is accessible via multiple localized subpaths such as '/eng/', '/chs/', or '/cht/', where the 'js/lang_en_us.js' or equivalent files are loaded. By injecting encoded traversal sequences such as '%c0%ae%c0%ae' into the request path, attackers can bypass input validation and disclose sensitive files.
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 path traversal vulnerability in Linknat VOS Manager versions prior to 2.1.9.07 allows unauthenticated remote attackers to read arbitrary files on the server by injecting encoded traversal sequences ('%c0%ae%c0%ae') into localized subpaths such as '/eng/', '/chs/', or '/cht/' when loading language files like 'js/lang_en_us.js', bypassing input validation.
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
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
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 Linknat VOS Manager installationSearch for Linknat VOS Manager by checking running processes, installed services, or common installation directories such as /opt/linknat/, /usr/local/linknat/, or C:\Program Files\Linknat\. Also check web server configurations for VOS Manager web applications.Affected if The product is installed and running as a service or web application.
-
Determine installed versionLocate the version information - typically found in an About page, login screen footer, version file (like version.txt, version.ini), or within the web application's main JavaScript files. Compare the version number to 2.1.9.07.Affected if The installed version is lower than 2.1.9.07.
-
Verify web interface accessibilityConfirm the VOS Manager web interface is accessible by accessing common paths such as /eng/, /chs/, or /cht/ on the server. The vulnerability is exploited via HTTP requests to these language subpaths.Affected if The web interface with language subpaths (/eng/, /chs/, /cht/) is accessible over HTTP.
-
Inspect web access logs for traversal attemptsReview web server access logs (Apache, Nginx, or embedded server logs) for requests containing the encoded traversal sequence '%c0%ae%c0%ae' combined with language paths like '/eng/', '/chs/', or '/cht/' and attempts to access 'js/lang_*.js' with traversal sequences.Affected if Log entries show requests with '%c0%ae%c0%ae' encoded traversal sequences targeting language paths.
-
Check for unauthorized file access indicatorsExamine server file system for any unexpected file read access or configuration changes that may indicate successful exploitation. Review application logs for errors related to file inclusion or path traversal.Affected if Logs or file system show evidence of arbitrary file reads beyond the intended web root.
A system is affected if Linknat VOS Manager is installed with a version lower than 2.1.9.07 and its web interface with language subpaths (/eng/, /chs/, /cht/) is accessible, allowing unauthenticated attackers to inject traversal sequences and read arbitrary files.
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 · scopedUpgrade to version 2.1.9.07 or later, or apply vendor-supplied patches; implement strict input validation to block traversal sequences in all request paths.
2.1.9.07
- Identify the current version of Linknat VOS Manager (VOS2009 or VOS3000) running on the system
- Download the fixed version 2.1.9.07 from the official vendor website (www.linknat.com)
- Review the vendor release notes for any prerequisites or migration instructions
- Follow the vendor's documented upgrade procedure to install version 2.1.9.07
- Verify the upgrade was successful by checking the version number
- Test that the path traversal vulnerability is no longer exploitable by attempting the encoded traversal sequence on the affected paths (/eng/, /chs/, /cht/)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.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 $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-34118 — 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-2025-34118 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