CVE-2025-49524
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 28.7.6, 29.5.1 and earlier are affected by a NULL Pointer Dereference vulnerability that could lead to application denial-of-service. An attacker could exploit this vulnerability to crash the application, causing a disruption in service. 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 confidenceAdobe Illustrator versions 28.7.6, 29.5.1 and earlier contain a NULL pointer dereference vulnerability that can be triggered when a user opens a maliciously crafted file. The vulnerability causes the application to crash, resulting in denial-of-service conditions. Successful exploitation requires user interaction in the form of opening the crafted file.
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>= 28.0, < 28.7.8>= 29.0, < 29.6CVSS 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.
-
Determine installed Adobe Illustrator versionOn Windows, open Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Illustrator\[Version] (e.g., 28 or 29) and read the 'Version' value. On macOS, right-click Adobe Illustrator in Applications, select Get Info, and check the version number. Alternatively, open Illustrator and go to Help > About Adobe Illustrator.Affected if The displayed version falls within the ranges 28.0 to 28.7.7 or 29.0 to 29.5.x (any version shown that is less than 28.7.8 in the 28.x line, or less than 29.6 in the 29.x line).
-
Verify exact version against affected rangesCompare the installed version number to the known affected ranges: version 28.x where x is less than 8 (28.0 through 28.7.7), or version 29.x where x is less than 6 (29.0 through 29.5.x).Affected if The installed version is 28.7.6, 28.7.7, 29.5.1, or any other version in the ranges 28.0 to 28.7.7 or 29.0 to 29.5.x.
If Adobe Illustrator is installed and its version is 28.0 through 28.7.7 or 29.0 through 29.5.x, the environment is affected by this vulnerability.
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 · scoped28.7.829.6
Users should avoid opening files from untrusted or unknown sources. Organizations should ensure Adobe Illustrator is updated to the latest patched version once released by Adobe. Consider implementing file type restrictions or sandboxing for Illustrator in high-security environments.
Adobe Illustrator 28.7.8 (or later 28.x) / 29.6 (or later 29.x)
- Close Adobe Illustrator if it is currently running
- Verify your current version by going to Help > About Adobe Illustrator in the menu
- Download Adobe Illustrator version 28.7.8 or later (for 28.x branch) or version 29.6 or later (for 29.x branch) from the official Adobe website at helpx.adobe.com
- Run the installer and follow the prompts to update the application
- Restart Illustrator after the update completes
- Verify the update was successful by checking the version number again
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.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 $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-49524 — 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-2025-49524 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