CVE-2024-22956: swftools · Use After Free
Source CVE Database V5
Not known to be exploited · CVSS 7.8 High.
Data as of 26 Oct 2026, 11:42 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 28% 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:H/I:H/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-22956, European organizations should first identify any use of swftools 0.9.2 or related versions within their infrastructure. Since no official patches are currently linked, organizations should monitor for updates from the swftools maintainers or community. In the interim, consider the following specific actions: 1) Restrict access to systems running swftools to trusted users only, minimizing the risk of local exploitation. 2) Implement strict user privilege management to reduce the impact of potential exploitation, ensuring users have only necessary permissions. 3) Employ application whitelisting and behavior monitoring to detect anomalous activity related to swftools processes. 4) If feasible, replace or phase out swftools in favor of more secure or actively maintained alternatives for Flash file processing. 5) Conduct code audits or static analysis on the swftools source code if custom builds are used, to identify and remediate use-after-free patterns. 6) Educate users about the risks of interacting with untrusted Flash content or files processed by swftools to reduce the likelihood of triggering the vulnerability. 7) Maintain up-to-date backups and incident response plans to quickly recover from potential exploitation.
Description
swftools 0.9.2 was discovered to contain a heap-use-after-free vulnerability via the function removeFromTo at swftools/src/swfc.c:838