Skip to main content
VulnerabilityPublished Updated

CVE-2022-40008: SWFTools · Out-of-bounds Write

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 15:59 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.1% chance of exploitation in 30 days – higher than 67% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Sep 2022

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

AI-suggested

To mitigate CVE-2022-40008 effectively, European organizations should: 1) Identify and inventory all systems and applications using SWFTools or components that parse TrueType fonts or SWF files. 2) Monitor vendor communications and security advisories for patches or updates addressing this vulnerability; apply them promptly once available. 3) Implement strict input validation and sandboxing for any processes handling untrusted font or SWF files to limit the impact of potential exploitation. 4) Employ network segmentation and access controls to restrict exposure of vulnerable services to untrusted networks. 5) Use application whitelisting and endpoint detection and response (EDR) solutions to detect anomalous behavior indicative of exploitation attempts. 6) Where patching is not immediately possible, consider disabling or removing SWFTools utilities from critical systems or replacing them with alternative, secure tools. 7) Educate security and IT teams about the risks of heap-buffer overflows and the importance of scrutinizing multimedia file processing workflows. These steps go beyond generic advice by focusing on proactive identification, containment, and monitoring tailored to the specific nature of this vulnerability and its exploitation vectors.

Description

SWFTools commit 772e55a was discovered to contain a heap-buffer overflow via the function readU8 at /lib/ttf.c.

References

Community reviews

Loading reviews…