Cyber Resilience

CVE-2026-15718

Mozilla Firefox ≤ 152.0.6

Published
14 July 2026
Modified
22 July 2026
Patch / advisory
CVSS Score v3.1 4.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
EPSS Score 0.0038 31th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2026-15718 is a medium-severity Release of Invalid Pointer or Reference (CWE-763) vulnerability in Mozilla Firefox. Its CVSS base score is 4.3 (Medium).

Operationally, ranked at the 31th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

EU & UK References

Vulnerability Data

We are aware that exploit code for this is public however we are not aware of any attacks in the wild abusing this flaw. This vulnerability was fixed in Firefox 152.0.6, Firefox ESR 140.13, and Thunderbird 140.13.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

Insufficient information to map techniques.
Confidence: LOW · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2024-43113Same product: Mozilla Firefox
CVE-2023-28159Same product: Mozilla Firefox
CVE-2023-4058Same product: Mozilla Firefox
CVE-2023-23597Same product: Mozilla Firefox
CVE-2023-32208Same product: Mozilla Firefox
CVE-2024-26282Same product: Mozilla Firefox
CVE-2026-4705Same product: Mozilla Firefox
CVE-2024-2606Same product: Mozilla Firefox
CVE-2026-4695Same product: Mozilla Firefox
CVE-2023-5173Same product: Mozilla Firefox

Affected Assets

mozilla
firefox
≤ 152.0.6

Mitigating Controls

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly prevent invalid pointer release errors during development.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

detects

Security testing can detect invalid pointer releases before release.

prevents

Secure SDLC practices can mandate proper memory-management APIs and reviews that catch incorrect deallocation.

prevents

Application security requirements can specify correct use of release functions and pointer validation.

prevents

Secure architecture principles include safe memory handling and resource-lifetime rules.

prevents

Secure coding standards directly prohibit mismatched or incorrect pointer-release calls.

References