Skip to content
Applications

CVE-2026-48350

8.6
High
EPSS 0.33%Patch availableJul 15, 2026

Path traversal in Adobe Animate allows file access and code execution via malicious files.

common questions

Is CVE-2026-48350 being exploited?

Not confirmed. CVE-2026-48350 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.33% probability of exploitation in the next 30 days.

How severe is CVE-2026-48350?

CVE-2026-48350 is rated High with a CVSS score of 8.6. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-48350?

Yes. A fix has been recorded for CVE-2026-48350. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-48350 affect?

CVE-2026-48350 affects Adobe Animate, Windows/macOS clients running Animate. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-48350?

Apply vendor patch when released; block or scan untrusted Animate files and restrict file handling.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Adobe AnimateWindows/macOS clients running Animate
impact

Attackers can traverse directories to access sensitive files and execute arbitrary code as the current user when a victim opens a crafted file.

action required

Patch when possible

affected versions
Adobe Adobe Animate 2023
  • affected<= 23.0.15
vendor says fixed in23.0.16
Adobe Adobe Animate 2024
  • affected<= 24.0.13
vendor says fixed in24.0.14

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free