QID 45526

Date Published: 2022-04-20

QID 45526: Microsoft Windows Authenticode Signature Verification is Not Enabled

This Information Gathering QID is based on the republished information for the WinVerifyTrust Signature Validation Vulnerability from Microsoft.

Microsoft stated that, they have re-published this to inform customers that EnableCertPaddingCheck is available in all currently supported versions of Windows 10 and Windows 11. And Microsoft does not plan to enforce the stricter verification behavior as a default functionality on supported releases of Microsoft windows.

This behavior remains available as an opt-in feature via registry key setting, and is available on supported editions of Windows released since December 10, 2013. This includes all currently supported versions of Windows 10 and Windows 11. The registry key already exists in Window 10 and Window 11, so no security update is required but the reg key must be set.

QID Detection Logic (Authenticated):
This QID checks for the presence of these registry keys HKEY_LOCAL_MACHINE\Software\Microsoft\Cryptography\Wintrust\Config and HKEY_LOCAL_MACHINE\Software\Wow6432Node\Microsoft\Cryptography\Wintrust\Config, and checks whether the value 'EnableCertPaddingCheck' associated with these keys is set to 1.
If these keys are missing or the value is not set to 1, then this QID gets reported.

A remote code execution vulnerability exists in the way that the WinVerifyTrust function handles Windows Authenticode signature verification for portable executable (PE) files. An anonymous attacker could exploit the vulnerability by modifying an existing signed executable file to leverage unverified portions of the file in such a way as to add malicious code to the file without invalidating the signature.

Solution
Customers are advised to refer to WinVerifyTrust Signature Validation for further details pertaining to this.

Opting into this stricter verification behavior causes the WinVerifyTrust function to perform strict Windows Authenticode signature verification for PE files. After opting-in, PE files will be considered "unsigned" if Windows identifies content in them that does not conform to the Authenticode specification. This may impact some installers. If you are using an installer that is impacted, Microsoft recommends using an installer that only extracts content from validated portions of the signed file.

Vendor References

CVEs related to QID 45526

Software Advisories
Advisory ID Software Component Link

© CVE.report 2026

Use of this information constitutes acceptance for use in an AS IS condition. There are NO warranties, implied or otherwise, with regard to this information or its use. Any use of this information is at the user's risk. It is the responsibility of user to evaluate the accuracy, completeness or usefulness of any information, opinion, advice or other content. EACH USER WILL BE SOLELY RESPONSIBLE FOR ANY consequences of his or her direct or indirect use of this web site. ALL WARRANTIES OF ANY KIND ARE EXPRESSLY DISCLAIMED. This site will NOT BE LIABLE FOR ANY DIRECT, INDIRECT or any other kind of loss.

CVE, CWE, and OVAL are registred trademarks of The MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. This site includes MITRE data granted under the following license.

Free CVE JSON API cve.report/api

CVE.report and Source URL Uptime Status status.cve.report