OT/ICSCritical 9.1
CVE-2026-8065
Unauthenticated firmware upload in Hitachi RTU500 enables device takeover
How scary is it?
updated 21 Nov 2026- Yes
Works without logging in1
No account and no user action needed (CVSS PR:N, UI:N).
- Yes
Reachable over the network1
Can be attacked remotely (CVSS AV:N).
- Yes
Proof-of-concept code is public2
1 GitHub proof of concept. GitHub proofs of concept are unvetted: some are fake or carry malware. No Exploit-DB entry or Metasploit exploit module on record.
- None known
Attacks seen in the wild1
None reported that we know of. CISA's SSVC assessment says exploitation: none.
- No
On CISA's exploited list3
Not in the catalog as of our last sync.
Scare-o-meter
Act this week
Serious and within reach of attackers. Schedule the fix this week.
- Low signal
- Routine patch
- Act this week
- Drop everything
Why: Reachable over the network with no login and no user action; CVSS 9.1.1 Read from the same rule that decides our alert emails.
Are you affected? only if all are true
You run Hitachi Energy RTU500 series CMU firmware in an affected version>= 9.0 and < 12.0
The CVE record states no fixed release.
As published in the CVE record. A version outside these ranges is not a statement that it is unaffected: vendors sometimes understate a range, and distribution builds with backported fixes keep the upstream number.
See the affected products table · Source 1
An attacker can reach it over the network
CVSS attack vector: Network (AV:N). Reachable over the internet or any routable network.
Source 1
Read from the CVE record: affected versions and the CVSS vector. It narrows things down. It does not prove you are safe.
What to do
Recommendation, AI-writtenIsolate affected RTUs, apply vendor mitigations, replace EOL units, monitor logs
Written by a language model from the CVE record. It is not the vendor's wording: check it against the sources.
Steps marked AI were written by a language model, from the CVE record or from the linked news pages. They are not the vendor's wording: check them against the sources.
Major vulnerability. Unauthenticated firmware upload in Hitachi RTU500 (OT/ICS) enables device takeover and potential disruption of critical infrastructure (energy/transport), warranting broad alerting.
- CVSS
- 9.1Criticalscored by the publisher (CNA)
- Exploited in the wild
- Not knownUnvetted proof-of-concept code on GitHub; not in CISA KEV
- EPSS
- 0.49%chance of exploitation in the next 30 daystop 57% of scored CVEsFIRST score of 21 Nov 2026
- Fix
- Not stated by the vendorno fixed release in the CVE record
- Published
- 29 Sept 2026analysed here 30 Sept 2026
Summary
Impact
Unauthenticated POST to firmware endpoint allows arbitrary firmware upload → full device compromise, remote code execution, integrity loss, and service disruption.
Triage
The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.
Affected products
| Product | Affected versions | Vendor says fixed in |
|---|---|---|
| Hitachi Energy RTU500 series CMU firmware | >= 9.0 and < 12.0Vendor says fixed in: not stated |
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
Products named in our analysis
- Hitachi Energy RTU500 (end-of-life firmware versions)
Fix and mitigation
Action required
Immediate action required
WAF and other mitigations
Can a WAF block it? No. A function is missing its authentication check. The attack requests look like normal traffic, so a WAF has nothing to match on.
Also consider: patch
Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Remediation steps (AI-written)
Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.
Exploitation evidence
- CISA KEV catalog
- Not listed as of our last sync.
- Public exploit code
- Unvetted proof-of-concept code on GitHub: 1 GitHub proof of concept
- CISA SSVC
- exploitation none, automatable yes, technical impact partialAssessed by CISA 29 Sept 2026 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.
GitHub proofs of concept
- murrez/CVE-2026-80650 stars
Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.
Timeline
- 29 Sept 2026First proof-of-concept repository on GitHub (unvetted)
- 29 Sept 2026Publishedsame day later
- 29 Sept 2026CISA SSVC assessment: exploitation nonesame day later
- 29 Sept 2026CVE record last updatedsame day later
- 30 Sept 2026Analysed by vulneraibility.com1 day later
Common questions
Is CVE-2026-8065 being exploited?
Not confirmed. CVE-2026-8065 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.49% probability of exploitation in the next 30 days.
How severe is CVE-2026-8065?
CVE-2026-8065 is rated Critical with a CVSS score of 9.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-8065?
Not known from our data. No patch reference has been recorded for CVE-2026-8065, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-8065 affect?
CVE-2026-8065 affects Hitachi Energy RTU500 (end-of-life firmware versions). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-8065?
Isolate affected RTUs, apply vendor mitigations, replace EOL units, monitor logs
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
References
1 reference in the CVE record, grouped by the tags the record gives them.
Other links (1)
- publisher.hitachienergy.com /preview?DocumentID=8DBD000251&LanguageCode=en&DocumentPartId=&Action=Launch
Where the data on this page comes from
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- PoC-in-GitHub: GitHub repositories that claim a proof of concept
Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.
Similar CVEs
Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.