CVE-2026-21658
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 i.e Improper 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 confidenceUnauthenticated Remote Code Execution via Code Injection vulnerability in Johnson Controls Frick Controls Quantum HD version 10.22 and prior. Insufficient validation of input in certain parameters allows injection of malicious code before authentication occurs, enabling arbitrary code execution on 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 device model and firmware versionAccess the Johnson Controls Frick Controls Quantum HD web interface or use SNMP to query the device system information. Look for the firmware version displayed in the device dashboard, about page, or system status. Alternatively, check the device's management console or diagnostic interface for the installed firmware version number.Affected if The installed firmware version is 10.22 or any version lower than 10.22 (e.g., 10.21, 10.20, etc.).
-
Verify if web management interface is enabledConfirm that the Quantum HD device has its web-based management interface (HTTP/HTTPS) enabled and listening on the network. Check device network configuration settings or scan the device IP for open web ports (80, 443, or custom ports).Affected if The web management interface is enabled and accessible over the network.
-
Assess network exposure of management interfaceDetermine whether the device management interface is reachable from network segments outside of a restricted/isolated network. Review firewall rules, ACLs, or network segmentation configurations that control access to the device IP address on the management port.Affected if The management interface is exposed to untrusted networks or allows unauthenticated access from external systems.
-
Identify unauthenticated parameter entry pointsReview the device configuration for web service parameters that can be accessed without authentication. These typically include login forms, query strings, or API endpoints processed before the authentication sequence completes.Affected if The device accepts and processes input through web parameters without requiring authentication credentials first.
A user is affected if the Quantum HD firmware version is 10.22 or lower AND the web management interface is network-accessible without authentication controls.
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.
From vendor dataIsolate the device on a restricted network segment immediately. Apply vendor-supplied firmware update to version 10.23 or later once available. If no patch exists, implement compensating controls such as firewall rules restricting access to the device management interfaces.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-21658 — 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-21658 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