Cyber Resilience

CVE-2026-47924

Memory Safety in Adobe Acrobat Dc 15.008.20082 – 26.001.21662

Memory Safety
Published
09 June 2026
Modified
17 June 2026
Patch / advisory
View advisory
CVSS Score v3.1 5.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
EPSS Score 0.0029 22th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2026-47924 is a medium-severity Use After Free (CWE-416) vulnerability in Apple Macos. Its CVSS base score is 5.5 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Malicious File (T1204.002); ranked at the 22th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SC-39 (Process Isolation) and SI-2 (Flaw Remediation) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

Acrobat Reader versions 24.001.30365, 26.001.21651 and earlier are affected by a Use After Free vulnerability that could lead to disclosure of sensitive memory. An attacker could leverage this vulnerability to disclose sensitive information. Exploitation of this issue requires user interaction…

more

in that a victim must open a malicious file.

CWE(s)
CWE-416

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

T1204.002 Malicious File Execution
An adversary may rely upon a user opening a malicious file in order to gain execution.
attack.mitre.org →
Why these techniques?

Direct match to malicious file requiring user interaction for exploitation; UAF enables memory disclosure but no other techniques are directly facilitated.

Confidence: HIGH · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2025-27159Same product: Adobe Acrobat
CVE-2026-47919Same product: Adobe Acrobat
CVE-2026-47918Same product: Adobe Acrobat
CVE-2026-47955Same product: Adobe Acrobat
CVE-2026-47915Same product: Adobe Acrobat
CVE-2026-47917Same product: Adobe Acrobat
CVE-2026-27220Same product: Adobe Acrobat
CVE-2026-47920Same product: Adobe Acrobat
CVE-2026-47921Same product: Adobe Acrobat
CVE-2026-47916Same product: Adobe Acrobat

Affected Assets

adobe
acrobat dc
15.008.20082 — 26.001.21662
adobe
acrobat reader dc
15.008.20082 — 26.001.21662
adobe
acrobat
24.0.0 — 24.001.30383

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • SI-2 Flaw Remediation
  • SC-39 Process Isolation
  • SI-3 Malicious Code Protection
Detect
Catch it (NIST detect / respond)
  • SI-3 Malicious Code Protection
Harden
Shrink the surface (DISA STIG)
  • 3 hardening rules · 3 OS baselines
Validate
Prove the fix (OWASP ASVS)
  • V1.4.3

Mitigating Controls (NIST 800-53 r5) AI

SI-2 Flaw Remediation good match
prevent

Directly requires timely patching of the vulnerable Acrobat Reader versions to eliminate the use-after-free flaw.

SC-39 Process Isolation good match
prevent

Process isolation (sandboxing) in PDF readers confines memory corruption exploits such as use-after-free to limit sensitive memory disclosure.

SI-3 Malicious Code Protection partial match
preventdetect

Malicious code protection can inspect or block the malicious PDF file required to trigger the vulnerability before it is opened.

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 incorporate memory-safety tooling and reviews that prevent most use-after-free defects.

ID.RA-01 partial match
prevents

Vulnerability identification processes can discover use-after-free issues via scanning or analysis but do not prevent their introduction.

PR.PS-02 partial match
prevents

Routine patching removes known use-after-free instances after they have been introduced in released software.

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.

A.8.29 Security testing in development and acceptance mostly match
detects

Security testing in development can detect use-after-free bugs before release.

A.8.25 Secure development life cycle partial match
prevents

Secure SDLC mandates memory-safety practices that reduce use-after-free defects.

A.8.26 Application security requirements partial match
prevents

Application security requirements can specify memory-management rules that mitigate use-after-free.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles include memory-safety design choices that limit use-after-free exposure.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly prescribe avoidance of use-after-free patterns.

A.8.32 Change management partial match
prevents

Change-management processes help ensure memory-safety fixes are deployed consistently.

References