# CVE-2026-58006: Altera SoCFPGA BL31 Mailbox Output Pointer Validation Enables EL3 Secure-Memory Corruption

> Attackers can corrupt secure memory via untrusted pointer dereference in Altera SoCFPGA BL31, enabling privilege escalation and code execution.

- **Severity:** High 8.3 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:L/VI:H/VA:H/SC:L/SI:H/SA: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:** 24 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-72h2-wwh5-8975

## What is CVE-2026-58006?

CVE-2026-58006 is a high-severity memory corruption vulnerability in Altera Trusted Firmware, published on 24 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Untrusted pointer dereference vulnerability in Altera Trusted Firmware on HPS allows Exploitation of Improperly Configured or Implemented Memory Protections.

This issue affects Trusted Firmware: through socfpga_v2.14.0.

Weakness: CWE-822 (Untrusted Pointer Dereference)

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


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

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

## Is CVE-2026-58006 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-58006 is a high-severity memory corruption vulnerability in Altera Trusted Firmware, published on 24 Sep 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-58006 in the wild and no public exploit code.

Affected product: Altera Trusted Firmware. 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-58006/ (Markdown: https://insights.sbomify.com/CVE-2026-58006/index.md)
```

## Sources

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

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