dbcve.org
IllustratorApplication · Adobe

CVE-2025-54283

HIGH · 7.8 CVSS v3.1 Published 2025-10-14
Fix available
A fix is available. Upgrade to 28.7.10 / 29.8 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.7, 28.7.9 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.7, 28.7.9 and earlier contain an out-of-bounds write vulnerability in the file parsing logic. When a user opens a specially crafted malicious file, the vulnerability allows memory corruption that can be leveraged for arbitrary code execution in the context of the current user session.

MitigationUpdate Adobe Illustrator to the latest patched version as provided by Adobe's security advisory. Until patched, advise users to avoid opening files from untrusted or 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:>= 28.0, < 28.7.10>= 29.0, < 29.8

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. Check Adobe Illustrator installed version on Windows
    Open Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Illustrator\ (or HKEY_CURRENT_USER for per-user installs). Check the "Version" or "InstallVersion" value in the folder for your installed version (e.g., 28.x or 29.x).
    Affected if The version is 28.0 through 28.7.9, or 29.0 through 29.7 (any version below 28.7.10 or 29.8).
  2. Check Adobe Illustrator installed version on macOS
    Open Finder, navigate to /Applications/Adobe Illustrator, right-click and select "Get Info", or open Illustrator and go to Help > About Illustrator. Note the version number displayed.
    Affected if The version is 28.0 through 28.7.9, or 29.0 through 29.7 (any version below 28.7.10 or 29.8).
  3. Confirm file parsing is active
    The vulnerability is triggered when Illustrator parses specially crafted malicious files. This feature is enabled by default whenever the application opens files (AI, EPS, PDF, or other supported formats). No additional configuration check is needed.
    Affected if You use Adobe Illustrator to open files from any source, which is the normal and expected use of the software.

You are affected if your installed Adobe Illustrator version falls within 28.0 to 28.7.9 or 29.0 to 29.7, and you open files (which is the standard use case for the application).

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.10 / 29.8 or later
Fixed in 28.7.1029.8
Interim mitigation

Update Adobe Illustrator to the latest patched version as provided by Adobe's security advisory. Until patched, advise users to avoid opening files from untrusted or unknown sources.

Recommended fix High confidence

Illustrator 28.7.10 or later, or Illustrator 29.8 or later

  1. Open Adobe Creative Cloud desktop application or visit the Adobe Illustrator download page at helpx.adobe.com
  2. Navigate to the Illustrator section and check for available updates
  3. Download and install Illustrator version 28.7.10 or later (for the 28.x line), or version 29.8 or later (for the 29.x line)
  4. Restart Illustrator after the update completes
  5. Verify the installed version by going to Help > About Illustrator to confirm the version number matches 28.7.10+ or 29.8+

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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