PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-81679 openremote CVE debrief

CVE-2026-81679 is a high-severity vulnerability in OpenRemote versions before 1.28.0, allowing cross-realm information disclosure via the Notification REST API. Attackers with read:admin credentials in one realm can access sensitive notification metadata and message content from all realms. This vulnerability has significant implications for the security of OpenRemote instances, as it could allow unauthorized access to sensitive information. Defenders should prioritize verifying exposure and remediating vulnerable instances.

Vendor
openremote
Product
Unknown
CVSS
HIGH 8.3
CISA KEV
Not listed in stored evidence
Original CVE published
2026-08-27
Original CVE updated
2026-09-23
Advisory published
2026-08-27
Advisory updated
2026-09-23

Who should care

Defenders and administrators of OpenRemote instances should assess exposure and prioritize remediation. This includes reviewing instance versions, restricting access to the Notification REST API, and monitoring for suspicious activity. Additionally, security teams and vulnerability management teams should be aware of the potential risks and take necessary steps to mitigate them.

Why it matters

CVE-2026-81679 is a high-severity vulnerability in OpenRemote versions before 1.28.0, allowing cross-realm information disclosure via the Notification REST API. Defenders should prioritize verifying exposure and remediating vulnerable instances.

  • Defenders must verify OpenRemote instance versions and exposure to the vulnerability.
  • Successful exploitation allows attackers to access sensitive notification metadata and message content from all realms.
  • Defenders should restrict access to the Notification REST API and monitor for suspicious activity.
  • Remediation priority is high due to the potential for sensitive information disclosure.

Technical summary

The vulnerability allows per-realm tenant administrators to read all tenants' sent notifications, including message bodies, via a zero-parameter GET request to the notification endpoint. This is possible due to a lack of proper access controls in the Notification REST API of OpenRemote versions before 1.28.0. The vulnerability has a CVSS score of 8.3 and is considered high-severity. It is essential for defenders to understand the technical details of the vulnerability to assess exposure and prioritize remediation effectively.

Defensive priority

Defenders should prioritize verifying exposure and remediating vulnerable OpenRemote instances.

Recommended defensive actions

  • Verify OpenRemote instance version and exposure to the vulnerability
  • Restrict access to the Notification REST API
  • Upgrade to OpenRemote version 1.28.0 or later
  • Monitor for suspicious activity on the Notification REST API
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The vulnerability is described in the CVE record and NVD entry. OpenRemote versions before 1.28.0 are affected. The Notification REST API allows per-realm tenant administrators to read all tenants' sent notifications.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-81679 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-81679

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-81679 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-81679

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.