Premiere Pro | Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') (CWE-22)
Affects Adobe Premiere 26.5.2 and earlier and 25.6.6 and earlier on Windows and macOS. Adobe has not given a severity rating here, and no fixed version is listed in the checked facts.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Adobe Premiere 26.5.2 and earlier Adobe Premiere 25.6.6 and earlier Windows or macOS platform
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 17/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
Premiere Pro contains a path traversal flaw that can be reached locally by an attacker with no login and no user action needed. An attacker could use it to read sensitive files and directories outside the intended access scope.
Read the original description
Premiere Pro is affected by an Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability that could lead to arbitrary file system read. An attacker could exploit this vulnerability to access sensitive files and directories outside the intended access scope. Exploitation of this issue does not require user interaction. Scope is changed.
Who should check
Teams running Adobe Premiere 26.5.2 and earlier or 25.6.6 and earlier on Windows and macOS
Read the source excerpt
“Adobe has released a priority 3 security update for Adobe Premiere”
cve.now Index
- Exploitation0/40No signal
- Exposure5/25Specific setups only
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.1/10CVSS 7.1
- No patch5/5No patch listed yet
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 27 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Adobe Premiere 26.5.2 and earlier Adobe Premiere 25.6.6 and earlier Windows or macOS platformWorkaround: The checked facts do not list a workaround for this issue. Until Adobe publishes a fix, follow Adobe's advisory for any interim guidance.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-110090 (Premiere Pro | Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') (CWE-22)), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-110090 (entry last updated 2026-11-10):
Affected:
- Adobe Premiere: through 26.5.2
- Adobe Premiere: through 25.6.6
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Adobe Premiere 26.5.2 and earlier (source: https://www.adobe.com/trust/security/products/premiere/apsb26-101.html)
- Adobe Premiere 25.6.6 and earlier (source: https://www.adobe.com/trust/security/products/premiere/apsb26-101.html)
- Windows or macOS platform (source: https://www.adobe.com/trust/security/products/premiere/apsb26-101.html)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: local access, no login, no user action.
CISA KEV: CVE-2026-110090 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-110090 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.adobe.com/trust/security/products/premiere/apsb26-101.html
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-110090
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-110090.Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- First seen by cve.now
- Record last updated
Affected versions
- Adobe Premiere
through 26.5.2
- Adobe Premiere
through 25.6.6
Evidence 3
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-110090
Is CVE-2026-110090 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A path traversal flaw lets Premiere read files on the file system, including sensitive files and directories outside its intended scope.Source: adobe.com
Which versions are affected by CVE-2026-110090?
Premiere: through 26.5.2. Premiere: through 25.6.6.Source: cve.now feed data
Am I affected, and how do I check?
Adobe Premiere 26.5.2 and earlier, and Adobe Premiere 25.6.6 and earlier, on Windows or macOS. To check a installed copy, look up its version in Premiere's About screen.Source: adobe.com
How do I fix CVE-2026-110090?
The checked facts do not name a fixed version, so no upgrade target can be confirmed. Check Adobe's advisory for a patched release and install it when it is available.Source: adobe.com
What if there's no patch?
The checked facts do not list a workaround for this issue. Until Adobe publishes a fix, follow Adobe's advisory for any interim guidance.Source: adobe.com