Quick answers
- Is CVE-2026-63224 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-63224 being exploited in the wild.
- How severe is CVE-2026-63224?
- Informational severity, published 30 October 2026.
- Which products and versions are affected?
- OpenRemote before 1.26.0.
- Is there a fix for CVE-2026-63224?
- Yes: fixed in 1.26.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-63224 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-63224?
- Check whether you run OpenRemote 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.
How to fix
- Fixed in: 1.26.0
Technical details
The datapoint export API constructs a PostgreSQL crosstab query by concatenating unsanitized asset and attribute names into a COPY statement with dollar-quote delimiters. Although single quotes are escaped in one context, double quotes in identifiers and the dollar-quote boundaries are not protected, enabling SQL injection. An authenticated user with asset creation/rename and datapoint read/export permissions can store SQL metacharacters in asset names and trigger a crosstab export to exfiltrate arbitrary SELECT query results in the ZIP/CSV response.
Affected products
- OpenRemote OpenRemote before 1.26.0
Timeline
- 2026-10-30: disclosed
- 2026-06-30: patched