CVE-2026-27269: Premiere Pro | Out-of-bounds Read (CWE-125)
Premiere Pro versions 25.5 and earlier are affected by an out-of-bounds read vulnerability when parsing a crafted file, which could result in a read past the end of an allocated memory structure. An attacker could leverage this vulnerability to execute code in the context of the current user. Exploitation of this issue requires user interaction in that a victim must open a malicious file.
Security readout for executives and security teams
Plain-English summary
Adobe Premiere Pro 25.5 and earlier can execute attacker-controlled code if a user opens a maliciously crafted file. Successful exploitation would run with the user’s permissions, potentially exposing data, modifying files, or disrupting the workstation.
Executive priority
Treat this as a high-priority endpoint remediation issue, particularly for creative teams receiving external files. Expedite Adobe-directed remediation and temporary file-handling controls, while avoiding claims of an active campaign without additional evidence.
Technical view
CVE-2026-27269 is an out-of-bounds read (CWE-125) in crafted-file parsing. The supplied CVSS 3.1 score is 7.8: local attack vector, low complexity, no prior privileges, required user interaction, unchanged scope, and high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is concentrated on endpoints running affected Premiere Pro versions, especially systems where users receive or open externally supplied project or media files. The supplied description identifies versions 25.5 and earlier; confirm exact product and version boundaries against Adobe’s advisory.
Exploitation context
Exploitation requires a victim to open a malicious file. The supplied bundle does not establish active exploitation, and the CVE is not identified as a KEV entry. No exploit availability, observed campaigns, indicators, or attack prevalence are provided.
Researcher notes
The narrative names Premiere Pro 25.5 and earlier, while structured affected data contains separate Premiere and Premiere Pro entries with 26.0 and 25.6 boundaries. Confirm exact SKU and version semantics with Adobe. The bundle provides no root-cause detail beyond CWE-125 and no exploit evidence or indicators.
Mitigation direction
Follow Adobe APSB26-28 guidance for every Premiere Pro 25.5-or-earlier installation.
Prioritize systems handling files from customers, contractors, shared storage, or unsolicited messages.
Restrict affected users from opening untrusted Premiere project or media files until remediation is confirmed.
Limit user privileges to reduce the impact of code executing in the current-user context.
Validation and detection
Inventory installed Premiere Pro versions across managed and unmanaged endpoints.
Confirm each affected installation’s remediation status against Adobe APSB26-28.
Verify deployment reporting with direct endpoint version checks on representative systems.
Review security telemetry for suspicious activity following the opening of externally sourced files.
Do not infer compromise solely from an affected installation; the bundle provides no indicators of compromise.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-125: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
2Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-125 · source CWE mapping
Out-of-bounds Read
Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.