dbcve.org
IllustratorApplication · Adobe

CVE-2025-30330

HIGH · 7.8 CVSS v3.1 Published 2025-05-13
Fix available
A fix is available. Upgrade to 28.7.6 / 29.4 or later.
See remediation →
81/100
Remediation priority · High
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Illustrator versions 29.3, 28.7.5 and earlier are affected by a Heap-based Buffer Overflow vulnerability that could result in arbitrary code execution in the context of the current user. Exploitation of this issue requires user interaction in that a victim must open a malicious file.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Adobe Illustrator versions 29.3, 28.7.5 and earlier contain a heap-based buffer overflow vulnerability that can be triggered when a victim opens a malicious file, potentially allowing arbitrary code execution in the context of the current user.

MitigationApply the vendor patch by updating Adobe Illustrator to a patched version. Until patched, avoid opening untrusted .ai or related graphic files from unknown sources.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
IllustratorApplication
Affected:>= 28.0, < 28.7.6>= 29.0, < 29.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if Adobe Illustrator is installed
    On Windows, check for Adobe Illustrator in Program Files or use 'Get-ItemProperty' registry key at 'HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*' looking for DisplayName containing 'Adobe Illustrator'. On macOS, check /Applications for Adobe Illustrator.app.
    Affected if Adobe Illustrator is not found on the system, the system is not affected by this vulnerability.
  2. Determine the installed Adobe Illustrator version
    On Windows, right-click the Illustrator executable in Program Files, select Properties, then Details to view the File Version. On macOS, right-click Adobe Illustrator.app, select Get Info, and view the Version number under General.
    Affected if The exact installed version cannot be determined, treat as potentially affected.
  3. Compare installed version against affected ranges
    Compare the version found in the previous step against these vulnerable ranges: 28.0 through 28.7.5 inclusive, or 29.0 through 29.3 inclusive. Versions 28.7.6 and above, or 29.4 and above, are patched.
    Affected if The installed version falls within >= 28.0 and < 28.7.6, or >= 29.0 and < 29.4.
  4. Identify if the system regularly processes .ai or graphic files from external sources
    Review the system's typical usage patterns: check browser download folders, email attachments, or common document directories for .ai files. Query users or check recent file access logs if available.
    Affected if Users routinely open .ai files from untrusted or unknown sources, increasing exposure to the exploit.

A user is affected if Adobe Illustrator is installed with a version between 28.0 and 28.7.5 inclusive, or between 29.0 and 29.3 inclusive, and the system can open malicious .ai files.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 28.7.6 / 29.4 or later
Fixed in 28.7.629.4
Interim mitigation

Apply the vendor patch by updating Adobe Illustrator to a patched version. Until patched, avoid opening untrusted .ai or related graphic files from unknown sources.

Recommended fix High confidence

Illustrator 28.7.6 or later (28.x branch), or Illustrator 29.4 or later (29.x branch)

  1. Open Adobe Creative Cloud desktop application or navigate to helpx.adobe.com/illustrator
  2. Locate Adobe Illustrator in your installed applications
  3. Click Update or Download to install the latest version
  4. Alternatively, download version 28.7.6 or later from the 28.x branch, or version 29.4 or later from the 29.x branch
  5. Restart Illustrator after the update completes
  6. Verify the installed version matches 28.7.6+ or 29.4+
Caveat Adobe minor updates typically maintain file compatibility, but test critical workflows with existing documents after upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Illustrator Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-30330 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-30330 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data