dbcve.org
Reb500 FirmwareOperating system · Hitachienergy

CVE-2026-2460

HIGH · 8.1 CVSS v3.1 Published 2026-02-24
Fix available
A fix is available. Upgrade to 8.3.3.1 or later.
See remediation →
87/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability exists in REB500 for an authenticated user with low-level privileges to access and alter the content of directories by using the DAC protocol that the user is not authorized to do so.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The REB500 product contains an authorization bypass vulnerability in its DAC (Discretionary Access Control) protocol implementation. An authenticated user with low-level privileges can exploit this flaw to access and modify directory contents that they are not authorized to access, effectively escalating their privileges beyond what the access control system permits.

MitigationRemediate by implementing proper authorization validation within the DAC protocol to enforce directory access controls based on user privilege levels. Verify that all directory access requests are validated against the user's actual authorization permissions before allowing access or modification.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Reb500 FirmwareOperating system
Affected:< 8.3.3.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed REB500 firmware version
    Access the REB500 device management interface or use the firmware version display command (typically via CLI or web interface). Locate the firmware version number in the system information or about section.
    Affected if The installed firmware version is lower than 8.3.3.1 (e.g., 8.2.x, 8.1.x, etc.)
  2. Confirm DAC protocol is enabled
    Locate the DAC (Discretionary Access Control) protocol configuration settings within the REB500 management interface or configuration files. Verify that the DAC protocol module is currently active/enabled.
    Affected if The DAC protocol is enabled and the firmware version is below 8.3.3.1
  3. Review user privilege assignments
    Access the user management or access control panel in the REB500 interface. Identify users who have been assigned low-level or restricted privileges within the DAC system.
    Affected if Low-privilege users exist in the system and the DAC protocol is enabled with firmware below 8.3.3.1
  4. Inspect directory access control configurations
    Examine the DAC directory access control rules or permissions matrix. Check which directories have access restrictions and verify how these restrictions are mapped to user privilege levels.
    Affected if Directory access controls are defined and low-privilege users could potentially bypass these restrictions due to the vulnerability

A system is affected if it runs REB500 firmware version below 8.3.3.1 with the DAC protocol enabled and low-privilege users present in the environment.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 8.3.3.1 or later
Fixed in 8.3.3.1
Interim mitigation

Remediate by implementing proper authorization validation within the DAC protocol to enforce directory access controls based on user privilege levels. Verify that all directory access requests are validated against the user's actual authorization permissions before allowing access or modification.

Recommended fix Moderate confidence

Reb500 Firmware 8.3.3.1 or later

  1. Contact Hitachi Energy technical support to obtain the firmware version 8.3.3.1 or later
  2. Follow the official REB500 firmware upgrade procedure provided in the product documentation
  3. Verify the upgrade was successful by confirming the firmware version
  4. Ensure the upgrade is performed during a planned maintenance window per operational procedures

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Reb500 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-2460 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-2460 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data