CVE-2020-26200
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 · uneditedA component of Kaspersky custom boot loader allowed loading of untrusted UEFI modules due to insufficient check of their authenticity. This component is incorporated in Kaspersky Rescue Disk (KRD) and was trusted by the Authentication Agent of Full Disk Encryption in Kaspersky Endpoint Security (KES). This issue allowed to bypass the UEFI Secure Boot security feature. An attacker would need physical access to the computer to exploit it. Otherwise, local administrator privileges would be required to modify the boot loader component.
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 confidenceKaspersky's custom boot loader in Kaspersky Rescue Disk (KRD) insufficiently validated UEFI module authenticity, allowing loading of untrusted modules. This bypassed UEFI Secure Boot and compromised trust in the Authentication Agent of Full Disk Encryption in Kaspersky Endpoint Security (KES).
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= 11.0.0= 11.0.1= 11.1.0< 18.0.11.3CVSS 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
- Physical
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:P/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 Kaspersky Endpoint Security is installedOpen Programs and Features in Windows Control Panel or use 'wmic product get name,version' to list installed softwareAffected if Kaspersky Endpoint Security appears in the installed programs list
-
Verify KES versionRight-click the KES icon in system tray and select 'About', or check the version in Programs and FeaturesAffected if Version is 10, 11.0.0, 11.0.1, or 11.1.0
-
Check if Kaspersky Rescue Disk is usedVerify if KRD has been used on this machine - check for KRD USB sticks or ISO files, or review boot configurationAffected if KRD has been used to boot the system
-
Verify KRD version if presentOpen the KRD ISO or check the version of the KRD media being usedAffected if KRD version is below 18.0.11.3
-
Confirm UEFI Secure Boot statusEnter BIOS/UEFI settings and check Secure Boot is enabled, or run 'msinfo32' and look for 'Secure Boot State'Affected if Secure Boot is enabled and the system uses the affected KES versions with KRD
You are affected if Kaspersky Endpoint Security version 10, 11.0.0, 11.0.1, or 11.1.0 is installed AND Kaspersky Rescue Disk version below 18.0.11.3 has been used to boot the system with UEFI Secure Boot enabled.
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 data18.0.11.3
Apply vendor-supplied updates to the Kaspersky boot loader component; ensure physical security and restrict local administrator access to prevent exploitation.
- Consultation2.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 $5,536.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-26200 — 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-2020-26200 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