CVE-2025-41110
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 · uneditedEncrypted WiFi and SSH credentials were found in the Ghost Robotics Vision 60 v0.27.2 APK. This vulnerability allows an attacker to connect to the robot's WiFi and view all its data, as it runs on ROS 2 without default authentication. In addition, the attacker can connect via SSH and gain full control of the robot, which could cause physical damage to the robot itself or its environment.
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 confidenceEncrypted WiFi and SSH credentials were discovered embedded in the Ghost Robotics Vision 60 robot's Android APK (v0.27.2). Attackers who obtain these credentials can connect to the robot's WiFi network and access its ROS 2-based control system, which operates without default authentication. Additionally, SSH access provides full root-level control of the robot platform, enabling potential manipulation of physical systems.
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= 0.27.2CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/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 Vision 60 firmware versionAccess the robot's administrative interface or check the firmware version through the robot's system information. This is typically available via the robot's web UI, console command, or configuration files. Common methods include accessing /etc/version, checking the about page in the robot management software, or running 'fw_printenv' or similar version commands if available on the device.Affected if The firmware version is exactly 0.27.2
-
Locate and inspect the Vision 60 APKSearch for the Vision 60 APK file on systems where it has been deployed or downloaded. The APK is typically distributed through Ghost Robotics update channels or documentation. Inspect the APK contents for embedded credential files, configuration files containing encrypted strings, or binary files that appear to contain network credentials.Affected if The APK contains hardcoded encrypted WiFi credentials, SSH private keys, or credential configuration files that are embedded in the application package.
-
Check if WiFi network uses hardcoded credentialsCompare the WiFi credentials currently in use on the robot's network against any credentials found in the APK or documentation. Access the robot's WiFi configuration through its management interface and verify whether the active WiFi password or SSID matches any default values that may have been extracted from the APK.Affected if The robot's WiFi is configured with credentials that were extracted from the APK or are known default values from the firmware release.
-
Verify SSH access statusCheck if SSH access is enabled on the robot and whether it accepts authentication using credentials derived from the APK. Attempt to enumerate active SSH users or check the robot's SSH configuration to determine if default or hardcoded SSH credentials are functional.Affected if SSH is accessible and accepts authentication using credentials found in the APK or uses the same key material distributed with firmware v0.27.2.
-
Assess ROS 2 authentication configurationExamine the ROS 2 configuration on the robot to determine whether authentication is enabled for node-to-node and client communications. Check for the presence of SROS2 configuration, authentication plugins, or security node configurations that would protect ROS 2 topics and services.Affected if ROS 2 is running without authentication, authorization, or encryption protections, allowing unauthenticated control of robot operations.
You are affected if your Vision 60 runs firmware version 0.27.2 and the WiFi/SSH credentials in use match those embedded in the APK, or if ROS 2 operates without authentication enabled.
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 dataRotate all exposed WiFi and SSH credentials immediately, implement strong authentication for ROS 2 communications, remove hardcoded credentials from firmware/images, and restrict network access to trusted endpoints.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-41110 — 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-41110 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