IllustratorApplication · Adobe

CVE-2025-49563

HIGH · 7.8 CVSS v3.1 Published 2025-08-12
Fix available
A fix is available. Upgrade to 28.7.9 / 29.7 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 28.7.8, 29.6.1 and earlier are affected by an out-of-bounds write 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 contains an out-of-bounds write vulnerability that allows arbitrary code execution when a user opens a maliciously crafted file. The vulnerability exists in versions 28.7.8, 29.6.1 and earlier, enabling attackers to execute code in the context of the current user.

MitigationApply the vendor patch by upgrading Adobe Illustrator to version 28.7.9 or 29.6.2 or later. Users should not open untrusted .ai or related files until the update is applied.

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.9>= 29.0, < 29.7

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 installed Adobe Illustrator version
    Open Adobe Illustrator and navigate to Help > About Adobe Illustrator, or right-click the application file in Program Files and select Properties to view version information
    Affected if The displayed version falls within 28.0 to 28.7.8, or 29.0 to 29.6.1
  2. Verify exact version number
    Locate the version number in the About dialog or file properties - note the full version string (e.g., 28.7.8 or 29.6.1)
    Affected if Version is less than 28.7.9 for the 28.x release line, or less than 29.7 for the 29.x release line
  3. Confirm the 28.x branch range
    If version starts with 28.x, compare the minor version against 28.7.8
    Affected if The version is 28.0 through 28.7.8 inclusive (any subversion below 28.7.9)
  4. Confirm the 29.x branch range
    If version starts with 29.x, compare the minor version against 29.6.1
    Affected if The version is 29.0 through 29.6.1 inclusive (any subversion below 29.7)

You are affected if Adobe Illustrator version is 28.0-28.7.8 or 29.0-29.6.1; you are NOT affected if running 28.7.9 or later, or 29.7 or later

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.9 / 29.7 or later
Fixed in 28.7.929.7
Interim mitigation

Apply the vendor patch by upgrading Adobe Illustrator to version 28.7.9 or 29.6.2 or later. Users should not open untrusted .ai or related files until the update is applied.

Recommended fix High confidence

Illustrator 28.7.9 or 29.7 (or later)

  1. Check the current Adobe Illustrator version by opening Illustrator and going to Help > About Adobe Illustrator
  2. Close Adobe Illustrator completely before updating
  3. Open Adobe Creative Cloud desktop app or navigate to helpx.adobe.com/illustrator
  4. Download and install Illustrator version 28.7.9 (for 28.x users) or version 29.7 (for 29.x users) or later
  5. After installation, restart Adobe Illustrator and verify the new version under Help > About Adobe Illustrator
Caveat Standard update; review Adobe's release notes for any workflow changes in new versions

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

Fix this in Illustrator Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-49563 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