basicsecurity.net
Proof, not just disclosure.
Threats / Apple / CVE-2025-43300
CVE-2025-43300 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

Apple iOS, iPadOS, and macOS vulnerability

Apple iOS, iPadOS, and macOS contain an out-of-bounds write vulnerability in the Image I/O framework that allows arbitrary code execution through malformed image processing.

Verdict

Today item — known-exploited.

An out-of-bounds write in Image I/O enables memory corruption when processing specially crafted images. Active exploitation in the wild demonstrates practical attack feasibility against all three platforms.

CISA KEV Yes · 2025-08-213EPSS 0.19972 (verify live)4Exploit Public PoC5
01

Is it exploitable?

— the evidence, ranked above the score
Exploit available
Public proof-of-concept exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
21 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2025-08-21).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.19972 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Apple, iOS, iPadOS, and macOS. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-787 Out-of-bounds Write — weakness family: Memory safety.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
WeaknessCWE-787 · Out-of-bounds WriteMemory safety
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution not established

No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.

03

Why it matters

— the attack path, told twice: adversary, then board
1

Front door — unauthenticated access narrative 1

Attacker
I craft a malicious image file that triggers out-of-bounds memory writes in the Image I/O framework.
Business
Attackers gain arbitrary code execution capability on affected devices without user interaction beyond opening an image.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I distribute the malicious image through messaging apps, email, or web content to reach target users.
Business
Device compromise spreads rapidly across iOS, iPadOS, and macOS user bases, enabling data theft or lateral movement.
3

Lateral reach — past segmentation narrative 3

Attacker
I establish persistent access or escalate privileges after initial code execution on compromised systems.
Business
Attackers maintain long-term control over user devices and sensitive data, creating ongoing breach and compliance liability.
04

What to do

— defensible action
  • Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • Public PoC available (VulnCheck)
  • 21 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Public exploit availability
  • Catalogued by apple (CNA)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by appleCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.