dbcve.org
IllustratorApplication · Adobe

CVE-2025-49526

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 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 when parsing specially crafted files. An attacker can exploit this by convincing a user to open a malicious .ai file, potentially executing arbitrary code with the privileges of the running user.

MitigationUpdate Adobe Illustrator to the latest patched version. Avoid opening untrusted or unsolicited 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.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. Check Adobe Illustrator version on Windows
    Open Control Panel > Programs and Features, locate Adobe Illustrator in the list, and note the version in the Version column. Alternatively, open Adobe Illustrator, go to Help > About Adobe Illustrator.
    Affected if The version is 28.0 through 28.7.7, or 29.0 through 29.5.x
  2. Check Adobe Illustrator version on macOS
    Open Finder, navigate to Applications folder, right-click Adobe Illustrator, select Get Info, and note the version number under General.
    Affected if The version is 28.0 through 28.7.7, or 29.0 through 29.5.x
  3. Verify exact version against affected ranges
    Compare your installed version number to the affected ranges: version 28.x less than 28.7.8, or version 29.x less than 29.6. The first affected range starts at 28.0 inclusive.
    Affected if Installed version falls within 28.0 <= version < 28.7.8 OR 29.0 <= version < 29.6
  4. Confirm the attack vector requires user action
    Note that exploitation requires a user to open a specially crafted .ai file. Check if your organization commonly opens .ai files from untrusted sources.
    Affected if Users routinely open .ai files from email attachments, downloads, or other untrusted sources without verification

You are affected if Adobe Illustrator is installed at version 28.0 through 28.7.7 or version 29.0 through 29.5, and users may open .ai files from untrusted sources.

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

Update Adobe Illustrator to the latest patched version. Avoid opening untrusted or unsolicited files from unknown sources.

Recommended fix High confidence

Adobe Illustrator 28.7.8 or 29.6 (or later)

  1. Check current Adobe Illustrator version by opening the application and navigating to Help > About Illustrator
  2. Close any open instances of Adobe Illustrator
  3. Backup important Illustrator files and preferences if desired
  4. Navigate to the Adobe Creative Cloud desktop application or visit helpx.adobe.com to download the latest version
  5. Download and install Adobe Illustrator version 28.7.8 (or version 29.6 or later)
  6. Launch Illustrator and verify the version by checking Help > About Illustrator to confirm the update was successful
  7. Exercise caution when opening files from untrusted sources to avoid potential exploitation

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-49526 — 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-49526 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