OpenRemote before 1.26.2 contains an authentication bypass vulnerability in the console registration API that allows unauthenticated attackers to update existing console assets by supplying a known asset identifier. Attackers can overwrite push notification tokens and console metadata without authentication or ownership validation, redirecting notifications or denying delivery to legitimate consoles.
CVE-2026-66013
This critical-severity CVE scores 9.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 69% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.3
- EG Score
- 9.3(medium)
- EG Risk
- 47(Track)EG Risk 47/100SSVC: Track
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 computedSeverity93% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 31%
- KEV
- Not listed
Published
July 25, 2026
Last Modified
July 25, 2026
Advisory Details (2)
Auto-updated Jul 25, 2026OpenRemote before 1.26.2 Authentication Bypass via Console Registration | Advisories | VulnCheck
https://www.vulncheck.com/advisories/openremote-before-authentication-bypass-via-console-registrationUnauthenticated Console Registration Allows Existing Console Asset Takeover · Advisory · openremote/openremote · GitHub
https://github.com/openremote/openremote/security/advisories/GHSA-gpfc-h59v-63cvVendor Advisories for CVE-2026-66013(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 / 13× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.
- 2026-07-27 02:30 UTCGHSA enrichment
- 2026-07-26 22:21 UTCGHSA enrichment
- 2026-07-26 18:11 UTCEG score recompute
- 2026-07-26 18:11 UTCGHSA enrichment
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 13:50 UTCEG score recompute
- 2026-07-26 13:50 UTCGHSA enrichment
- 2026-07-26 09:43 UTCGHSA enrichment
- 2026-07-26 02:45 UTCEG score recompute
- 2026-07-26 02:45 UTCGHSA enrichment
- 2026-07-25 11:02 UTCEG score recompute
- 2026-07-25 11:01 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-66013?
When was CVE-2026-66013 disclosed?
Is CVE-2026-66013 actively exploited?
What is the CVSS score of CVE-2026-66013?
How do I remediate CVE-2026-66013?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-66013
Is Your Infrastructure Affected by CVE-2026-66013?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.