dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-56784

HIGH · 8.1 CVSS v3.1 Published 2026-06-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
OpenRemote before 1.25.0 contains an insecure direct object reference (IDOR) vulnerability in the bulk alarm deletion endpoint that allows authenticated users to permanently delete alarms belonging to other tenants by supplying arbitrary alarm IDs. The removeAlarms() method in AlarmResourceImpl.java omits realm-scoping validation in its JPA query, enabling any user with alarm-write permissions to enumerate sequential auto-increment alarm IDs and delete cross-tenant alarm records without authorization.

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

OpenRemote before 1.25.0 has an IDOR vulnerability in the bulk alarm deletion endpoint. The removeAlarms() method in AlarmResourceImpl.java fails to include realm-scoping validation in its JPA query, allowing authenticated users with alarm-write permissions to delete alarms from other tenants by supplying arbitrary sequential auto-increment alarm IDs.

MitigationUpgrade to OpenRemote 1.25.0 or later which includes proper realm-scoping validation in the alarm deletion JPA query to enforce tenant isolation.

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

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 OpenRemote installation and version
    Locate the OpenRemote installation directory and check the version manifest or pom.xml file. Common locations include /opt/openremote or the application deployment directory. Look for version.txt, pom.xml, or the WAR file version.
    Affected if The installed version is before 1.25.0 (e.g., 1.24.x, 1.23.x, or any version prior to 1.25.0)
  2. Verify the AlarmResourceImpl.java component exists
    Locate the AlarmResourceImpl.java file in the deployed application source or decompiled classes. This file should exist in the Java source under the alarm resource package path.
    Affected if The vulnerable removeAlarms() method is present in the codebase and the application is running a version before 1.25.0
  3. Confirm REST API endpoints are exposed
    Check the OpenRemote deployment configuration to confirm the REST API is accessible. Verify that HTTP/HTTPS endpoints for alarm operations are enabled and reachable.
    Affected if The REST API endpoints are publicly or internally accessible without additional network restrictions
  4. Validate user authentication is enabled
    Review the OpenRemote security configuration to confirm user authentication is active. Check that users must authenticate to access alarm-related REST endpoints.
    Affected if Users can authenticate to the system and obtain session tokens for API access
  5. Audit alarm-write permission assignments
    Review user roles and permissions in the OpenRemote admin console or user database. Identify which authenticated users or service accounts have alarm-write permissions granted.
    Affected if Authenticated users possess alarm-write permissions, enabling them to access the vulnerable removeAlarms() endpoint

A user is affected if running OpenRemote version before 1.25.0 with exposed REST API, enabled authentication, and users granted alarm-write permissions that could exploit the realm-scoping gap in the removeAlarms() method.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to OpenRemote 1.25.0 or later which includes proper realm-scoping validation in the alarm deletion JPA query to enforce tenant isolation.

Recommended fix High confidence

OpenRemote 1.25.0 or latest stable release

  1. 1. Backup your OpenRemote installation and database before proceeding with any changes.
  2. 2. Identify your current OpenRemote version by checking the deployment configuration or Docker image tag.
  3. 3. If running a version before 1.25.0, plan the upgrade to version 1.25.0 or later.
  4. 4. For Docker-based deployments: Update your docker-compose.yml or image reference to use the OpenRemote 1.25.0 image or the latest stable release.
  5. 5. For non-Docker deployments: Download and install OpenRemote version 1.25.0 or the latest stable release from the official repository.
  6. 6. Run database migrations if required by the upgrade process.
  7. 7. Verify the upgrade was successful by checking the OpenRemote web interface and confirming the version number.
  8. 8. Test alarm creation and deletion functionality to ensure the realm-scoping fix is working correctly.
Caveat Review release notes for 1.25.0 to check for any breaking changes related to alarm management or API modifications

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-56784 — 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-56784 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