OpenRemote has authenticated SQL injection in crosstab datapoint exports
Affects OpenRemote versions before 1.26.0 for accounts that can use CSV crosstab datapoint exports. Fixed in 1.26.0.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in 1.26.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
OpenRemote, an open-source internet-of-things platform, is affected by an authenticated SQL injection flaw in its datapoint export feature for CSV crosstab exports. A user who can create or rename assets and export datapoints can inject SQL through asset names, potentially reading database contents returned in the export, including other tenants' data in multi-tenant deployments.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
OpenRemote is an open-source internet-of-things platform. Prior to 1.26.0, the `datapoint export` API constructs `CSV crosstab` SQL by concatenating an `asset name` and `attribute name` into a `COPY` query that uses `crosstab` and streams `TO STDOUT`. The `asset name` enters both a double-quoted column identifier and a category query enclosed by the fixed `$cat$` delimiter. Escaping single quotes in one string context does not escape embedded double quotes in identifiers or protect that dollar-quote boundary. An authenticated user permitted to create or rename an asset and read/export datapoints for one of its attributes can store SQL metacharacters in the name and request a `crosstab` export, causing injected SELECT output to be returned in the normal ZIP/CSV response. This enables database exfiltration without direct database or filesystem access or token forgery. In a multi-tenant deployment it can expose other tenants' data if the manager's database role can read shared tables; integrity and availability effects are not established by the demonstrated read primitive. This issue is fixed in version 1.26.0.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- openremote openremote
fixed in 1.26.0
- io.openremote:openremote-managerMaven
fixed in 1.26.0
References 3
GitHub · openremote/core
Questions about CVE-2026-63224
What does this mean?
An authenticated user can inject SQL into a crosstab datapoint export, and the injected SQL runs through the manager's PostgreSQL connection. The results come back in the CSV/ZIP export, so database data can be read out, possibly including data from other tenants if the database role can read shared tables.Source: github.com
Am I affected, and how do I check?
The listed affected range is versions before 1.26.0 of the openremote product and io.openremote:openremote-manager. The bug requires access to a crosstab datapoint export format (CSV crosstab). To check a setup, look at the OpenRemote manager version in use and whether crosstab datapoint exports are available to the account.Source: github.com
What should I do about it?
Upgrade to OpenRemote 1.26.0 or later, which is the listed fixed version.Source: github.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data