dbcve.org
IllustratorApplication · Adobe

CVE-2025-61820

HIGH · 7.8 CVSS v3.1 Published 2025-11-11
Fix available
A fix is available. Upgrade to 29.8.3 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.10, 29.8.2 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 contains a heap-based buffer overflow vulnerability when parsing specially crafted files. An attacker can exploit this by enticing a user to open a malicious file, leading to arbitrary code execution in the context of the current user. This is a classic file-parsing vulnerability with user-interaction requirements.

MitigationUpdate Adobe Illustrator to the latest version to remediate this vulnerability. Until patched, users should not open 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.10>= 29.0, < 29.8.3

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. Identify the installed Adobe Illustrator version on Windows
    Open Registry Editor and navigate to HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\Illustrator.exe, then read the (Default) value to locate the executable path. Right-click the Illustrator.exe file in that location, select Properties, and view the Details tab for the Product Version.
    Affected if The product version falls within 28.0 through 28.7.10, or 29.0 through 29.8.2
  2. Identify the installed Adobe Illustrator version on macOS
    Open Finder, go to /Applications, locate the Adobe Illustrator folder, right-click Adobe Illustrator.app, select Get Info, and view the Version field under General.
    Affected if The product version falls within 28.0 through 28.7.10, or 29.0 through 29.8.2
  3. Compare your version against the affected ranges
    Using the version number obtained from the previous step, verify whether it is greater than or equal to 28.0 and less than or equal to 28.7.10, OR greater than or equal to 29.0 and less than 29.8.3.
    Affected if Your installed version matches either range (28.0-28.7.10 or 29.0-29.8.2), indicating the vulnerability is present
  4. Confirm the file parsing attack vector
    Understand that the vulnerability is triggered when Illustrator parses specially crafted files. This is a core function of the software and applies to any file opened in the application.
    Affected if You use Adobe Illustrator to open files, which is the normal and intended use of the software

If your installed Adobe Illustrator version is 28.0 through 28.7.10 or 29.0 through 29.8.2, your environment is affected by this vulnerability when opening 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 29.8.3 or later
Fixed in 29.8.3
Interim mitigation

Update Adobe Illustrator to the latest version to remediate this vulnerability. Until patched, users should not open files from untrusted sources.

Recommended fix High confidence

Adobe Illustrator 29.8.3 or later (or latest 29.x release)

  1. 1. Open Adobe Illustrator on your system
  2. 2. Navigate to Help > Check for Updates (or use the Creative Cloud desktop app)
  3. 3. If an update is available, download and install Adobe Illustrator version 29.8.3 or later
  4. 4. Alternatively, manually download the latest version from the Adobe website or Creative Cloud desktop application
  5. 5. Restart Illustrator after the update completes
  6. 6. Verify the installed version by going to Help > About Adobe Illustrator
Caveat Users on the 28.x branch will need to migrate to the 29.x branch; ensure compatibility with existing workflows and plugins

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

Fix this in Illustrator Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,800
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,880.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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