# CVE-2026-43606: Information disclosure in Vitis™ Libraries - Security Module

> Local attackers can exploit timing discrepancies in the ECDSA component to extract private keys, compromising confidentiality and integrity.

- **Severity:** High 7.7 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Aug 2026
- **Updated:** 12 Aug 2026
- **Also known as:** GHSA-cx8r-g3c8-jcfg

## What is CVE-2026-43606?

CVE-2026-43606 is a high-severity vulnerability in AMD Vitis™  Libraries - Security Module, published on 11 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-208 (Observable Timing Discrepancy)

## Which versions are affected by CVE-2026-43606?


## How do I fix CVE-2026-43606?

No fix has been published for CVE-2026-43606 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-43606 being exploited?

There is no known exploitation of CVE-2026-43606 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-43606 and fix it if it is affected.

What it is: CVE-2026-43606 is a high-severity vulnerability in AMD Vitis™  Libraries - Security Module, published on 11 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-43606 in the wild and no public exploit code.

Affected product: AMD Vitis™  Libraries - Security Module. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-43606/ (Markdown: https://insights.sbomify.com/CVE-2026-43606/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-43606
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-43606
- OSV: https://osv.dev/vulnerability/CVE-2026-43606

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-43606/
Summaries are generated and may contain mistakes; the official description above is the record.