NVD / CVE Program· CNA apple

CVE-2025-24252: A use-after-free issue was addressed with improved memory management.

Noroxi assessment

Priority: Monitor (action score 35/100)

Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
Probability of exploitation in the next 30 days: 1.3% (FIRST EPSS); higher than 70.6% of all records.
Someone on the same network segment can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
According to the record, no fixed version is available yet.

Low priority for now. Update when a fix is released; follow the vendor's advisory.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

A use-after-free issue was addressed with improved memory management. This issue is fixed in iOS 18.4 and iPadOS 18.4, iPadOS 17.7.6, macOS Sequoia 15.4, macOS Sonoma 14.7.5, macOS Ventura 13.7.5, tvOS 18.4, visionOS 2.4. An attacker on the local network may be able to corrupt process memory.

HighCVSS 8.8 · v3.1—Proof of concept No fix recorded

BDU:2025-06520

Published: Apr 28, 2025
Updated: Jun 17, 2026
EPSS: 1.3% · 70th percentile
CWE: CWE-416

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 35 / 40 · 8.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 1.3%

CISA SSVC decision

Exploitation: proof of concept
Automatable: no
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
Proof of concept exists, no weaponized module
No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
apple	ipados	cpe:2.3:o:apple:ipados
apple	iphone os	cpe:2.3:o:apple:iphone_os
apple	macos	cpe:2.3:o:apple:macos
apple	tvos	cpe:2.3:o:apple:tvos
apple	visionos	cpe:2.3:o:apple:visionos

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

apple ipadosbefore 17.7.6
apple ipados18.0 and later · before 18.4
apple iphone osbefore 18.4
apple macosbefore 13.7.5
apple macos14.0 and later · before 14.7.5
apple macos15.0 and later · before 15.4
apple tvosbefore 18.4
apple visionosbefore 2.4

Versions reported by the vendor

Affected version ranges reported by the assigning authority (apple). Independent of NVD's CPE analysis and usually ahead of it.

Apple iOS and iPadOS
- before 18.4affected
Apple iPadOS
- before 17.7.6affected
Apple macOS
- before 13.7.5affected
- before 14.7.5affected
- before 15.4affected
Apple tvOS
- before 18.4affected
Apple visionOS
- before 2.4affected

Same product

apple: all records

Other highest-scoring records for the same primary product.

CVE-2025-43300An out-of-bounds write issue was addressed with improved bounds checking.KEV
90Now
CVE-2021-30860An integer overflow was addressed with improved input validation.KEV
84Now
CVE-2023-41064A buffer overflow issue was addressed with improved memory handling.KEV
77This week

Published before and after this one in the same product

← EarlierCVE-2025-24206Apr 28, 2025 · An authentication issue was addressed with improved state management.
30Monitor
← EarlierCVE-2025-24251Apr 28, 2025 · The issue was addressed with improved checks.
26Monitor
Later →CVE-2025-24270Apr 28, 2025 · This issue was addressed by removing the vulnerable code.
22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

Proof-of-concept repository on GitHub ×2

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
Source	Kind	Date
Proof-of-concept repository on GitHub	stars:163	2025-04-29
Proof-of-concept repository on GitHub	stars:3	2025-05-10

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

PublishedApr 28, 2025
First PoCApr 29, 2025same day
TodayNov 3, 2026+554 d

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2025-2408591 days apartA use after free issue was addressed with improved memory management.KEV
75This week
CVE-2023-41974474 days apartA use-after-free issue was addressed with improved memory management.KEV
62This week
CVE-2025-4322292 days apartA use-after-free issue was addressed by removing the vulnerable code.
39Monitor
CVE-2026-43814455 days apartA use after free issue was addressed with improved memory management.
39Monitor
CVE-2026-43822455 days apartA use after free issue was addressed with improved memory management.
39Monitor
CVE-2026-64751455 days apartA use after free issue was addressed with improved memory management.
39Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Someone on the same network segment can trigger it.
No account or password is required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Adjacent
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

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

nvd-secondary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1free(dev->buf);
2/* ... another thread is still running ... */
3process(dev->buf);

Fixed

1lock(&dev->lock);
2free(dev->buf);
3dev->buf = NULL;
4unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

References

support.apple.com/en-us/122371

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records