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

Apple Multiple Products vulnerability

Apple FontParser in iOS, iPadOS, macOS, and watchOS contains a memory corruption vulnerability (CWE-787) that may enable code execution when processing maliciously crafted fonts.

Verdict

Today item — known-exploited.

A buffer overflow in font parsing allows remote code execution on multiple Apple platforms. The vulnerability is actively exploited in the wild with moderate EPSS score, posing significant risk to users who open untrusted font files or visit compromised web content.

CISA KEV Yes · 2021-11-033EPSS 0.22178 (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
3 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 2021-11-03).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.22178 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Apple, Multiple Products. 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 font file with oversized data structures to overflow the parser buffer.
Business
Attackers gain arbitrary code execution on user devices across iOS, iPadOS, macOS, and watchOS ecosystems.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I distribute the malicious font via email attachment, messaging app, or compromised website.
Business
User devices become compromised when the font is processed, enabling data theft, lateral movement, or persistent access.
3

Lateral reach — past segmentation narrative 3

Attacker
I leverage code execution to escalate privileges and access sensitive user data or system resources.
Business
Confidentiality and integrity of user information across multiple device types is compromised, damaging customer trust.
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)
  • 3 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.