CVE-2026-106087

waiting for further signalsZero needs more public information before it can validate it.

GHSA-5xj2-3wq5-8chm ↗EUVD-2026-110818 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
Hitachi Energy TRO600 Series Firmware >= 9.0.0.0, <= 9.1.1.0
CWE-306 Missing Authentication for Critical Function
ETK-2026-2756Zero's internal tracking ID, independent of the CVE number., permanent identifier
2h 11msince last run
22mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+0h49m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

TRO600 Series Firmware is affected by an unauthenticated arbitrary file-read vulnerability. A remote attacker able to reach an affected device may retrieve sensitive files, including configuration and password data, without logging in.

mitigation

Restrict network access to affected TRO600 devices to trusted administrative networks and isolate them from untrusted networks. Monitor vendor advisories for a firmware update, as no fixed version is recorded.

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
22m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-27 11:56Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-27 11:56Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-106087

{
  "etk_id": "ETK-2026-2756",
  "cve_id": "CVE-2026-106087",
  "display_id": "CVE-2026-106087",
  "ghsa_id": "GHSA-5xj2-3wq5-8chm",
  "euvd_id": "EUVD-2026-110818",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unauthenticated arbitrary file read in TRO600 firmware",
  "summary": "TRO600 Series Firmware is affected by an unauthenticated arbitrary file-read vulnerability. A remote attacker able to reach an affected device may retrieve sensitive files, including configuration and password data, without logging in.",
  "mitigation": "Restrict network access to affected TRO600 devices to trusted administrative networks and isolate them from untrusted networks. Monitor vendor advisories for a firmware update, as no fixed version is recorded.",
  "vendor": "Hitachi Energy",
  "product": "TRO600 Series Firmware",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 9.0.0.0, <= 9.1.1.0"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "TRO600 Series Firmware",
      "purl": null
    }
  ],
  "cwes": [
    306
  ],
  "cvss_score": 8.7,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 22.202032183333333,
  "t0_at": "2026-10-27T11:56:54.738000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-27T11:56:54.738000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-27T11:56:54.738000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-106087"
    }
  }
}

published 2026-10-27 12:23Z
last change 2026-10-27 14:18Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.