Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-66013 – Authentication Bypass – OpenRemote before 1.26.2

Be the first to know when new zero-days emerge:

Summary

CVE-2026-66013 is a critical authentication bypass vulnerability (CVSS 4.0: 9.3) in OpenRemote, an open-source enterprise IoT platform. The flaw resides in the public console registration API, which performs no authentication, ownership validation, or realm verification when updating an existing console record — allowing unauthenticated remote attackers to overwrite any console asset by supplying a known asset identifier. All OpenRemote releases prior to version 1.26.2 are affected.

Technical details

  • Root cause: The console registration endpoint treats console asset IDs as authorization credentials rather than object references (CWE-639: Authorization Bypass Through User-Controlled Key; CWE-862: Missing Authorization). The API lacks authentication requirements, ownership checks, realm matching, and re-registration secrets, so possession of a console asset ID alone is sufficient to authorize arbitrary mutations to that asset.
  • Trigger condition: An attacker must obtain a valid console asset ID, which may be exposed via client-side storage, application logs, network traffic, or URLs — common in IoT deployment scenarios.
  • Attack vector: Fully network-accessible (AV:N) with no credentials required (PR:N), no user interaction (UI:N), low attack complexity (AC:L), and no attack prerequisites (AT:N).
  • Impact: An attacker can overwrite push notification tokens and console provider metadata for any known console asset, redirecting or suppressing operational alerts sent to legitimate consoles. Multi-tenant deployments are particularly at risk due to global asset lookup without realm scoping, enabling cross-tenant console takeover.

Affected software

  • OpenRemote all versions ≤ 1.26.1

Severity

  • CVSS 4.0 Base Score: 9.3 (Critical)
  • Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N

Mitigation and recommended actions

  • Immediate: Upgrade to OpenRemote version 1.26.2, which was confirmed by the vendor to address unauthenticated console registration by introducing proper authentication requirements, ownership verification, and realm validation for console re-registration scenarios.
  • If immediate patching is not feasible, restrict network-level access to OpenRemote Manager API endpoints from untrusted or external networks, and monitor for anomalous or unexpected console registration requests.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge