CVE-2026-54640 — OpenRemote: XXE in KNXProtocol.startAssetImport() allows arbitrary file read via unprotected XMLInputFactory
OpenRemote is an open-source internet-of-things platform. Prior to 1.24.2, the KNXProtocol.startAssetImport method in agent/src/main/java/org/openremote/agent/protocol/knx/KNXProtocol.java processes 0.xml from an authenticated user's uploaded ETS project ZIP with Saxon TransformerFactoryImpl and XMLInputFactory parsers that permit external entity resolution. This incomplete remediation of CVE-2026-40882 leaves the KNX handler unprotected while the parallel Velbus handler is hardened, allowing a regular realm user to read files accessible to the JVM process or cause server-side requests. This issue is fixed in version 1.24.2.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+2
- Technical severity (high)+6
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Maven Io.openremote:openremote-agent: fixed in version 1.24.2 — github.com (GitHub Security Advisories)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Io.openremote Openremote-manager, Openremote Openremote, Maven Io.openremote:openremote-agent).
- Apply the fixed version or the patch documented under Remediation.
- Search available logs for exploit probes matching the vulnerability class (injection), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Io.openremote | Openremote-manager | version < 1.24.2 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Openremote | Openremote | version < 1.24.2 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Maven | Io.openremote:openremote-agent | ≤ 1.24.1 | Vulnerable | GitHub Security Advisories |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 7.6 | CVSS 3.1 | High | 2.8 | 4.7 | security-advisories@github.com via NIST National Vulnerability Database |
| 7.6 | CVSS 3.1 | High | — | — | GitHub, Inc. via GitHub Security Advisories |
| 7.6 | CVSS 3.1 | High | — | — | GitHub_M via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L (score shown at the top: security-advisories@github.com) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Look for parameters with command/query metacharacters and unexpected child processes of the service.
Timeline
What happened to this CVE, newest first.
- 2026
- Fix documented
- Affected products added · maven/io.openremote:openremote-agent
- Affected products added · openremote/openremote, io.openremote/openremote-manager
- SSVC assessment updated
- Record published
- CVSS changed · 7.6
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× References added · Oct 13, 2026 – Oct 13, 2026
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
6 on the record
- github.com/openremote/core/security/advisories/GHSA-7v6w-c3f4-9wpq
- github.com/openremote/openremote/commit/c28d3c60ebc2da68d9b6c4a6d7a5ad875a255ee9
- github.com/advisories/GHSA-7v6w-c3f4-9wpq
- github.com/openremote/core/releases/tag/1.24.2
- github.com/openremote/core/commit/c28d3c60ebc2da68d9b6c4a6d7a5ad875a255ee9
- github.com/openremote/openremote/security/advisories/GHSA-7v6w-c3f4-9wpq
Elsewhere on this site
Related CVEs (same products)
- High CVE-2026-54641 OpenRemote: Cross-Realm User Information Disclosure in UserResourceImpl 2d
- High CVE-2026-81679 OpenRemote before 1.28.0 Cross-Realm Information Disclosure via Notification API Aug 27, 2026
- Medium CVE-2026-67310 openremote before 1.27.0 Cross-Tenant IDOR via setAssetLinks Aug 1, 2026
- Medium CVE-2026-65009 OpenRemote before 1.26.2 Information Disclosure via Syslog REST API Jul 21, 2026
- High CVE-2026-62238 OpenRemote < 1.26.0 SQL Injection via Crosstab Export Jul 16, 2026
- High CVE-2026-56784 OpenRemote < 1.25.0 IDOR via Bulk Alarm Deletion Endpoint Jun 23, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-54640 is "OpenRemote: XXE in KNXProtocol.startAssetImport() allows arbitrary file read via unprotected XMLInputFactory", rated High. It affects Openremote-manager (Io.openremote); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.6 describes technical severity. EPSS 0.22% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.