Critical security advisoryCriticalFlagged by our vulnerability database: PHP2Shell is on CISA’s exploited list. Most WordPress hosting runs PHP. See if your site is affectedFlagged by our vulnerability database: PHP2Shell is being exploited. DetailsExploited: PHP2Shell. Check your site
HuttenlocherTechnologies
Updated 2 h ago

Vulnerability database

Every flaw the U.S. government’s cybersecurity agency (CISA) has confirmed attackers are using, plus the new WordPress plugin and theme bugs published each day, sorted by what they mean for a small business. We refresh it twice a day. If you see something your website or office runs, tell us.

1,762exploited flaws on CISA’s list
34added in the last 30 days
344new WordPress flaws this week
390,080entries in the database

13 results

  • Apr 9, 2026osslsigncode is a tool that implements Authenticode signing and timestamping.CVE-2026-39856 · Other software · mtrojnar · reported by GitHubMedium 5.5

    osslsigncode is a tool that implements Authenticode signing and timestamping. Prior to 2.13, an out-of-bounds read vulnerability exists in osslsigncode version 2.12 and earlier in the PE page-hash computation code (pe_page_hash_calc()). When processing PE sections for page hashing, the function uses PointerToRawData and SizeOfRawData values from section headers without validating that the referenced region lies within the mapped file. An attacker can craft a PE file with section headers that point beyond the end of the file. When osslsigncode computes page hashes for such a file, it may attempt to hash data from an invalid memory region, causing an out-of-bounds read and potentially crashing the process. The vulnerability can be triggered while signing a malicious PE file with page hashing enabled (-ph), or while verifying a malicious signed PE file that already contains page hashes. Verification of an already signed file does not require the verifier to pass -ph. This vulnerability is fixed in 2.13.

    Product
    osslsigncode
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Apr 9, 2026osslsigncode is a tool that implements Authenticode signing and timestamping.CVE-2026-39855 · Other software · mtrojnar · reported by GitHubMedium 5.5

    osslsigncode is a tool that implements Authenticode signing and timestamping. Prior to 2.13, an integer underflow vulnerability exists in osslsigncode version 2.12 and earlier in the PE page-hash computation code (pe_page_hash_calc()). When page hash processing is performed on a PE file, the function subtracts hdrsize from pagesize without first validating that pagesize >= hdrsize. If a malicious PE file sets SizeOfHeaders (hdrsize) larger than SectionAlignment (pagesize), the subtraction underflows and produces a very large unsigned length. The code allocates a zero-filled buffer of pagesize bytes and then attempts to hash pagesize - hdrsize bytes from that buffer. After the underflow, this results in an out-of-bounds read from the heap and can crash the process. The vulnerability can be triggered while signing a malicious PE file with page hashing enabled (-ph), or while verifying a malicious signed PE file that already contains page hashes. Verification of an already signed file does not require the verifier to pass -ph. This vulnerability is fixed in 2.13.

    Product
    osslsigncode
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Apr 9, 2026osslsigncode is a tool that implements Authenticode signing and timestamping.CVE-2026-39853 · Other software · mtrojnar · reported by GitHubHigh 7.8

    osslsigncode is a tool that implements Authenticode signing and timestamping. Prior to 2.12, A stack buffer overflow vulnerability exists in osslsigncode in several signature verification paths. During verification of a PKCS#7 signature, the code copies the digest value from a parsed SpcIndirectDataContent structure into a fixed-size stack buffer (mdbuf[EVP_MAX_MD_SIZE], 64 bytes) without validating that the source length fits within the destination buffer. This pattern is present in the verification handlers for PE, MSI, CAB, and script files. An attacker can craft a malicious signed file with an oversized digest field in SpcIndirectDataContent. When a user verifies such a file with osslsigncode verify, the unbounded memcpy can overflow the stack buffer and corrupt adjacent stack state. This vulnerability is fixed in 2.12.

    Product
    osslsigncode
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 9, 2023uthenticode is a small cross-platform library for partially verifying Authenticode digital signatures.CVE-2023-40012 · Other software · trailofbits · reported by GitHubMedium 5.9

    uthenticode is a small cross-platform library for partially verifying Authenticode digital signatures. Versions of uthenticode prior to the 2.x series did not check Extended Key Usages in certificates, in violation of the Authenticode X.509 certificate profile. As a result, a malicious user could produce a "signed" PE file that uthenticode would verify and consider valid using an X.509 certificate that isn't entitled to produce code signatures (e.g., a SSL certificate). By design, uthenticode does not perform full-chain validation. However, the absence of EKU validation was an unintended oversight. The 2.0.0 release series includes EKU checks. There are no workarounds to this vulnerability.

    Product
    uthenticode
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 9, 2023uthenticode is a small cross-platform library for partially verifying Authenticode digital signatures.CVE-2023-39969 · Other software · trailofbits · reported by GitHubCritical 9

    uthenticode is a small cross-platform library for partially verifying Authenticode digital signatures. Version 1.0.9 of uthenticode hashed the entire file rather than hashing sections by virtual address, in violation of the Authenticode specification. As a result, an attacker could modify code within a binary without changing its Authenticode hash, making it appear valid from uthenticode's perspective. Versions of uthenticode prior to 1.0.9 are not vulnerable to this attack, nor are versions in the 2.x series. By design, uthenticode does not perform full-chain validation. However, the malleability of signature verification introduced in 1.0.9 was an unintended oversight. The 2.x series addresses the vulnerability. Versions prior to 1.0.9 are also not vulnerable, but users are encouraged to upgrade rather than downgrade. There are no workarounds to this vulnerability.

    Product
    uthenticode
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jul 11, 2023Mono Authenticode Validation Spoofing VulnerabilityCVE-2023-35373 · Computers, phones & browsers · Microsoft · reported by secure@microsoft.comMedium 5.3

    Mono Authenticode Validation Spoofing Vulnerability

    Product
    Mono 6.12.0
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Sep 15, 2021Windows Authenticode Spoofing VulnerabilityCVE-2021-36959 · Computers, phones & browsers · Microsoft · reported by secure@microsoft.comMedium 5.5

    Windows Authenticode Spoofing Vulnerability

    Product
    Windows 10 Version 1507
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jul 14, 2021Windows Authenticode Spoofing VulnerabilityCVE-2021-33782 · Computers, phones & browsers · Microsoft · reported by secure@microsoft.comMedium 5.5

    Windows Authenticode Spoofing Vulnerability

    Product
    Windows 10 Version 1507
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 28, 2019Windows binaries generated with InstallBuilder versions earlier than 19.7.0 are vulnerable to tampering even if they contain a valid Authenticode signature.CVE-2019-5530 · Other software · Bitrock · reported by security@vmware.comHigh 7.8

    Windows binaries generated with InstallBuilder versions earlier than 19.7.0 are vulnerable to tampering even if they contain a valid Authenticode signature.

    Product
    Installbuilder
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Apr 10, 2012Microsoft Windows Authenticode Signature Verification Remote Code Execution VulnerabilityCVE-2012-0151 · Computers, phones & browsers · Microsoft · reported by secure@microsoft.comExploitedHigh 7.8

    The Authenticode Signature Verification function in Microsoft Windows (WinVerifyTrust) does not properly validate the digest of a signed portable executable (PE) file, which allows user-assisted remote attackers to execute code.

    Product
    Windows
    On CISA’s list since
    Jun 8, 2022 (federal fix deadline Jun 22, 2022)
    What to do
    Attackers are using this now. Install Microsoft’s update today. If there is no update for your version, take the product off the internet or stop using it until there is.
  • Apr 14, 2010The Authenticode Signature verification functionality in cabview.dll in Cabinet File Viewer Shell Extension 5.1, 6.0, and 6.1 in Microsoft Windows 2000 SP4, WinCVE-2010-0487 · Computers, phones & browsers · Microsoft · reported by secure@microsoft.comHigh 9.3

    The Authenticode Signature verification functionality in cabview.dll in Cabinet File Viewer Shell Extension 5.1, 6.0, and 6.1 in Microsoft Windows 2000 SP4, Windows XP SP2 and SP3, Windows Server 2003 SP2, Windows Vista Gold, SP1, and SP2, Windows Server 2008 Gold, SP2, and R2, and Windows 7 does not properly use unspecified fields in a file digest, which allows remote attackers to execute arbitrary code via a modified cabinet (aka .CAB) file that incorrectly appears to have a valid signature, aka "Cabview Corruption Validation Vulnerability."

    Product
    Windows 7
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Apr 14, 2010The WinVerifyTrust function in Authenticode Signature Verification 5.1, 6.0, and 6.1 in Microsoft Windows 2000 SP4, Windows XP SP2 and SP3, Windows Server 2003 CVE-2010-0486 · Computers, phones & browsers · Microsoft · reported by secure@microsoft.comHigh 9.3

    The WinVerifyTrust function in Authenticode Signature Verification 5.1, 6.0, and 6.1 in Microsoft Windows 2000 SP4, Windows XP SP2 and SP3, Windows Server 2003 SP2, Windows Vista Gold, SP1, and SP2, Windows Server 2008 Gold, SP2, and R2, and Windows 7 does not properly use unspecified fields in a file digest, which allows user-assisted remote attackers to execute arbitrary code via a modified (1) Portable Executable (PE) or (2) cabinet (aka .CAB) file that incorrectly appears to have a valid signature, aka "WinVerifyTrust Signature Validation Vulnerability."

    Product
    Windows 7
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Nov 17, 2003The Authenticode capability in Microsoft Windows NT through Server 2003 does not prompt the user to download and install ActiveX controls when the system is lowCVE-2003-0660 · Computers, phones & browsers · Microsoft · reported by MITREHigh 7.5

    The Authenticode capability in Microsoft Windows NT through Server 2003 does not prompt the user to download and install ActiveX controls when the system is low on memory, which could allow remote attackers to execute arbitrary code without user approval.

    Product
    Windows 2000
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.

Where this comes from: the exploited list is CISA’s Known Exploited Vulnerabilities catalog. Everything else is the whole National Vulnerability Database, where each record is published by the team that found the bug (Wordfence, Patchstack, WPScan, the vendors themselves and others); we show who. Exploit odds are FIRST’s EPSS, updated daily. Titles and categories are ours, so check the linked record before acting on a detail. For a write-up of the big ones, see our advisories. Every vendor, and every WordPress plugin and theme with a recorded flaw, also has its own page. All of it is free to reuse as JSON, CSV or RSS.

Weekly security brief

The flaws that hit local websites, every Friday.

One short email: what got exploited this week, which WordPress plugins broke, and what to check. Unsubscribe in one click.

Get in touch

Tell us what you're building.

A website, your marketing, a security check, an app, or the thing you've been running out of a spreadsheet for three years. A few lines is plenty.

01The person who'll do the work writes back
02A short call, then a written plan with the price
03Nothing starts until you say yes
04Hacked or down right now? Call, and we pick up the same day
843-331-6339

Not ready to talk yet? Run the free website check and see what Google sees.

What do you need?
Build
Grow
Protect
Urgent

No newsletter, no sales sequence. Just a reply.