dbcve.org
Command InjectionWeakness · CWE-77

CVE-2025-26385

CRITICAL · 9.5 CVSS v4.0 Published 2026-01-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Johnson Controls Metasys component listed below have Improper Neutralization of Special Elements used in a Command (Command Injection) Vulnerability . Successful exploitation of this vulnerability could allow remote SQL execution This issue affects  * Metasys: Application and Data Server (ADS) installed with SQL Express deployed as part of the Metasys 14.1 and prior installation,  * Extended Application and Data Server (ADX) installed with SQL Express deployed as part of the Metasys 14.1 installation,  * LCS8500 or NAE8500 installed with SQL Express deployed as part of the Metasys installation Releases 12.0 through 14.1,  * System Configuration Tool (SCT) installed with SQL Express deployed as part of the SCT installation 17.1 and prior,  * Controller Configuration Tool (CCT) installed with SQL Express deployed as part of the CCT installation 17.0 and prior.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Multiple Johnson Controls Metasys components (ADS, ADX, LCS8500, NAE8500, SCT, CCT) deployed with SQL Express contain an improper neutralization of special elements vulnerability enabling command injection, which could allow remote SQL execution. The vulnerability affects versions 12.0 through 14.1 for NAE/LCS, 14.1 and prior for ADS, and 17.1/17.0 and prior for SCT/CCT.

MitigationApply vendor patches when available; alternatively, migrate from SQL Express to a properly hardened full SQL Server instance with least-privilege configurations, or implement network segmentation to limit exposure of affected Metasys components.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Metasys component
    Determine which Metasys component(s) are deployed in your environment: ADS (Application Data Server), ADX (Advanced Application Server), LCS8500/NAE8500 (Network Automation Engine), SCT (System Configuration Tool), or CCT (Commissioning Configuration Tool). Check product documentation or system inventory for the component name.
    Affected if The component is ADS, ADX, LCS8500/NAE8500, SCT, or CCT.
  2. Verify SQL Express deployment
    Confirm whether the Metasys component is configured to use SQL Express as its database backend. This can be verified through the Metasys installation documentation, SQL Server configuration, or by checking the database connection settings in the Metasys administration interface.
    Affected if SQL Express is in use - the vulnerability only affects Metasys deployments using SQL Express.
  3. Determine installed version for ADS/ADX/NAE
    Locate the version information for the Metasys ADS, ADX, or NAE installation. This is typically found in the Metasys UI under System > About, in the Windows Programs and Features list, or in the Metasys server diagnostics. Record the exact version number.
    Affected if The version is 12.0, 12.1, 12.2, 13.0, 13.1, 13.2, 14.0, or 14.1 - any version from 12.0 through 14.1.
  4. Determine installed version for SCT
    Locate the version of the System Configuration Tool (SCT) installed. Check in Windows Programs and Features, or launch SCT and navigate to Help > About to find the version number.
    Affected if The version is 17.1 or any version prior to 17.1.
  5. Determine installed version for CCT
    Locate the version of the Commissioning Configuration Tool (CCT) installed. Check in Windows Programs and Features, or launch CCT and navigate to Help > About to find the version number.
    Affected if The version is 17.0 or any version prior to 17.0.

You are affected if any of these conditions are true: (1) Metasys ADS/ADX/NAE version is 12.0-14.1 and uses SQL Express, (2) SCT version is 17.1 or prior, or (3) CCT version is 17.0 or prior.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patches when available; alternatively, migrate from SQL Express to a properly hardened full SQL Server instance with least-privilege configurations, or implement network segmentation to limit exposure of affected Metasys components.

Have this fixed Scoped from the published advisory
  • Consultation10.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
38.0 hours of engineering $6,800
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,880.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-26385 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-26385 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data