PHP2Shell : See if you’re affected with a free external attack surface scan. Click Here > 

Back
New CVE Detected

CVE-2026-8065 – Authentication Bypass Enabling Arbitrary Firmware Upload – Hitachi Energy RTU500 ser

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-8065 is a critical authentication bypass vulnerability (CVSS 9.1) affecting the firmware update endpoint of Hitachi Energy RTU500 series CMU firmware. An unauthenticated, remote attacker can send a crafted POST request to the update endpoint and upload arbitrary firmware without providing any credentials. Successful exploitation can modify device functionality and compromise the integrity and availability of the remote terminal unit.

Technical details

  • Root cause: The firmware update endpoint on affected RTU500 CMU devices is missing an authentication check (CWE-306, Missing Authentication for Critical Function), allowing unauthenticated requests to reach a function intended for privileged use.
  • Trigger conditions: An attacker crafts a POST request to the firmware update endpoint containing arbitrary firmware content; no valid session, credentials, or prior authentication is required.
  • Attack vector: Network-based (AV:N), low attack complexity (AC:L), no privileges required (PR:N), no user interaction (UI:N).
  • Impact: High impact to integrity and availability of the device (the vulnerability does not affect confidentiality per the CVSS vector). A successful upload of attacker-supplied firmware could alter device behavior, disrupt operation, or render the RTU unavailable — significant given RTU500 units are used for substation automation and remote control in energy/grid environments.
  • Related weakness: Mapped to CAPEC-638 (Altered Component Firmware).

Affected software

  • Hitachi Energy RTU500 series CMU firmware, versions 9.0 up to (but not including) 12.0

Severity

  • CVSS v3.1 Base Score: 9.1 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H

Mitigation and recommended actions

  • Immediate: Upgrade affected RTU500 series CMU firmware to version 12.0 or later, and consult Hitachi Energy’s cybersecurity advisory (document 8DBD000251) for the exact release and update procedure for your device configuration.
  • If patching cannot be performed immediately:
    • Restrict network access to the RTU500 management/firmware-update interface to trusted management networks only, using firewalls, VPNs, or network segmentation.
    • Ensure RTU500 devices are not directly exposed to the public internet.
    • Monitor for unexpected firmware update requests or unplanned firmware changes on affected devices.
    • Follow general ICS network hardening guidance (e.g., isolating OT networks from IT/corporate networks and the internet) until the firmware update is applied.

References

Are you exposed?

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

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

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

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

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

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge