Skip to main content

AMD Vitis Libraries CVE-2026-43606

| EUVDEUVD-2026-56555 HIGH
Observable Timing Discrepancy (CWE-208)
2026-08-11 psirt@amd.com GHSA-cx8r-g3c8-jcfg
8.5
CVSS 4.0 · Vendor: amd
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Gain local process access on target host
  2. Delivery
    Identify victim process using Vitis ECDSA secp256k1
  3. Exploit
    Observe repeated signing operation timing or EM emissions
  4. Execution
    Collect sufficient timing samples
  5. Persist
    Apply lattice-based key recovery algorithm
  6. Impact
    Extract ECDSA private key

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V6 - Authentication Timing attack prevention
Exploitation Conditions

Local process-level access to the same host running the AMD Vitis Libraries ECDSA secp256k1 Security Module is required, consistent with the CVSS 4.0 AV:L rating. The victim application must be actively performing ECDSA signing operations using the secp256k1 curve via the Vitis Libraries Security Module - passive or non-signing workloads are not at risk. For electromagnetic side-channel attacks, physical proximity to the device and specialized measurement equipment are additional prerequisites. Exploitation is limited by: the need to observe many signing operations for statistical key recovery (not a single-request attack), the local-only access vector (no remote unauthenticated path exists), and the requirement for the specific secp256k1 ECDSA code path to be exercised. No authentication bypass or default-configuration exposure applies - this affects only systems actively using the Vitis Libraries cryptographic primitives.

Impact

The CVSS 4.0 vector (AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N) scores 8.5, reflecting that local access alone - with no privilege requirement - is sufficient precondition, and that key recovery yields both high confidentiality and integrity impact. However, the local access requirement (AV:L) substantially constrains the real-world threat surface: an attacker must have a process running on the same host or physical proximity for EM analysis, and must be able to observe a sufficient number of ECDSA signing operations to perform statistical key recovery. This is not a trivial one-shot exploit - it requires sustained measurement capability. EPSS data was not provided in the intelligence feed, so exploitation probability cannot be quantified. No CISA KEV listing and no public POC code have been identified, which is consistent with a low-to-moderate near-term exploitation risk. The highest realistic risk is in multi-tenant FPGA research environments, cloud FPGA instances, or any deployment where a less-privileged co-resident process can time or measure cryptographic operations. No conflicting signals were detected between the CVSS vector and the textual description - both consistently indicate local, non-privileged access is the attack surface.

Exploit ScenarioDerived

An attacker with a co-resident process on a shared FPGA compute host repeatedly triggers or observes ECDSA secp256k1 signing operations in a victim process using the unpatched Vitis Libraries Security Module. By measuring wall-clock timing differences across thousands of signing calls - exploiting the non-constant-time implementation - the attacker applies a lattice-based key-recovery algorithm to reconstruct the full private key. No public POC has been identified, but this attack class is well-documented in academic literature against non-constant-time ECDSA implementations.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Aug 11, 2026

Timing side-channel in AMD Vitis Libraries' ECDSA secp256k1 Security Module exposes private cryptographic keys to local attackers via statistical analysis of operation timing or electromagnetic emanations. Affected are versions prior to 2026.1 of the Vitis Libraries Security Module and Vitis Unified Installer for FPGAs and Adaptive SoCs on Windows. AMD has released version 2026.1 as the fix; no public exploit or active exploitation has been identified at time of analysis.

RemediationAI

The primary fix is to upgrade to AMD Vitis Libraries Security Module version 2026.1 and Vitis Unified Installer version 2026.1, as documented in AMD security bulletin AMD-SB-8015 (https://www.amd.com/en/resources/product-security/bulletin/AMD-SB-8015.html). If immediate patching is not feasible, compensating controls should focus on restricting co-tenancy: prevent untrusted processes from running on the same host as any workload performing ECDSA secp256k1 signing, and where FPGA deployments are physically accessible, enforce strict physical access controls to mitigate electromagnetic side-channel observation. Rotating any private keys that were generated or used for signing operations on unpatched deployments is advisable, as past signing operations may have leaked key material. No additional workarounds are documented in the available references.

Affected VersionsENISA

Vitis™ Unified Installer for FPGAs & Adaptive SoCs in Windows patch: 2026.1
Vitis™ Libraries - Security Module patch: 2026.1

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

CWE-208 (Observable Timing Discrepancy) identifies non-constant-time cryptographic operations. In ECDSA, the secp256k1 scalar multiplication - the core of private-key signing - must execute in constant time regardless of key bit values; any data-dependent branching or memory access pattern leaks information about the scalar (private key). AMD Vitis Libraries provide hardware-accelerated cryptographic primitives targeting FPGA and Adaptive SoC platforms (Xilinx/AMD devices) via the Vitis unified software platform. The affected component is the Security Module within Vitis Libraries. Timing attacks on ECDSA can, with sufficient signing observations, allow full private key recovery via lattice-based methods. Electromagnetic side-channel attacks are a physical variant that measures power or EM emissions rather than time. The secp256k1 curve is widely used in blockchain and cryptocurrency applications, making key exposure particularly high-impact.

Know when Amd gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (amd) PRIMARY 8.5 HIGH
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
vuln.today AI 6.3 MEDIUM

Local access with high complexity (requires sustained timing observation and statistical analysis); low privilege because a co-resident unprivileged process suffices; no availability impact.

3.1 AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N
4.0 AV:L/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (amd).

CVSS VectorVendor: amd

Attack Vector
Local
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
High
Vulnerable system: Availability
None
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

DescriptionCVE.org

Observable Timing Discrepancy in the AMD Vitis Libraries ECDSA secp256k1 component could allow attackers with local access to potentially perform timing analysis or electromagnetic emanation attacks, resulting in high confidentiality and integrity impact due to the exposure of private cryptographic keys.

Executive ViewAI

Why It Matters

AMD's cryptographic development platform (Vitis Libraries) contains a critical vulnerability allowing attackers with local system access to steal private keys from ECDSA operations by analyzing timing patterns and electromagnetic signals. Windows development teams using pre-2026.1 versions face exposure of their most sensitive cryptographic material, potentially compromising any downstream applications or services that depend on these keys.

Business Impact: High
Compensating Controls

Vendor-released patch: version 2026.1

Threat Intelligence Overview

EPSS Score
0.1%
Top 98% exploitable
Prevalence
Low
niche FPGA/Adaptive SoC development toolchain, limited production footprint
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.1%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Small
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

42
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +42
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

More in Amd

View all
CVE-2021-22986 CRITICAL POC
9.8 Mar 31

On BIG-IP versions 16.0.x before 16.0.1.1, 15.1.x before 15.1.2.1, 14.1.x before 14.1.4, 13.1.x before 13.1.3.6, and 12.

CVE-2026-46174 HIGH POC
8.8 May 28

Local privilege escalation and information disclosure in the Linux kernel on AMD Zen2 CPUs allows low-privileged users t

CVE-2020-6103 CRITICAL POC
9.9 Jul 20

An exploitable code execution vulnerability exists in the Shader functionality of AMD Radeon DirectX 11 Driver atidxx64.

CVE-2020-6102 CRITICAL POC
9.9 Jul 20

An exploitable code execution vulnerability exists in the Shader functionality of AMD Radeon DirectX 11 Driver atidxx64.

CVE-2020-6101 CRITICAL POC
9.9 Jul 20

An exploitable code execution vulnerability exists in the Shader functionality of AMD Radeon DirectX 11 Driver atidxx64.

CVE-2020-6100 CRITICAL POC
9.9 Jul 20

An exploitable memory corruption vulnerability exists in AMD atidxx64.dll 26.20.15019.19000 graphics driver. Rated criti

CVE-2018-6546 CRITICAL POC
9.8 Apr 13

plays_service.exe in the plays.tv service before 1.27.7.0, as distributed in AMD driver-installation packages and Gaming

CVE-2021-3653 HIGH POC
8.8 Sep 29

A flaw was found in the KVM's AMD code for supporting SVM nested virtualization. Rated high severity (CVSS 8.8), this vu

CVE-2020-12138 HIGH POC
8.8 Apr 27

AMD ATI atillk64.sys 5.11.9.0 allows low-privileged users to interact directly with physical memory by calling one of se

CVE-2019-5098 HIGH POC
8.6 Dec 05

An exploitable out-of-bounds read vulnerability exists in AMD ATIDXX64.DLL driver, version 26.20.13001.29010. Rated high

CVE-2015-7724 HIGH POC
7.8 Jun 07

AMD fglrx-driver before 15.9 allows local users to gain privileges via a symlink attack. Rated high severity (CVSS 7.8),

CVE-2015-7723 HIGH POC
7.8 Jun 07

AMD fglrx-driver before 15.7 allows local users to gain privileges via a symlink attack. Rated high severity (CVSS 7.8),

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy