CVE-2020-11005: The WindowsHello open source library (NuGet HaemmerElectronics.SeppPenner.WindowsHello), before version 1.0.4,

Q: How do I fix CVE-2020-11005?

windowshello: upgrade to 1.0.4. Exact commands for each OS are on this page.

Q: Is CVE-2020-11005 being exploited?

CVE-2020-11005 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2020-11005 affect?

CVE-2020-11005 affects windowshello. Severity is medium (CVSS 5.1). The WindowsHello open source library (NuGet HaemmerElectronics.SeppPenner.WindowsHello), before version 1.0.4, has a vulnerability where encrypted data could potentially be decrypted without needing authentication. If the library is used to

Q: How urgent is CVE-2020-11005?

Priority 21/100. No elevated risk signals yet.

Routine

MEDIUM 5.1UPGRADE

CVE-2020-11005 is a medium-severity flaw (CVSS 5.1) affecting windowshello. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The WindowsHello open source library (NuGet HaemmerElectronics.SeppPenner.WindowsHello), before version 1.0.4, has a vulnerability where encrypted data could potentially be decrypted without needing authentication. If the library is used to encrypt text and write the output to a txt file, another executable could be able to decrypt the text using the static method NCryptDecrypt from this same library without the need to use Windows Hello Authenti

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	5.1 (Medium)
Attack vector	Local
Attack complexity	High
Privileges needed	None
User interaction	None
EPSS exploit chance	0.2% (top 86%)
CISA exploited list	No
Weakness	CWE-288, CWE-327
Published	2020-04-14
Last modified	2026-06-17

Publisher (CNA): GitHub, Inc. · Vendor: windowshello project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2020-04-14 23:15 UTCPublished CVE record published
2026-06-17 02:48 UTCUpdated Record last modified

windowshello project windowshello UPGRADE

Affected: < 1.0.4

Fixed in: 1.0.4

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy windowshello || rpm -q windowshello || windowshello --version

2. UPGRADE to 1.0.4 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade windowshello

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade windowshello

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2020-11005?

windowshello: upgrade to 1.0.4. Exact commands for each OS are on this page.

Is CVE-2020-11005 being exploited?

CVE-2020-11005 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2020-11005 affect?

CVE-2020-11005 affects windowshello. Severity is medium (CVSS 5.1). The WindowsHello open source library (NuGet HaemmerElectronics.SeppPenner.WindowsHello), before version 1.0.4, has a vulnerability where encrypted data could potentially be decrypted without needing authentication. If the library is used to

How urgent is CVE-2020-11005?

Priority 21/100. No elevated risk signals yet.

Software pages

Windows vulnerabilities

References

← Back to latest CVEs