CVE-2026-34662
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 · uneditedIllustrator versions 29.8.6, 30.3 and earlier are affected by a NULL Pointer Dereference vulnerability that could result in an application denial-of-service. An attacker could exploit this vulnerability to crash the application, leading to a denial-of-service condition. 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 · moderate confidenceA NULL Pointer Dereference vulnerability in Adobe Illustrator versions 29.8.6, 30.3 and earlier allows attackers to crash the application by having victims open maliciously crafted files. The vulnerability occurs when processing file data without proper NULL pointer validation during file parsing operations.
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>= 29.0, < 29.8.7>= 30.0, < 30.4CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Adobe Illustrator is installedOn Windows check for the installation folder at C:\Program Files\Adobe\Adobe Illustrator [Version] or query the Windows Registry under HKLM\SOFTWARE\Adobe\Illustrator. On macOS check /Applications/Adobe Illustrator folder.Affected if Adobe Illustrator is not installed on the system.
-
Identify the installed Adobe Illustrator versionOn Windows, open Adobe Illustrator and go to Help > About Adobe Illustrator to display the exact version number, or check the version value in the Windows Registry at HKLM\SOFTWARE\Adobe\Illustrator\InstallPath. On macOS, right-click the application in /Applications, select Get Info, and read the Version field.Affected if The installed version cannot be determined.
-
Compare installed version against affected rangesReview the version identified in the previous step. The affected version ranges are: 29.0 through 29.8.6 (inclusive), and 30.0 through 30.3 (inclusive). Versions 29.8.7 and above, or 30.4 and above, are not affected.Affected if The installed version falls within 29.0 to 29.8.6 OR 30.0 to 30.3.
-
Assess file handling exposureDetermine whether the system or user profile frequently opens AI, EPS, or other Illustrator file formats from external or untrusted sources, such as email attachments, downloads from the internet, or network shares from other users.Affected if Users routinely open Illustrator files from untrusted or unknown sources without prior validation.
A system is affected if Adobe Illustrator is installed with version 29.0 through 29.8.6 or version 30.0 through 30.3, and users open Illustrator files from untrusted sources.
Generated from the published advisory. Verify against your own configuration.
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 · scoped29.8.730.4
Update Adobe Illustrator to version 29.8.7 or later (for 29.x branch) or 30.4 or later (for 30.x branch) to receive the patch. Avoid opening files from untrusted sources until the update is applied.
Illustrator 29.8.7 or later for 29.x branch; Illustrator 30.4 or later for 30.x branch
- 1. Determine the currently installed Adobe Illustrator version by opening Illustrator and navigating to Help > About Adobe Illustrator
- 2. If running version 29.0 through 29.8.6, upgrade to version 29.8.7 or later
- 3. If running version 30.0 through 30.3, upgrade to version 30.4 or later
- 4. Download the latest Adobe Illustrator version from the official Adobe website or through Creative Cloud desktop application
- 5. Install the updated version and restart the application
- 6. Verify the version by checking Help > About Adobe Illustrator to confirm the installed version contains the fix
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-34662 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-34662 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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