{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-27853 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-27853 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-27853 is a high-severity authentication bypass vulnerability in n/a, published on 13 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-27853 and fix it if it is affected.\n\nWhat it is: CVE-2025-27853 is a high-severity authentication bypass vulnerability in n/a, published on 13 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-27853 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-27853/ (Markdown: https://insights.sbomify.com/CVE-2025-27853/index.md)","id":"CVE-2025-27853","markdown":"https://insights.sbomify.com/CVE-2025-27853/index.md","name":"CVE-2025-27853","record":{"aliases":["GHSA-cvgr-crrw-gcqx"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Garmin WDU","requires_auth":"none","summary":"Attackers can bypass authentication on the Garmin WDU by directly accessing unauthenticated WebSocket APIs, allowing unauthorized control of the device.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"empirbus_wireless_display_unit_firmware","vendor":"garmin"}],"cvss":{"score":7.3,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-306","name":"Missing Authentication for Critical Functionality"}],"description":"The locally served web site on the Garmin WDU (v1 1.4.6 and v2 5.0) allows its authentication to be bypassed. The WDU web site only performs authentication with the client within the client's browser. The WebSockets used to communicate with the WDU server do not enforce any authentication. An attacker may bypass all authentication mechanisms by directly utilizing the remote APIs available on the websocket.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Auth bypass in n/a","id":"CVE-2025-27853","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Apache Felix HTTP Webconsole Plugin: XSS in HTTP Webconsole Plugin","id":"CVE-2025-27867"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2025-27852"},"products":["n/a"],"published":"2026-05-13","related":[{"cvss_score":9.3,"headline":"Cross-site request forgery in n/a","id":"CVE-2025-27851","kev_date_added":null,"published":"2026-05-13"},{"cvss_score":7.5,"headline":"Path traversal in n/a","id":"CVE-2025-27850","kev_date_added":null,"published":"2026-05-13"},{"cvss_score":5,"headline":"Cross-site scripting in n/a","id":"CVE-2025-27852","kev_date_added":null,"published":"2026-05-13"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-14","vendors":["n/a"]},"summary":"Attackers can bypass authentication on the Garmin WDU by directly accessing unauthenticated WebSocket APIs, allowing unauthorized control of the device.","url":"https://insights.sbomify.com/CVE-2025-27853/"}