Skip to content
Applications

CVE-2026-48334

9.3
Critical
EPSS 0.40%Patch availableJul 15, 2026

Adobe Illustrator input validation flaw allows arbitrary code execution when opening crafted files.

common questions

Is CVE-2026-48334 being exploited?

Not confirmed. CVE-2026-48334 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.40% probability of exploitation in the next 30 days.

How severe is CVE-2026-48334?

CVE-2026-48334 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-48334?

Yes. A fix has been recorded for CVE-2026-48334. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-48334 affect?

CVE-2026-48334 affects Adobe Illustrator (unspecified versions), Windows, macOS. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-48334?

Block untrusted .ai/.eps, scan/ quarantine files, restrict Illustrator use, apply vendor patch when released.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Adobe Illustrator (unspecified versions)WindowsmacOS
impact

Arbitrary code execution as current user via opening a malicious Illustrator file; attackers can run malware, steal data, or persist on endpoints.

action required

Immediate action required

affected versions
Adobe Illustrator Desktop 2025
  • affected<= 29.8.7
vendor says fixed in29.8.9
Adobe Illustrator Desktop 2026
  • affected<= 30.5
vendor says fixed in30.6

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free