CVE-2025-24448
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.2.1, 28.7.4 and earlier are affected by an out-of-bounds read vulnerability that could lead to disclosure of sensitive memory. An attacker could leverage this vulnerability to bypass mitigations such as ASLR. 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 29.2.1, 28.7.4 and earlier contain an out-of-bounds read vulnerability that allows disclosure of sensitive memory contents when processing a specially crafted malicious file. This memory disclosure can be leveraged by an attacker to bypass ASLR (Address Space Layout Randomization) mitigations, potentially facilitating further exploitation. Successful exploitation requires user interaction in the form of opening a malicious 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.5>= 29.0, < 29.3CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
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 installedCheck for Adobe Illustrator in the system. On Windows, inspect Program Files/Adobe or use PowerShell: Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*' | Where-Object {$_.DisplayName -like '*Adobe Illustrator*'}. On macOS, check /Applications for Adobe Illustrator.appAffected if Adobe Illustrator is found on the system
-
Identify the installed Illustrator versionOpen Adobe Illustrator, then go to Help > About Adobe Illustrator, or on Windows right-click the application in Control Panel > Programs and check the Version fieldAffected if The displayed version falls within 28.0 through 28.7.4 OR 29.0 through 29.2.1 (any version >= 28.0 but < 28.7.5, OR >= 29.0 but < 29.3)
-
Confirm version is in vulnerable rangeCompare your installed version number to the affected ranges: 28.0 <= version < 28.7.5 OR 29.0 <= version < 29.3. For example, versions 28.5, 28.7, 28.7.4, 29.0, 29.1, 29.2, and 29.2.1 are all vulnerableAffected if Your version matches the affected ranges - you are running a vulnerable release that can disclose memory when processing specially crafted files
You are affected if Adobe Illustrator is installed and the installed version is 28.0 through 28.7.4 or 29.0 through 29.2.1 (any version >= 28.0 but < 28.7.5, or >= 29.0 but < 29.3).
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.529.3
Update Adobe Illustrator to the latest patched version released by Adobe. Until patched, exercise caution when opening files from untrusted sources, as the vulnerability is triggered upon file open.
Illustrator 28.7.5 (or later) for 28.x line; Illustrator 29.3 (or later) for 29.x line
- Open Adobe Creative Cloud desktop application or launch Illustrator
- Navigate to the Updates section or check for available updates
- Update Adobe Illustrator to version 28.7.5 or later for the 28.x release line, OR update to version 29.3 or later for the 29.x release line
- Alternatively, download the latest version of Illustrator from the Adobe website (helpx.adobe.com) and reinstall
- Restart Illustrator after the update completes
- Verify the installed version by going to Help > About Adobe Illustrator and confirm the version number is >= 28.7.5 or >= 29.3
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-24448 — 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-24448 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