CVE-2022-26845
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 authentication in firmware for Intel(R) AMT before versions 11.8.93, 11.22.93, 11.12.93, 12.0.92, 14.1.67, 15.0.42, 16.1.25 may allow an unauthenticated user to potentially enable escalation of privilege via network access.
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 confidenceImproper authentication in Intel AMT firmware allows unauthenticated network attackers to bypass authentication and gain privileged access to the out-of-band management engine. This gives attackers complete control over the affected system, including the ability to redirect network traffic, deploy malware, or fully compromise the host OS.
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< 11.8.93>= 11.12.0, < 11.12.93>= 11.22.0, < 11.22.93>= 12.0, < 12.0.92>= 14.1, < 14.1.67>= 15.0, < 15.0.42>= 16.1.0, < 16.1.25CVSS 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.
-
Check if Intel AMT is enabled in the systemAccess the system BIOS/UEFI during boot and look for Intel AMT (Intel Active Management Technology) settings under 'Advanced' or 'Security' menus, or check if the Intel Management Engine Interface (MEI) device is present in Device Manager under 'System devices'. On Linux, check if the mei driver is loaded: `lsmod | grep mei` or check for device nodes in /dev/mei* or /sys/class/mei/.Affected if Intel AMT is enabled and the MEI device is present in the system.
-
Determine the Intel AMT firmware versionAccess the Intel AMT web interface by navigating to https://[hostname]:16992 or https://[hostname]:16993 (the default management ports). The login page typically displays the firmware version. Alternatively, on Windows, use the Intel Management Engine Interface (MEI) driver and query via `wmic /namespace:\\root\wmi PATH Intel_AMT_Version` or check the Intel Driver & Support Assistant. On Linux, use the `fwts` tool (firmware test suite) command: `fwts amt -v` or read from /sys/class/mei/*/fw_versions.Affected if The detected version falls within any of these ranges: < 11.8.93; >= 11.12.0 and < 11.12.93; >= 11.22.0 and < 11.22.93; >= 12.0 and < 12.0.92; >= 14.1 and < 14.1.67; >= 15.0 and < 15.0.42; >= 16.1.0 and < 16.1.25.
-
Check network accessibility of AMT interfacesVerify if ports 16992 (HTTP) and 16993 (HTTPS) used by Intel AMT are listening and reachable from the network. Use `netstat -an | findstr "16992 16993"` on Windows or `ss -tlnp | grep -E "16992|16993"` on Linux. If accessible, an unauthenticated remote attacker could exploit the authentication bypass. Confirm if these ports are bound to external network interfaces versus localhost only.Affected if The Intel AMT web interface (ports 16992/16993) is accessible from untrusted network segments.
The system is affected by CVE-2022-26845 if Intel AMT is enabled, the firmware version is within any of the affected ranges listed, and the AMT management interface is network-accessible.
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 · scoped11.8.9311.12.9311.22.93
Update Intel AMT firmware to version 11.8.93, 11.22.93, 11.12.93, 12.0.92, 14.1.67, 15.0.42, 16.1.25 or later. If patching is not immediately feasible, disable Intel AMT or restrict network access to the AMT management interfaces.
Intel AMT firmware version 12.0.92 or later (14.1.67, 15.0.42, 16.1.25 if available for your platform; alternatively 11.22.93, 11.12.93, or 11.8.93 depending on hardware compatibility)
- 1. Identify the current Intel AMT firmware version by accessing the Intel Management Engine (ME) interface or checking via system BIOS information
- 2. Determine the appropriate firmware version for your hardware platform by consulting Intel's compatibility documentation
- 3. Download the corresponding firmware update from Intel's support website (www.intel.com) - look for Intel Management Engine firmware updates specific to your system/model
- 4. Apply the firmware update through one of these methods: Intel Management Engine Interface (MEI) tool, BIOS update that includes AMT firmware, or Intel SCS (Setup and Configuration Software) for enterprise deployment
- 5. After update completion, verify the firmware version has been successfully updated to 11.8.93, 11.12.93, 11.22.93, 12.0.92, or later (14.1.67, 15.0.42, 16.1.25 if available for your platform)
- 6. If AMT is not required in your environment, consider disabling Intel AMT through BIOS settings as an additional mitigation measure
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.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 $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-26845 — 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-2022-26845 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