# CVE-2024-8105: Insecure Platform Key (PK) used in UEFI system firmware signature

> Attackers with the hardcoded private key can sign malicious UEFI executables, bypassing Secure Boot and executing arbitrary code on affected systems.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Aug 2024
- **Updated:** 28 Jun 2026
- **Also known as:** GHSA-5xg9-v43g-xgcj

## What is CVE-2024-8105?

CVE-2024-8105 is a medium-severity vulnerability in Acer AU47 M1, published on 26 Aug 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability exists in UEFI implementations that use a hard-coded software-based Platform Key (PK). An attacker in possession of the corresponding PK private key can sign arbitrary UEFI executables or firmware components, causing them to be trusted by affected systems and potentially bypassing UEFI Secure Boot trust validation.

## Which versions are affected by CVE-2024-8105?


## How do I fix CVE-2024-8105?

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

## Is CVE-2024-8105 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-8105 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-8105 and fix it if it is affected.

What it is: CVE-2024-8105 is a medium-severity vulnerability in Acer AU47 M1, published on 26 Aug 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-8105 exists.

Affected product: Acer AU47 M1. 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-2024-8105/ (Markdown: https://insights.sbomify.com/CVE-2024-8105/index.md)
```

## Sources

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

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