VulnerabilityPublished 10 Mar 2026Updated 27 Aug 2026

CVE-2026-27270: Adobe Illustrator Desktop 2026 · Out-of-bounds Read

Affects Adobe Illustrator Desktop 2026Source CVE Database V5

Compare

Not known to be exploited · CVSS 5.5 Medium.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score

5.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

Attack Vector: Local
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 10 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
AdobeIllustrator Desktop 2026	Affected <=30.1	Fixed in–
AdobeIllustrator Desktop 2025	Affected <=29.8.4	Fixed in–

AI-suggested

Monitor Adobe's official channels for patches addressing CVE-2026-27270 and apply updates promptly once released.
Implement strict file handling policies to restrict opening Illustrator files from untrusted or unknown sources, including email attachments and downloads.
Educate users about the risks of opening unsolicited or suspicious Illustrator files and encourage verification of file origins.
Employ endpoint security solutions capable of detecting anomalous file behaviors or memory access patterns related to Illustrator.
Use application whitelisting and sandboxing techniques to limit the impact of potential exploitation.
Consider network-level controls to block or quarantine suspicious file transfers involving Illustrator files.
Maintain regular backups of critical design data to mitigate potential indirect impacts of exploitation attempts.
Conduct internal audits to identify and isolate systems running vulnerable Illustrator versions, prioritizing their remediation.

Description

Illustrator versions 29.8.4, 30.1 and earlier are affected by an Out-of-bounds Read vulnerability that could lead to memory exposure. An attacker could leverage this vulnerability to access sensitive information stored in memory. Exploitation of this issue requires user interaction in that a victim must open a malicious file.

Impact

The primary impact of CVE-2026-27270 is the potential unauthorized disclosure of sensitive information stored in memory during Illustrator file processing. This can lead to leakage of confidential design data, intellectual property, or user credentials if such data resides in memory adjacent to the exploited buffer. While the vulnerability does not allow code execution or system compromise, the confidentiality breach can have serious consequences for organizations relying on Illustrator for sensitive projects. Attackers could leverage this flaw to gain insights into proprietary designs or internal information, potentially facilitating further targeted attacks or corporate espionage. Since exploitation requires user interaction, social engineering or phishing campaigns distributing malicious Illustrator files could be used to trigger the vulnerability. The impact is particularly significant for creative agencies, media companies, and enterprises with sensitive design workflows. The absence of known exploits in the wild reduces immediate risk but does not eliminate the threat, especially once exploit code becomes available.

CWE-125Out-of-bounds Read (opens in a new tab)
Base weaknessCWE Top 25 (2025): #8
The product reads data past the end, or before the beginning, of the intended buffer.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Architecture and Design · Language Selection
Use a language that provides appropriate memory abstractions.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
Attack patterns
Overread Buffers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

helpx.adobe.com/security/products/illustrator/apsb26-18.html (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 10 Mar 2026, 23:30 UTC

WeaknessesCWE-125

Technical details

References

Community reviews

Related threats