Internal NCryptDecrypt method could be used externally from WindowsHello library.

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.1 · CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS

• CVE-2020-11005: 0.23% estimated exploitation activity in the next 30 days; percentile 14.40 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact Every user of the library before version 1.0.4. Patches Patched in 1.0.4+. Workarounds None. References https://github.com/SeppPenner/WindowsHello/issues/3 For more information It this 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 Authentication again.

Published by the source

14 Apr 2020, 23:09 UTC

Last modified by the source

9 Jan 2023, 05:02 UTC

Source last checked

26 Oct 2026, 16:58 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-wvpv-ffcv-r6cw

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2020-11005

Advisory: Internal NCryptDecrypt method could be used externally from WindowsHello library.
IDs: CVE-2020-11005, GHSA-wvpv-ffcv-r6cw
Record: https://patchnext.com/advisories/cve-2020-11005 (revision 1, source checked 26 Oct 2026, 16:58 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: haemmerelectronics.sepppenner.windowshello 1.0.4. A vendor fix does not mean a deployment is fixed.

## Affected components
- NuGet haemmerelectronics.sepppenner.windowshello: affected < 1.0.4; fixed in 1.0.4

## Suggested inspection (read-only)
- NuGet haemmerelectronics.sepppenner.windowshello: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on haemmerelectronics.sepppenner.windowshello.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-wvpv-ffcv-r6cw (GitHub-reviewed advisory GHSA-wvpv-ffcv-r6cw lists affected ranges: NuGet haemmerelectronics.sepppenner.windowshello >=0 <1.0.4)

Commands are suggestions: review each one before running it.