dbcve.org
IllustratorApplication · Adobe

CVE-2025-49568

MEDIUM · 5.5 CVSS v3.1 Published 2025-08-12
Fix available
A fix is available. Upgrade to 28.7.9 / 29.7 or later.
See remediation →
58/100
Remediation priority · Elevated
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 a Use After Free vulnerability that could lead to disclosure of sensitive memory. 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 Use After Free vulnerability in versions 28.7.8, 29.6.1 and earlier that can lead to disclosure of sensitive memory. The vulnerability is triggered when a victim opens a specially crafted malicious file, requiring user interaction for exploitation.

MitigationUpdate Adobe Illustrator to a patched version beyond 29.6.1 and avoid opening files from untrusted 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.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
None
Availability
None

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

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. Identify installed Adobe Illustrator version
    Open Adobe Illustrator, then go to Help > About Adobe Illustrator. Alternatively, on Windows right-click the Illustrator.exe file in Program Files and select Properties > Details; on macOS right-click the .app in Applications and select Get Info.
    Affected if The displayed version falls within 28.0 to 28.7.8 inclusive, or 29.0 to 29.6.1 inclusive.
  2. Check Windows Registry for version
    Open Registry Editor (regedit), navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Adobe Illustrator and look for the Version or VersionNumber value.
    Affected if The registry version value matches the affected ranges (28.0-28.7.8 or 29.0-29.6.1).
  3. Locate Illustrator executable on disk
    Navigate to C:\Program Files\Adobe\Adobe Illustrator (folder name contains version number) on Windows, or /Applications/Adobe Illustrator on macOS. Check the folder name for the version number.
    Affected if The folder version matches the affected ranges (28.0-28.7.8 or 29.0-29.6.1).

A system is affected if Adobe Illustrator is installed with any version from 28.0 through 28.7.8, or from 29.0 through 29.6.1.

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

Update Adobe Illustrator to a patched version beyond 29.6.1 and avoid opening files from untrusted sources.

Recommended fix High confidence

Upgrade to Illustrator 28.7.9 or later, or 29.7 or later

  1. Verify your current Adobe Illustrator version by opening the application and navigating to Help > About Adobe Illustrator
  2. Close Adobe Illustrator if it is currently running
  3. For macOS: Use the Creative Cloud desktop application to check for updates and install the latest version
  4. For Windows: Use the Creative Cloud desktop application or check for updates via Help > Check for Updates
  5. Install version 28.7.9 or later for the 28.x product line
  6. Alternatively, install version 29.7 or later for the 29.x product line
  7. After installation, verify the fix by opening Illustrator and confirming the version at Help > About Adobe Illustrator shows 28.7.9 or higher, or 29.7 or higher
  8. Exercise caution when opening files from untrusted sources to mitigate the user interaction requirement for 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-49568 — 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-49568 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