---
title: "CVE-2026-25267: Memory Corruption - Memory Corruption"
description: "A memory corruption vulnerability occurs when a non-secure loader rewrites page tables before secure memory initialization, letting attackers cause memory corruption, exploit requires specific loader behavior."
url: https://panop.io/threat-heartbeat/CVE-2026-25267/
---

# CVE-2026-25267 Memory Corruption - Memory Corruption

A memory corruption vulnerability occurs when a non-secure loader rewrites page tables before secure memory initialization, letting attackers cause memory corruption, exploit requires specific loader behavior.

CVSS base score 7.8 /10

High

CISA KEV

Not listed

Public exploit

None known

EPSS

0.06% chance of exploitation in 30 days

[View the NVD record ↗](https://nvd.nist.gov/vuln/detail/CVE-2026-25267)

## Details

Type

Memory Corruption

CVSS vector

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

Published

6 October 2026

Updated

15 October 2026

Weakness

[CWE-862](https://cwe.mitre.org/data/definitions/862.html)

## Vendor fix

Update to the latest version with secure memory initialization fixes.

Patching closes this CVE. It does not tell you which of your systems run the affected version, or what else is exposed alongside them.

## References

- [https://nvd.nist.gov/vuln/detail/CVE-2026-25267](https://nvd.nist.gov/vuln/detail/CVE-2026-25267)
- [https://docs.qualcomm.com/product/publicresources/securitybulletin/october-2026-bulletin.html](https://docs.qualcomm.com/product/publicresources/securitybulletin/october-2026-bulletin.html)

[← All CVEs](https://panop.io/threat-heartbeat/)

## What this record can't tell you

- Whether you run the affected software, and where
- Whether an attacker can actually reach and exploit it
- The misconfigurations that never get a CVE number
- What it would cost the business, ranked into what to fix first

Panop answers these inside your environment, for this CVE and every other finding.

[Book a demo](https://panop.io/demo)