CVE-2026-10557

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-06-12. A secondary CVSS source baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this week
9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 9.8Exploit: None knownExposed services: Not assessed

Yarbo recommends users update the Yarbo mobile app to 3.17.4 or later (from the CVE record's solution, Cybersecurity and Infrastructure Security Agency (CISA) Industrial Control Systems (ICS)) — apply it.

The Yarbo Android and iOS applications contain hard-coded MQTT broker credentials that are identical for all users and all devices. These credentials are embedded in the application binary and are readily extractable via APK decompilation. The credentials provide access to cloud MQTT brokers carrying real-time telemetry for the entire global Yarbo robot fleet. They allow both wildcard subscription to all robot telemetry topics and publishing to any robot's command topic using only the robot's serial number.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
59
EG Risk 59/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
The EG Score, 9.8 of 10.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: Yarbo recommends users update the Yarbo mobile app to 3.17.4 or later (from the CVE record's solution, Cybersecurity and Infrastructure Security Agency (CISA) Industrial Control Systems (ICS)). Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
27th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

Yarbo recommends users update the Yarbo mobile app to 3.17.4 or later (from the CVE record's solution, Cybersecurity and Infrastructure Security Agency (CISA) Industrial Control Systems (ICS)). Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 12, 2026

Last Modified

June 12, 2026

Advisory Details (2)

Auto-updated Oct 8, 2026
Fix named in the CVE record's solution (Cybersecurity and Infrastructure Security Agency (CISA) Industrial Control Systems (ICS)). Sources: cisa.
CISA

Yarbo Android/iOS Mobile Application and Cloud Infrastructure | CISA

https://www.cisa.gov/news-events/ics-advisories/icsa-26-162-01
Web page

CSAF/csaf_files/OT/white/2026/icsa-26-162-01.json at develop · cisagov/CSAF · GitHub

https://github.com/cisagov/CSAF/blob/develop/csaf_files/OT/white/2026/icsa-26-162-01.json

Vendor Advisories for CVE-2026-10557(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 13× in last 7d / 29× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 443 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 343 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-12 23:06 UTCGHSA enrichmentGHSA-65ch-m8fq-jhr5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  2. 2026-10-12 16:39 UTCEG score recompute
  3. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  4. 2026-10-12 09:52 UTCGHSA enrichmentGHSA-65ch-m8fq-jhr5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  5. 2026-10-11 20:15 UTCEG score recompute
  6. 2026-10-11 18:27 UTCEG score recompute
  7. 2026-10-11 15:01 UTCEG score recompute
  8. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  9. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  10. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  11. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  12. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  13. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  14. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  15. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  16. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  17. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  18. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  19. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  20. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  21. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  22. 2026-09-23 13:47 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  23. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  24. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  25. 2026-09-16 05:14 UTCEPSS rescoreEPSS 0.4% · 28th percentile
Show 75 more
  1. 2026-09-14 08:15 UTCGHSA enrichmentGHSA-65ch-m8fq-jhr5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  2. 2026-09-14 04:01 UTCEG score recompute
  3. 2026-09-14 04:00 UTCGHSA enrichmentGHSA-65ch-m8fq-jhr5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  4. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  5. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  6. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  7. 2026-09-11 09:36 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  8. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  9. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  10. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  11. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  12. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  13. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  14. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  15. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  16. 2026-08-30 23:44 UTCEG score recompute
  17. 2026-08-30 23:44 UTCGHSA enrichmentGHSA-65ch-m8fq-jhr5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  18. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  19. 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  20. 2026-08-28 21:40 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  21. 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  22. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  23. 2026-08-25 03:59 UTCGHSA enrichmentGHSA-65ch-m8fq-jhr5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  24. 2026-08-24 23:50 UTCEG score recompute
  25. 2026-08-24 23:50 UTCGHSA enrichmentGHSA-65ch-m8fq-jhr5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  26. 2026-08-23 23:21 UTCGHSA enrichmentGHSA-65ch-m8fq-jhr5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  27. 2026-08-23 18:26 UTCGHSA enrichmentGHSA-65ch-m8fq-jhr5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  28. 2026-08-23 14:16 UTCGHSA enrichmentGHSA-65ch-m8fq-jhr5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  29. 2026-08-23 10:06 UTCEG score recompute
  30. 2026-08-23 10:06 UTCGHSA enrichmentGHSA-65ch-m8fq-jhr5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  31. 2026-08-21 23:48 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  32. 2026-08-21 23:33 UTCGHSA enrichmentGHSA-65ch-m8fq-jhr5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  33. 2026-08-21 19:13 UTCGHSA enrichmentGHSA-65ch-m8fq-jhr5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  34. 2026-08-21 14:56 UTCGHSA enrichmentGHSA-65ch-m8fq-jhr5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  35. 2026-08-21 10:47 UTCGHSA enrichmentGHSA-65ch-m8fq-jhr5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  36. 2026-08-21 06:35 UTCGHSA enrichmentGHSA-65ch-m8fq-jhr5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  37. 2026-08-21 00:58 UTCEG score recompute
  38. 2026-08-21 00:58 UTCGHSA enrichmentGHSA-65ch-m8fq-jhr5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  39. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  40. 2026-08-20 20:48 UTCGHSA enrichmentGHSA-65ch-m8fq-jhr5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  41. 2026-08-20 16:30 UTCGHSA enrichmentGHSA-65ch-m8fq-jhr5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  42. 2026-08-20 08:47 UTCEG score recompute
  43. 2026-08-20 08:47 UTCGHSA enrichmentGHSA-65ch-m8fq-jhr5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  44. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  45. 2026-08-19 13:45 UTCEG score recompute
  46. 2026-08-19 13:45 UTCGHSA enrichmentGHSA-65ch-m8fq-jhr5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  47. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  48. 2026-08-17 15:33 UTCEG score recompute
  49. 2026-08-17 15:33 UTCGHSA enrichmentGHSA-65ch-m8fq-jhr5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  50. 2026-08-17 11:20 UTCGHSA enrichmentGHSA-65ch-m8fq-jhr5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  51. 2026-08-17 07:10 UTCGHSA enrichmentGHSA-65ch-m8fq-jhr5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  52. 2026-08-17 03:01 UTCGHSA enrichmentGHSA-65ch-m8fq-jhr5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  53. 2026-08-16 22:52 UTCGHSA enrichmentGHSA-65ch-m8fq-jhr5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  54. 2026-08-16 16:18 UTCEG score recompute
  55. 2026-08-16 16:18 UTCGHSA enrichmentGHSA-65ch-m8fq-jhr5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  56. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  57. 2026-08-16 12:06 UTCGHSA enrichmentGHSA-65ch-m8fq-jhr5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  58. 2026-08-16 07:57 UTCGHSA enrichmentGHSA-65ch-m8fq-jhr5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  59. 2026-08-16 03:48 UTCEG score recompute
  60. 2026-08-16 03:48 UTCGHSA enrichmentGHSA-65ch-m8fq-jhr5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  61. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  62. 2026-08-15 23:39 UTCGHSA enrichmentGHSA-65ch-m8fq-jhr5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  63. 2026-08-15 18:53 UTCGHSA enrichmentGHSA-65ch-m8fq-jhr5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  64. 2026-08-15 14:44 UTCGHSA enrichmentGHSA-65ch-m8fq-jhr5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  65. 2026-08-15 10:34 UTCGHSA enrichmentGHSA-65ch-m8fq-jhr5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  66. 2026-08-15 03:17 UTCEG score recompute
  67. 2026-08-15 03:17 UTCGHSA enrichmentGHSA-65ch-m8fq-jhr5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  68. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  69. 2026-08-14 23:08 UTCGHSA enrichmentGHSA-65ch-m8fq-jhr5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  70. 2026-08-14 18:59 UTCGHSA enrichmentGHSA-65ch-m8fq-jhr5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  71. 2026-08-14 14:49 UTCGHSA enrichmentGHSA-65ch-m8fq-jhr5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  72. 2026-08-14 10:40 UTCGHSA enrichmentGHSA-65ch-m8fq-jhr5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  73. 2026-08-14 06:31 UTCGHSA enrichmentGHSA-65ch-m8fq-jhr5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  74. 2026-08-14 02:21 UTCGHSA enrichmentGHSA-65ch-m8fq-jhr5 · GitHub severity CRITICAL · GitHub CVSS 9.8
  75. 2026-08-13 22:12 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-10557?
CVE-2026-10557 is a critical-severity vulnerability; its CVE record was published on June 12, 2026. The Yarbo Android and iOS applications contain hard-coded MQTT broker credentials that are identical for all users and all devices. These credentials are embedded in the application binary and are readily extractable via APK decompilation. The credentials provide access to cloud MQTT brokers…
When was CVE-2026-10557 made public?
CVE-2026-10557 was made public on June 11, 2026: that is the date its CVE record's CNA, Cybersecurity and Infrastructure Security Agency (CISA) Industrial Control Systems (ICS), gives for when the vulnerability was made public. The CVE record itself was published on June 12, 2026. EchelonGraph's copy of the record carries a last-modified date of June 12, 2026; the record at its source may have been updated since.
Is CVE-2026-10557 actively exploited?
CVE-2026-10557 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (27th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-10557?
CVE-2026-10557 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-10557?
The CVE record's solution for CVE-2026-10557, written by its CNA Cybersecurity and Infrastructure Security Agency (CISA) Industrial Control Systems (ICS), names the fix: "Yarbo recommends users update the Yarbo mobile app to 3.17.4 or later." The vendor advisories EchelonGraph has for CVE-2026-10557 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-10557

Explore →

Is Your Infrastructure Affected by CVE-2026-10557?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.