dbcve.org
IllustratorApplication · Adobe

CVE-2026-34661

HIGH · 7.8 CVSS v3.1 Published 2026-05-12
Fix available
A fix is available. Upgrade to 29.8.7 / 30.4 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 29.8.6, 30.3 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 versions 29.8.6, 30.3 and earlier contain an out-of-bounds write vulnerability that allows writing beyond allocated memory buffers. Successful exploitation enables arbitrary code execution in the context of the current user, triggered by opening a maliciously crafted file.

MitigationUpdate Adobe Illustrator to a version later than 29.8.6 and 30.3 as provided by Adobe's security advisory. Avoid opening untrusted .ai or related 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:>= 29.0, < 29.8.7>= 30.0, < 30.4

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
    Check for Adobe Illustrator in the Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\Illustrator.exe, or look in typical install directories such as C:\Program Files\Adobe\Adobe Illustrator 64 Bit or C:\Program Files (x86)\Adobe\Adobe Illustrator 64 Bit
    Affected if Adobe Illustrator is found on the system
  2. Determine installed Adobe Illustrator version
    Open Adobe Illustrator, go to Help > About Adobe Illustrator, or right-click the executable and select Properties > Details to view the File Version
    Affected if Unable to determine version or version cannot be read
  3. Compare version against affected ranges
    Compare your installed version number to the affected ranges: 29.0 through 29.8.6, or 30.0 through 30.3
    Affected if Installed version is 29.0, 29.1, 29.2, 29.3, 29.4, 29.5, 29.6, 29.7, 29.8, 29.8.1, 29.8.2, 29.8.3, 29.8.4, 29.8.5, 29.8.6, 30.0, 30.1, 30.2, or 30.3

You are affected if Adobe Illustrator versions 29.0 through 29.8.6 or 30.0 through 30.3 are installed on your system and you open 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 29.8.7 / 30.4 or later
Fixed in 29.8.730.4
Interim mitigation

Update Adobe Illustrator to a version later than 29.8.6 and 30.3 as provided by Adobe's security advisory. Avoid opening untrusted .ai or related files from unknown sources.

Recommended fix High confidence

Illustrator 29.8.7 (for 29.x branch) or Illustrator 30.4 (for 30.x branch)

  1. Check current Adobe Illustrator version by opening the application and navigating to Help > About Adobe Illustrator
  2. Close Adobe Illustrator completely
  3. If using version 29.0-29.8.6, upgrade to version 29.8.7
  4. If using version 30.0-30.3, upgrade to version 30.4
  5. Download the updated version from the official Adobe website or use the Creative Cloud desktop application to update
  6. Restart Illustrator after installation
  7. Verify the version by checking Help > About Adobe Illustrator to confirm the installed version
Caveat Adobe minor version updates typically maintain file format compatibility; verify with release notes for any specific feature changes

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

Fix this in Illustrator Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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