CVE-2025-27850
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 locally served web site on the Garmin WDU (v1 1.4.6 and v2 5.0) allows a symlink attack. If a malicious graphics package containing symlinks is uploaded, the web server follows the supplied links when serving content. No mechanisms to restrict those link targets to a specific area of the filesystem is enabled. This allows an attacker to retrieve arbitrary files from the device.
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 symlink attack vulnerability exists in the locally served web site of Garmin WDU devices (v1 1.4.6 and v2 5.0). Attackers can upload a malicious graphics package containing symbolic links, causing the web server to follow these links when serving content. Since no filesystem path restrictions are enforced, the vulnerability allows retrieval of arbitrary files from the device.
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= 1.4.6= 5.00CVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 firmware versionAccess the Garmin Empirbus Wireless Display Unit web interface (typically at the device IP) and navigate to the system information or firmware settings page to view the installed firmware version. Alternatively, check via CLI if you have administrative shell access.Affected if The installed firmware version is exactly 1.4.6 or exactly 5.00 (these are the affected versions).
-
Confirm web server is accessibleAttempt to access the device's web interface via HTTP or HTTPS on the device IP address. Look for pages related to graphics, themes, or media uploads.Affected if The web interface is accessible and contains functionality for uploading graphics packages or theme files.
-
Check web server symlink configurationIf you have access to the device's configuration files or administrative panel, examine the web server settings for options related to 'FollowSymLinks', 'symlink', or symbolic link handling.Affected if Symlink following is enabled or no explicit restriction on following symbolic links is configured on the web server.
-
Verify graphics upload feature is enabledLocate the upload functionality within the web interface (often under Settings, Appearance, Graphics, or Theme sections). Determine if the file upload feature is available to any user or admin account.Affected if The graphics package upload feature is enabled and accessible without additional security controls.
You are affected if your Garmin WDU firmware is version 1.4.6 or 5.00, the web interface is accessible, and the graphics upload feature with symlink-following behavior is present.
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 dataImplement web server configuration to disable symlink following, add path validation to ensure symbolic links resolve only within an allowed directory, and implement integrity verification for uploaded graphics packages before deployment.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-27850 — 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-27850 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