CVE-2023-25862
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 version 26.5.2 (and earlier) and 27.2.0 (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 26.5.2 and earlier (26.x) and 27.2.0 and earlier (27.x) contain an out-of-bounds read vulnerability. When a user opens a maliciously crafted file, the application reads memory outside allocated buffers, potentially exposing sensitive memory contents. This information leak can be leveraged to defeat ASLR (Address Space Layout Randomization) protections, making subsequent exploitation easier.
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<= 26.5.2>= 27.0.0, < 27.3.1CVSS 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.
-
Check Adobe Illustrator installed versionOpen Adobe Illustrator, go to Help > About Adobe Illustrator to display the version number. Alternatively, check the installed version via the Creative Cloud desktop application or system program list.Affected if The displayed version is 26.5.2 or earlier, or falls between 27.0.0 and 27.3.0 inclusive.
-
Identify if file parsing is in useDetermine whether Adobe Illustrator is used to open or import files, particularly .ai (Adobe Illustrator), EPS, PDF, or other supported vector graphic formats that trigger the vulnerable parsing code path.Affected if The application is routinely used to open files, as the out-of-bounds read triggers during file parsing operations.
-
Assess file source exposureReview user behavior or organizational policies regarding file handling. Identify whether Adobe Illustrator is used to open files received from external sources, email attachments, or downloaded content.Affected if Users open files from untrusted or unknown sources, as exploitation requires the user to deliberately open a maliciously crafted file.
You are affected if Adobe Illustrator version is 26.5.2 or earlier, or 27.0.0 through 27.3.0, and the application is used to open files from potentially 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 · scoped27.3.1
Apply the vendor-supplied security patch by updating Adobe Illustrator to a version newer than 26.5.2 and 27.2.0. Additionally, enforce user awareness to avoid opening files from untrusted sources, as exploitation requires user interaction.
Adobe Illustrator 27.3.1 or later (or 26.5.3 or later for the 26.x release line)
- 1. Ensure Adobe Illustrator is fully closed before updating
- 2. Open Adobe Creative Cloud desktop application
- 3. Navigate to the 'Apps' section where Illustrator is listed
- 4. Click the 'Update' button next to Adobe Illustrator
- 5. Wait for the update to download and install completely
- 6. Restart Illustrator after the update completes
- 7. Verify the installed version by going to Help > About Adobe Illustrator
- 8. Confirm the version shows 27.3.1 (or later in the 27.x line) or 26.5.3 (or later in the 26.x line)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-25862 — 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-2023-25862 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