CVE-2026-21657
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 · uneditedImproper Control of Generation of Code ('Code Injection') vulnerability in Johnson Controls Frick Controls Quantum HD allows Code Injection. Insufficient validation of input in certain parameters may permit unexpected actions, which could impact the security of the device before authentication occurs.This issue affects 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 · moderate confidenceA code injection vulnerability exists in Frick Controls Quantum HD version 10.22 and prior due to insufficient validation of input in certain parameters. This allows an attacker to inject malicious code before authentication occurs, potentially giving them full control of the industrial refrigeration control 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 versionAccess the Quantum HD web management interface and navigate to the System Information or About page to retrieve the firmware version number. Alternatively, check the device's status display if available locally.Affected if The firmware version displayed is 10.22 or lower.
-
Locate the management interfaceDetermine the IP address of the Quantum HD device and verify which network ports are listening (typically HTTP on port 80 or HTTPS on port 443). Use a network scanner or check device network configuration.Affected if The web management interface is accessible from the network without restriction.
-
Confirm unauthenticated parameter accessAttempt to access common parameter endpoints or input fields in the web interface without providing credentials. Observe whether the device accepts input before any login prompt appears.Affected if The device accepts input or displays interface elements without requiring authentication first.
-
Review network exposureCheck firewall rules or network segmentation configurations to determine whether the Quantum HD device is directly accessible from untrusted networks or the internet.Affected if The device has no firewall or network isolation protecting its management interface from external access.
The environment is affected if the Quantum HD firmware version is 10.22 or lower and the management interface is network-accessible without proper authentication barriers.
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 · scopedApply vendor patches when available; until then, networkisolate the device behind a firewall, disable unnecessary network exposure, and monitor for anomalous traffic patterns. Coordinate with Johnson Controls for specific hardening guidance.
Fixed firmware version beyond 10.22 (contact Johnson Controls for specific version number)
- 1. Identify the current firmware version of the Frick Controls Quantum HD device
- 2. Contact Johnson Controls technical support or visit the official Johnson Controls product page to obtain the fixed firmware version
- 3. Review all release notes and security advisories associated with the fixed version
- 4. Create a backup of the current device configuration if supported
- 5. Follow the official Johnson Controls firmware update procedure to apply the fixed version
- 6. After upgrade, verify the device is operational and the vulnerability is resolved
- 7. Implement network segmentation and firewall rules to limit exposure to the device if immediate upgrade is not possible
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-21657 — 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-21657 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