CVE-2026-21659
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 · uneditedUnauthenticated Remote Code Execution and Information Disclosure due to Local File Inclusion (LFI) vulnerability in Johnson Controls Frick Controls Quantum HD allow an unauthenticated attacker to execute arbitrary code on the affected device, leading to full system compromise. This issue affects Frick Controls Quantum HD: Frick Controls Quantum HD version 10.22 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 confidenceUnauthenticated Local File Inclusion (LFI) vulnerability in Johnson Controls Frick Controls Quantum HD version 10.22 and prior allows remote attackers to execute arbitrary code and disclose sensitive information without any authentication, resulting in full system compromise of the affected device.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 10.22CVSS 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
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify the firmware version of the Johnson Controls Frick Controls Quantum HD deviceAccess the device management interface or use the vendor-provided method to retrieve the current firmware version. This is typically found in the system information or about section of the web interface, or via CLI commands documented in the device manual.Affected if The installed firmware version is 10.22 or any version prior to 10.22.
-
Verify if the web management interface is exposed to untrusted networksReview network firewall rules and device network configuration to determine if the Quantum HD web interface (typically HTTP/HTTPS on ports 80 or 443, or vendor-specified ports) is accessible from outside the trusted internal network.Affected if The web interface is directly accessible from untrusted networks such as the internet or guest networks without VPN or firewall filtering.
-
Test for unauthenticated access to file inclusion endpointsUsing a web proxy or curl command, attempt to access common LFI payload patterns on the web interface without providing any authentication credentials. Example patterns include accessing paths that traverse to system files such as /etc/passwd or device configuration files.Affected if The device returns file contents or sensitive configuration data without requiring any login credentials.
-
Confirm the service accepting unauthenticated requests is the Quantum HD firmware serviceVerify that the exposed service responding to unauthenticated requests is indeed the Johnson Controls Frick Controls Quantum HD application and not a third-party component, by examining response headers, banner information, or the URL structure.Affected if The unauthenticated LFI test targets the Quantum HD firmware web interface specifically.
The environment is affected if the Johnson Controls Frick Controls Quantum HD firmware version is 10.22 or prior AND the web interface is accessible without authentication from an untrusted network.
Generated from the published advisory. Verify against your own configuration.
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.
dbcve · scopedIsolate affected devices from untrusted networks immediately and upgrade to a version beyond 10.22 when available; if upgrade is not immediately possible, implement network segmentation and monitor for indicators of compromise.
Contact Johnson Controls for the fixed firmware version (newer than 10.22)
- Contact Johnson Controls customer support or visit the official Johnson Controls security advisory page at johnsoncontrols.com to obtain the latest firmware version for Frick Controls Quantum HD
- Verify with the vendor that the obtained version includes the fix for CVE-2026-21659 (LFI leading to unauthenticated RCE)
- Schedule a maintenance window for the firmware update process
- Follow the vendor's official firmware update procedure for Quantum HD devices
- After updating, verify the device is operational and the vulnerability is remediated
- Check CISA advisories (cisa.gov) for any additional guidance or indicators of compromise
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation10.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-21659 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-21659 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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