Habr•September 1, 2026•🇷🇺Translated from Russian

Code Signing Myths: Why a Valid Digital Signature Does Not Equal File Safety

Digital signatures are frequently treated as proof that a file is trustworthy. In practice they answer a narrower question: the file was produced by a named publisher at a specific moment and has not been altered since. They do not state that the file is safe today, that the signer is still the legitimate owner of the key, or that the key has never been stolen.

Attackers obtain usable certificates through several non-cryptographic routes. A private key left on a CI build agent can be exfiltrated during a compromise, exactly as occurred with the Stuxnet samples signed by certificates stolen from Realtek and JMicron. Supply-chain attacks such as ShadowHammer against ASUS Live Update in 2019 replaced payload contents while preserving the original publisher signature. Certificates can also be purchased from resellers that perform minimal identity checks, allowing an attacker to operate under a formally valid but effectively fictitious legal entity.

Expired certificates remain dangerous because signature verification evaluates the chain at the time recorded by an RFC 3161 timestamp token rather than the current date. Using the OpenSSL -attime flag demonstrates that a chain rejected today as expired will validate when tested against a date inside the original validity window. The same mechanism applies to Authenticode signatures; Windows accepts signatures timestamped while the certificate was still valid even if the certificate has since expired. The 2022 Nvidia certificate leak illustrated the issue: both keys were already expired yet were still used to sign drivers that Windows loaded without complaint.

Signature hashes do not cover the entire file. Authenticode deliberately excludes the PE checksum field, the certificate table directory entry, and the attribute certificate table itself. Historical implementations of WinVerifyTrust performed no additional checks on the excluded region, enabling the padding abuse documented in CVE-2013-3900. Microsoft published Security Advisory 2915720 and the EnableCertPaddingCheck registry key, yet the stricter behavior remains opt-in because it can break legitimate distribution workflows.

Revocation is equally unreliable for code-signing scenarios. When CRL or OCSP endpoints are unreachable, most verifiers treat the certificate as valid. Even when revocation succeeds, the revocation date can be set after the actual compromise, preserving a window during which timestamped malicious signatures continue to pass checks.

Practical defenses therefore focus on concrete identity rather than the mere presence of a signature. Maintain explicit thumbprint allow-lists in WDAC or AppLocker, treat timestamp tokens as first-class telemetry, block known-compromised certificates by thumbprint, and enforce strict revocation checking for high-risk categories. Signing keys must reside only in hardware security modules; build agents should submit hashes for signing rather than hold extractable private keys.

Related articles

Habr•Vulnerabilities & Exploits

F6 Investigates First In-the-Wild Exploitation of Critical CVE-2026-76466 in Cisco Expressway

Russian cybersecurity firm F6 has documented the first confirmed exploitation of the critical CVE-2026-76466 vulnerability (CVSS 9.8) affecting Cisco Expressway devices. Attackers targeted a Russian company and quickly adapted a public proof-of-concept exploit to gain root-level remote command execution on version X15.5.3. The flaw resides in the Erlang distribution authentication mechanism on TCP port 4372, allowing unauthenticated command execution via a hardcoded cookie. After initial access, the threat actors deployed over 100 custom Python scripts for network reconnaissance, lateral movement, and data collection, including tools that abused WinRM, SMB, LDAP, and SQL Server protocols. F6 observed modifications to the original PoC that enabled arbitrary command execution and result retrieval, along with auxiliary scripts for TCP relaying and repeated connection attempts. The incident highlights how quickly public exploits can be weaponized against perimeter devices that bridge external and internal networks.

Securitylab•Vulnerabilities & Exploits

NGINX2Root Vulnerabilities: Ten Critical Flaws Patched in NGINX Including Remote Code Execution via HTTP/2

On November 18 2026 NGINX developers addressed ten vulnerabilities with five grouped under the NGINX2Root research name by Theori's Xint team. The most severe CVE-2026-123007 enables unauthenticated remote code execution on servers with HTTP/2 enabled by exploiting memory corruption that originated in 2015. Researchers demonstrated full compromise including root escalation via a separate Linux SCTP kernel flaw and escape from Docker containers. Working exploits have been published by Rapid7 and others with specific requirements such as AVX-512 support and substantial traffic volumes. Patches are available in NGINX 1.30.7 1.31.9 and corresponding NGINX Plus releases while temporary mitigations include disabling HTTP/2 or HTTP/3. The issues affect standalone servers reverse proxies Kubernetes ingress controllers and embedded NGINX instances across distributions.

安全客•Vulnerabilities & Exploits

Linux Kernel CVE-2026-98432 Enables Remote Code Execution Across Nearly All Versions Since 4.4

China's NVDB issued a high-severity advisory on November 18 warning of a remote code execution flaw in the Linux Kernel that grants attackers full root privileges. The vulnerability affects Linux Kernel 4.4 and virtually every subsequent mainline release, impacting major distributions including Ubuntu, Debian, Red Hat, SUSE, Oracle, and Chinese variants such as Kylin, UnionTech, and Deepin. Because the flaw is remotely exploitable without prior authentication and leads directly to highest privileges, exposed public-facing systems face immediate risk. The advisory notably states that AI models can rapidly analyze patches, identify trigger conditions, and generate working exploit chains, shrinking the traditional window between disclosure and weaponization from days to hours. Official fixes have been published for multiple stable branches, yet administrators must still validate driver compatibility, container runtimes, and third-party modules before deploying kernel updates in production. The advisory also highlights incomplete vulnerability disclosures across PHP, Node.js, Apache, Chrome, GitLab, and MySQL, underscoring the need for precise asset inventories rather than reliance on vulnerability databases alone.

Habr•Vulnerabilities & Exploits

Wireshark 4.6.10 Released with Fixes for 39 Vulnerabilities and Multiple Protocol Dissectors

The open-source network protocol analyzer Wireshark has received its 4.6.10 update, addressing 14 bugs along with 39 security vulnerabilities discovered during testing. The release continues the 4.6 development branch that began in October 2025 and follows the long-standing stable line that started with version 1.0.0 in 2008. Patches cover a wide range of protocol dissectors including RTSE, NBAP, IEEE 1609.2, IrDA, Matter, IEEE 1905, OpenWire, USB-PTP, Exported PDU, ACN, PROFINET, SDP, MsgPack, NNTP, TLS, and SCTP. Additional corrections resolve infinite loops in the Kafka dissector and Tektronix K12xx file parser, heap disclosure issues, and a remote code execution flaw in LoRaWAN decryption tracked as ZDI-CAN-32851. The update also ships Npcap 1.89 for Windows installers and changes the default extcap directory on Unix-like systems to libexec for better multiarch compatibility.