CVE-2025-21134
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 on iPad versions 3.0.7 and earlier are affected by an Integer Underflow (Wrap or Wraparound) 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 confidenceAdobe Illustrator on iPad versions 3.0.7 and earlier contain an integer underflow vulnerability where malformed input in a malicious file can cause wraparound during integer arithmetic, leading to arbitrary code execution in the context of the current user. Exploitation requires the victim to open a specially crafted 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< 3.0.8CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify Adobe Illustrator on iPad is installedCheck your iPad's App Library or home screen for the Adobe Illustrator app iconAffected if The app is present on the device
-
Check the installed app versionOpen the App Store, tap your profile icon, tap Purchased, find Adobe Illustrator, and note the version number shown. Alternatively, open Adobe Illustrator, go to Help > About to view version infoAffected if Version displayed is 3.0.7 or earlier, or any version below 3.0.8
-
Confirm vulnerability applicabilityNo additional configuration check needed - the vulnerability triggers upon opening a specially crafted malicious fileAffected if Running any version below 3.0.8 means the integer underflow vulnerability is present and could be triggered by opening a malformed file
You are affected if Adobe Illustrator on iPad version 3.0.7 or earlier is installed on your device (any version less than 3.0.8).
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 · scoped3.0.8
Update Adobe Illustrator on iPad to a version newer than 3.0.7. Avoid opening untrusted or unexpected files received from unverified sources.
Illustrator on iPad 3.0.8
- Open the App Store on the iPad
- Tap on your profile icon in the top right corner
- Scroll down to the 'Available Updates' section
- Locate 'Adobe Illustrator' in the list of pending updates
- Tap 'Update' next to Adobe Illustrator
- Wait for the download and installation to complete
- Verify the installed version is 3.0.8 or later by opening the app and checking the version in Settings > Adobe Illustrator
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-21134 — 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-21134 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