CVE-2024-22914: swftools · Use After Free
Affects swftoolsSource CVE Database V5
Not known to be exploited · CVSS 5.5 Medium.
Data as of 26 Oct 2026, 11:07 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 19 Jan 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubmatthiaskramm/swftoolspkg:github/matthiaskramm/swftoolsOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate CVE-2024-22914, organizations should first restrict access to systems running SWFTools, ensuring only trusted users can execute or interact with the software. Avoid processing untrusted or malicious SWF files that could trigger the vulnerability. Implement application whitelisting and user privilege restrictions to limit exposure. Monitor system logs and application behavior for crashes or anomalies related to SWFTools usage. Since no official patches are available yet, consider isolating SWFTools in sandboxed or containerized environments to contain potential crashes. Evaluate alternative tools or updated versions that do not exhibit this vulnerability. Engage with the SWFTools community or maintainers to track patch releases and apply updates promptly once available. Additionally, conduct code audits or use memory safety tools to detect similar issues if custom builds or forks of SWFTools are in use. Regular backups and disaster recovery plans will help mitigate availability impacts if denial of service occurs.
Description
A heap-use-after-free was found in SWFTools v0.9.2, in the function input at lex.swf5.c:2620. It allows an attacker to cause denial of service.