CVE-2022-26837
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 input validation in the BIOS firmware for some Intel(R) Processors may allow a privileged user to potentially enable escalation of privilege via local 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 · moderate confidenceImproper input validation in the BIOS firmware for select Intel processors allows a privileged local user to potentially escalate privileges. This is a firmware-level vulnerability affecting the BIOS, not the operating system, requiring local access to the system.
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 dataall versionsall versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS 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
- Local
- Complexity
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:H/PR:L/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 processor modelRun 'lscpu' on Linux or 'wmic cpu get name' on Windows to retrieve the CPU model name. Look for Intel Xeon Gold model numbers 5317, 5318n, 5318s, 5318y, 5320, 5320t, 6312u, or 6314u.Affected if The CPU model matches any of the affected Xeon Gold numbers listed in the CVE (5317, 5318n, 5318s, 5318y, 5320, 5320t, 6312u, 6314u).
-
Confirm BIOS firmware versionRun 'dmidecode -s bios-version' on Linux or 'wmic bios get smbiosbiosversion' on Windows. Alternatively, access the BIOS setup during boot (press DEL/F2/F12) and locate the BIOS version information.Affected if The system has a BIOS firmware version present (all versions of affected models are vulnerable).
-
Verify system uses BIOS firmwareConfirm the system boots in Legacy BIOS mode or UEFI with BIOS compatibility. Check boot logs or run 'ls /sys/firmware/efi' on Linux (if empty, likely BIOS). On Windows, check 'msinfo32' for BIOS mode.Affected if The system uses BIOS firmware rather than pure UEFI without BIOS (the vulnerability is in BIOS firmware).
-
Assess local access exposureEvaluate whether untrusted local users have physical access or could obtain privileged local account access. Check user permissions, physical security controls, and multi-user configurations.Affected if The system allows local user accounts or physical access to users who are not fully trusted administrators.
If the system contains an Intel Xeon Gold processor matching models 5317, 5318n, 5318s, 5318y, 5320, 5320t, 6312u, or 6314u and runs BIOS firmware, the environment is affected by this CVE.
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 dataApply BIOS firmware updates provided by Intel or the original equipment manufacturer (OEM) for affected processors. Prioritize systems with higher privilege exposure and implement physical access controls to limit local attack surface.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-26837 — 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-26837 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