CVE-2026-121689

waiting for further signalsZero needs more public information before it can validate it.

GHSA-7996-r4fp-7jc4 ↗EUVD-2026-120094 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
FrodoBots EarthRover Mini+ firmware 6.2.4_6.2.5_0.614.0
ETK-2026-3973Zero's internal tracking ID, independent of the CVE number., permanent identifier
8h 01msince last run
8mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+30h10m
0
+2h
+4h
+6h
+8h
+10h

description

EarthRover Mini+ firmware version 6.2.4_6.2.5_0.614.0 can disclose Wi-Fi credentials and system password-hash information. An attacker who can reach its unauthenticated API, diagnostic interface, or ADB service may obtain this sensitive data without logging in.

mitigation

Disable or restrict unauthenticated API, diagnostic, and ADB access to trusted administrators and networks, and rotate the affected Wi-Fi and device credentials. Monitor for a vendor firmware update; no fixed version is recorded.

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
–
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
–
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
8m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-09 16:27Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-11-09 16:27Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-121689

{
  "etk_id": "ETK-2026-3973",
  "cve_id": "CVE-2026-121689",
  "display_id": "CVE-2026-121689",
  "ghsa_id": "GHSA-7996-r4fp-7jc4",
  "euvd_id": "EUVD-2026-120094",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Credential exposure in EarthRover Mini+ firmware",
  "summary": "EarthRover Mini+ firmware version 6.2.4_6.2.5_0.614.0 can disclose Wi-Fi credentials and system password-hash information. An attacker who can reach its unauthenticated API, diagnostic interface, or ADB service may obtain this sensitive data without logging in.",
  "mitigation": "Disable or restrict unauthenticated API, diagnostic, and ADB access to trusted administrators and networks, and rotate the affected Wi-Fi and device credentials. Monitor for a vendor firmware update; no fixed version is recorded.",
  "vendor": "FrodoBots",
  "product": "FrodoBots EarthRover Mini+ firmware",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "6.2.4_6.2.5_0.614.0"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "FrodoBots EarthRover Mini+ firmware",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": null,
  "cvss_src": null,
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 7.74747935,
  "t0_at": "2026-11-09T16:27:03.106000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-09T16:27:03.106000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-09T16:27:03.106000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-121689"
    }
  }
}

published 2026-11-09 16:40Z
last change 2026-11-11 05:12Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.