IllustratorApplication · Adobe

CVE-2026-48337

HIGH · 7.8 CVSS v3.1 Published 2026-07-14
Fix available
A fix is available. Upgrade to 29.8.9 / 30.6 or later.
See remediation →
81/100
Remediation priority · High
No privileges 5 weeks old

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 is 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 · moderate confidence

Adobe Illustrator contains an out-of-bounds write vulnerability that allows memory corruption beyond allocated buffer boundaries. Successful exploitation permits arbitrary code execution within the context of the user who opened the malicious file. The vulnerability requires victim interaction, specifically opening a crafted malicious file.

MitigationApply the official Adobe security patch for Illustrator when available. Until then, exercise caution by not opening files from untrusted sources and consider restricting file handling privileges for the application.

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.9>= 30.0, < 30.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. Verify Adobe Illustrator is installed
    Check for Adobe Illustrator installation: On Windows, look in C:\Program Files\Adobe\Adobe Illustrator [Version] or check Programs and Features. On macOS, check /Applications for Adobe Illustrator.app
    Affected if Adobe Illustrator is present on the system
  2. Retrieve installed version number
    On Windows, right-click the application in Programs and Features and select Properties, or run 'Get-ItemProperty' in PowerShell for the Illustrator.exe path. On macOS, right-click Adobe Illustrator.app and select Get Info to view the version
    Affected if Unable to determine the version number
  3. Compare version against first affected range
    Check if the installed version is >= 29.0 and < 29.8.9. For example, versions 29.0 through 29.8.8 are affected
    Affected if Version falls within 29.0 to 29.8.8 inclusive
  4. Compare version against second affected range
    Check if the installed version is >= 30.0 and < 30.6. For example, versions 30.0 through 30.5 are affected
    Affected if Version falls within 30.0 to 30.5 inclusive

The system is affected if Adobe Illustrator is installed and the version number falls within 29.0-29.8.8 or 30.0-30.5, since these ranges contain the out-of-bounds write vulnerability exploitable via malicious 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.9 / 30.6 or later
Fixed in 29.8.930.6
Interim mitigation

Apply the official Adobe security patch for Illustrator when available. Until then, exercise caution by not opening files from untrusted sources and consider restricting file handling privileges for the application.

Recommended fix High confidence

Adobe Illustrator 29.8.9 or 30.6 (or later)

  1. Close Adobe Illustrator if it is currently running
  2. Update Adobe Illustrator to version 29.8.9 or later for the 29.x branch, or version 30.6 or later for the 30.x branch
  3. Restart Illustrator after the update
  4. Verify the installed version matches the fixed release (Help > About Adobe Illustrator)

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-48337 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