Quick answers
- Is This vulnerability exploited in the wild?
- No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
- How severe is This vulnerability?
- High severity, with a CVSS score of 8.1, published 23 June 2026.
- Which products and versions are affected?
- io.openremote:openremote-manager (Maven) < 1.25.0.
- Is there a fix for This vulnerability?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is This vulnerability attacked?
- It is attacked over the network, in a hosted service.
- Am I affected?
- Check whether you run io.openremote:openremote-manager (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is an Insecure Direct Object Reference (IDOR) in the bulk alarm deletion endpoint (removeAlarms method in AlarmResourceImpl.java). The vulnerable code verifies that the authenticated user's own realm is active and accessible, but fails to validate that the targeted alarm IDs belong to the caller's realm before deletion. Because alarm IDs are sequential auto-increment values, attackers can enumerate IDs and delete cross-tenant alarm records. The singular removeAlarm() method correctly validates per-alarm realm authorization, but the plural removeAlarms() lacks this check in its underlying JPA queries. An attacker requires only alarm write permissions in their own realm to exploit this flaw and permanently destroy alarms in any other tenant's realm.
Affected products
- OpenRemote Manager < 1.25.0
Timeline
- 2026-06-19: disclosed
- 2026-06-23: advisory
- 2026-09-24: other: Advisory withdrawn as duplicate of GHSA-h3m5-97jq-qjrf