Skip to main content
Menu
CVEs

FrodoBots EarthRover Mini+ firmware hard-coded cloud credentials in device firmware

CVE-2026-121685EUVD-2026-120090Published November 9, 2026, updated

9.8CriticalCISA-ADP
Exploited
No known exploitation
Fix
See vendor advisory
Who is exposed
Not reported

Summary

FrodoBots EarthRover Mini+ firmware contains hard-coded, fleet-wide credentials, including keys for AWS IAM and AWS IoT MQTT, BasicAuth credentials for an Agora token service, and a Slack incoming webhook URL. Anyone who downloads the publicly available firmware file can extract these credentials through static analysis, and doing so requires no special privileges.

Written by a model

Original description

FrodoBots EarthRover Mini+ firmware (version 6.2.4_6.2.5_0.614.0) contains multiple sets of hard-coded credentials. These include fleet‑wide credentials, including BasicAuth credentials for an Agora token service, AWS IAM access keys, AWS IoT MQTT credentials, and a Slack incoming webhook URL. These credentials are embedded directly in frodobot.bin and are accessible through static analysis of the publicly downloadable firmware. Extraction requires no special privileges.

Who should check

Teams operating FrodoBots EarthRover Mini+ robots on firmware 6.2.4_6.2.5_0.614.0, and owners of the AWS IAM, AWS IoT, Agora and Slack accounts whose credentials are embedded in that firmware.

Not fixed by: Removal of the now-invalidated credential strings from the firmware is still pending.

“FrodoBots EarthRover Mini+ firmware (version 6.2.4_6.2.5_0.614.0)”

kb.cert.org

What to do

Workaround: No workaround is given in the checked facts. Until a fix is confirmed, limit exposure by treating the embedded credentials as compromised and rotating any that are still in use.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-121685 (CVE-2026-121685), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-121685 (entry last updated 2026-11-12):
Affected:
- FrodoBots FrodoBots EarthRover Mini+ firmware: versions 6.2.4_6.2.5_0.614.0
Fix: partial. The advisory says the fix does not fully address the issue.
Conditions (all must be true for the bug to be hit):
- Device runs FrodoBots EarthRover Mini+ firmware version 6.2.4_6.2.5_0.614.0. (source: https://kb.cert.org/vuls/id/188754)
- Credentials are embedded in the publicly downloadable firmware file and can be read by static analysis. (source: https://kb.cert.org/vuls/id/188754)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-121685 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-121685 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.frodobots.ai/
- https://github.com/frodobots-org
- https://kb.cert.org/vuls/id/188754
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-121685
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-121685"}.

Affected versions

cve.now Index

35of 100 · methodology v3
  • Exploitation0/40No signal
  • Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity10/10CVSS 9.8, total technical impact per CISA
  • No patch5/5No fixed version listed; see vendor advisory

What would change the score

  • Would score about 80 if added to CISA KEV
  • Would score about 75 if CISA's SSVC rates exploitation active
  • Would score about 40 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now3 days
  3. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: total

  4. Record last updated
  5. Posted on X by cve.now

Public exploit activity

100%0Posted on X by cve.nowNov 9Nov 22
  • EPSS: 0.61%
  • Posted on X by cve.now Nov 12

Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.

Evidence 5

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
Linkfrodobots.ai · frodobots.ai
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-121685
RecordNVD · CVE-2026-121685
Other links 2
Linkgithub.com · frodobots-org
Linkkb.cert.org · vuls/id/188754

Questions about CVE-2026-121685

Is CVE-2026-121685 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

The FrodoBots EarthRover Mini+ firmware contains hard-coded credentials that can be read from the publicly downloadable firmware file by static analysis. Those credentials cover backend services such as the Agora token service, AWS IAM and IoT MQTT, and a Slack incoming webhook URL, which could allow unauthorized Slack posting and possible misuse of backend infrastructure.

Source: kb.cert.org

Which versions are affected by CVE-2026-121685?

FrodoBots EarthRover Mini+ firmware: version 6.2.4_6.2.5_0.614.0.

Source: cve.now feed data

Am I affected, and how do I check?

The advisory names FrodoBots EarthRover Mini+ firmware version 6.2.4_6.2.5_0.614.0 as affected. To check a device, compare its firmware version against that string in the device's firmware information.

Source: kb.cert.org

How do I fix CVE-2026-121685?

No fixed version or vendor patch is named in the checked facts. Most embedded credentials have reportedly been removed, but the advisory does not list a version to upgrade to.

Source: kb.cert.org

What if there's no patch?

No workaround is given in the checked facts. Until a fix is confirmed, limit exposure by treating the embedded credentials as compromised and rotating any that are still in use.

Source: kb.cert.org

Is the fix complete?

The advisory says most embedded credentials have been removed, which means the fix is partial. The checked facts do not say which credentials, if any, remain in the firmware.

Source: kb.cert.org

No corrections so far. Something wrong on this page? Report an error.