Skip to content
Applications

CVE-2026-21280

8.6
High
EPSS 0.25%Patch availableJan 14, 2026

Illustrator untrusted search path flaw enabling user-assisted code execution.

common questions

Is CVE-2026-21280 being exploited?

Not confirmed. CVE-2026-21280 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.25% probability of exploitation in the next 30 days.

How severe is CVE-2026-21280?

CVE-2026-21280 is rated High with a CVSS score of 8.6. 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-21280?

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

What does CVE-2026-21280 affect?

CVE-2026-21280 affects Adobe Illustrator 29.8.3, Adobe Illustrator 30.0, Adobe Illustrator (older versions). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-21280?

Monitor for updates; restrict opening unknown Illustrator files; 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 29.8.3Adobe Illustrator 30.0Adobe Illustrator (older versions)
impact

User-assisted RCE via manipulated search path; attacker must entice user to open a crafted file.

action required

Monitor only

affected versions
Adobe Illustrator Desktop 2025
  • affected<= 29.8.3
vendor says fixed in29.8.4
Adobe Illustrator Desktop 2026
  • affected<= 30.0
vendor says fixed in30.1

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