VulnerabilityPublished 5 Mar 2024Updated 26 Nov 2024

CVE-2024-26337: swftools

Affects swftoolsSource CVE Database V5

Not known to be exploited · CVSS 4.3 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

4.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.5% chance of exploitation in 30 days – higher than 48% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 5 Mar 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
GitHubmatthiaskramm/swftools`pkg:github/matthiaskramm/swftools`Other threats	Affected =0.9.2	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-26337, organizations should first identify all instances of swftools v0.9.2 in their environments. Until an official patch is released, restrict network access to systems running swftools to trusted users and networks only, minimizing exposure to potential attackers. Run swftools processes with the least privileges necessary to limit the impact of exploitation. Implement monitoring and alerting for abnormal crashes or service disruptions related to swftools. Consider isolating swftools usage in sandboxed or containerized environments to contain crashes and prevent broader system impact. Review and harden access controls to prevent unauthorized users from executing swftools commands. Stay informed about vendor updates or patches and apply them promptly once available. If possible, evaluate alternative tools or updated versions that do not contain this vulnerability. Conduct regular backups of critical data and workflows to ensure recovery in case of disruption.

Description

swftools v0.9.2 was discovered to contain a segmentation violation via the function s_font at swftools/src/swfc.c.

Impact

The primary impact of CVE-2024-26337 is denial of service due to application crashes caused by the segmentation violation. Organizations using swftools in production environments, especially those processing SWF files in automated pipelines or multimedia applications, may experience service interruptions. This can lead to operational delays, reduced availability of services, and potential financial or reputational damage if critical workflows are disrupted. Since the vulnerability requires low privileges but no user interaction, it could be exploited by insiders or attackers who have gained limited access to affected systems. The absence of confidentiality or integrity impact reduces the risk of data breaches or unauthorized data modification. However, the disruption of service availability can still have significant consequences, particularly in environments where swftools is integrated into larger systems or where uptime is critical. The lack of known exploits currently limits immediate widespread risk, but the vulnerability should be addressed proactively to prevent future exploitation.

References

github.com/matthiaskramm/swftools/issues/223 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Feb 2026, 10:52 UTC

Technical details

References

Community reviews

Related threats