dbcve.org
IllustratorApplication · Adobe

CVE-2025-49527

HIGH · 7.8 CVSS v3.1 Published 2025-07-08
Fix available
A fix is available. Upgrade to 28.7.8 / 29.6 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.6, 29.5.1 and earlier are affected by a Stack-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 contains a stack-based buffer overflow vulnerability in versions 28.7.6, 29.5.1 and earlier. When a user opens a specially crafted malicious file, the overflow can be triggered, allowing arbitrary code execution in the context of the current user's privileges.

MitigationDo not open untrusted or unsolicited .ai or related files in Adobe Illustrator. Apply vendor patches as soon as they become available and implement file origin restrictions to mitigate exposure.

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.8>= 29.0, < 29.6

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. Verify Adobe Illustrator is installed
    Windows: Open Control Panel > Programs and Features, or check C:\Program Files\Adobe\Adobe Illustrator [Version]\Support Files\Contents\Windows\Adobe Illustrator.exe. Mac: Check /Applications/Adobe Illustrator [Version].app
    Affected if Adobe Illustrator software is present on the system
  2. Determine the installed version number
    Windows: Right-click Adobe Illustrator in Programs and Features and select Properties > Details > File Version, or open Illustrator and go to Help > About Adobe Illustrator. Mac: Open Illustrator and go to Adobe Illustrator > About Adobe Illustrator, or right-click the .app in Applications and select Get Info
    Affected if Unable to determine the version number from the installed software
  3. Compare against affected version ranges
    Match the installed version to the following ranges: 28.0.0 through 28.7.7.x, or 29.0.0 through 29.5.x. Versions 28.7.8 and above, and 29.6 and above are NOT affected
    Affected if Installed version is 28.0.0 to 28.7.7.x OR 29.0.0 to 29.5.x (these versions contain the vulnerability)

User is affected if Adobe Illustrator is installed and the version falls within 28.0 to 28.7.7 or 29.0 to 29.5.x ranges, since the buffer overflow triggers when opening specially crafted files in those versions

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.8 / 29.6 or later
Fixed in 28.7.829.6
Interim mitigation

Do not open untrusted or unsolicited .ai or related files in Adobe Illustrator. Apply vendor patches as soon as they become available and implement file origin restrictions to mitigate exposure.

Recommended fix High confidence

Illustrator 28.7.8 or later, or Illustrator 29.6 or later

  1. Close Adobe Illustrator if it is currently running
  2. Open Adobe Creative Cloud desktop application or navigate to helpx.adobe.com
  3. Check for available updates for Adobe Illustrator
  4. Install Illustrator version 28.7.8 or later (for 28.x line users) OR version 29.6 or later (for 29.x line users)
  5. Restart Adobe Illustrator after the update completes
  6. Verify the installed version by going to Help > About Adobe Illustrator

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

Fix this in Illustrator Scoped from the published advisory
  • Consultation3.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,620
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-49527 — 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-49527 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