← Vulnerability feed

Vulnerability record · CVE-2026-80469 · published 11 September 2026

CVE-2026-80469: Improper verification of cryptographic signature vulnerability

An attacker may achieve arbitrary code execution on a target system by uploading a malicious device driver package, bypassing driver verification mechanisms, and triggering the execution of attacker-controlled code. User interaction is required.

8.3 CVSS 3.1 High EPSS 0.39% · top 69.7% CWE-347 · Improper verification of cryptographic signature Deferred
8.3CVSS 3.1 base score
0.39%EPSS exploitation probability, 30 days
NoNot in CISA KEV
0Affected product versions listed by NVD
6References
18 Sep 2026Last modified by NVD

Description

An attacker may achieve arbitrary code execution on a target system by uploading a malicious device driver package, bypassing driver verification mechanisms, and triggering the execution of attacker-controlled code. User interaction is required.

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H

References

LinkTags
https://www.cisa.gov/resources-tools/resources/ics-recommended-practices
https://www.first.org/cvss/calculator/3.1
https://www.sick.com/.well-known/csaf/white/2026/sca-2026-0012.json
https://www.sick.com/.well-known/csaf/white/2026/sca-2026-0012.pdf
https://www.sick.com/media/docs/9/19/719/special_information_sick_operating_guidelines_cybersecurity_by_sick_en_im010671
https://www.sick.com/psirt

Track CVE-2026-80469 inside VULONE

Watch it alongside the ransomware crews, C2 infrastructure and forum chatter that reference it, query it through the API and pull it into your SIEM over TAXII.

Start free Open in platform

Related vulnerabilities

Same products first, then exploited flaws of the same weakness class.

10.0CVE-2026-5430Wso2 api control plane improper verification of cryptographic signature vulnerabilityThe JWT authentication mechanism accepts tokens signed with algorithms other than those explicitly configured or supported. This allows an attacker t…KEVEPSS 0.59%9.5CVE-2026-48558SimpleHelp OIDC authentication bypass via unverified token signatureSimpleHelp 5.5.15 and earlier and 6.0 pre-release versions accept OIDC identity tokens without verifying their cryptographic signature. When OIDC is …KEVEPSS 5.7%analysed9.8CVE-2025-59718Fortinet FortiOS/FortiProxy SAML signature check bypass in FortiCloud SSOFortiOS, FortiProxy and FortiSwitchManager fail to properly verify the cryptographic signature of SAML responses used for FortiCloud SSO login. An un…KEVEPSS 68%analysed4.6CVE-2025-47827IGEL OS Secure Boot bypass via improper signature verificationIGEL OS before version 11 fails to properly verify a cryptographic signature in the igel-flash-driver module, allowing Secure Boot to be bypassed. A …KEVEPSS 4.9%analysed10.0CVE-2020-2021PAN-OS SAML signature verification bypass allows authentication bypassPAN-OS fails to properly verify SAML signatures when SAML authentication is enabled and the 'Validate Identity Provider Certificate' option is unchec…KEVEPSS 4.4%analysed5.5CVE-2013-3900Windows WinVerifyTrust Authenticode signature verification RCECVE-2013-3900 is a remote code execution flaw in how the Windows WinVerifyTrust function verifies Authenticode signatures on portable executable file…KEVEPSS 45%analysed7.8CVE-2020-1464Windows file signature validation spoofing allows loading of improperly signed filesWindows incorrectly validates file signatures, so a crafted file can be treated as properly signed. This lets an attacker bypass the security feature…KEVEPSS 39%analysed

Source: NIST National Vulnerability Database (record CVE-2026-80469), CISA KEV, FIRST EPSS (scores of 2026-09-26). This page is refreshed as NVD updates the record.