Skip to main content
CVE-2022-40674VulnerabilityPublished Updated

CVE-2022-40674: n/a

Source CVE Database V5

0

Not known to be exploited · CVSS 8.1 High : upgrade to 2.4.9 soon.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
8.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
2.2% chance of exploitation in 30 days – higher than 82% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.4.9
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 14 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 2026-10-25.

What to do

Upgrade libexpat/libexpat to 2.4.9.

Affected software

ProductAffectedFixed in
GitHublibexpat/libexpatpkg:github/libexpat/libexpatOther threatsAffected
  • <2.4.9
Fixed in
  • 2.4.9

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should immediately identify all systems and applications using libexpat versions prior to 2.4.9. This includes scanning software inventories, dependencies, and embedded devices. The primary mitigation is to upgrade libexpat to version 2.4.9 or later where the vulnerability is fixed. If upgrading is not immediately feasible, organizations should apply virtual patching via web application firewalls or intrusion prevention systems to detect and block suspicious XML payloads that could trigger the vulnerability. Network segmentation and strict input validation on XML data sources can reduce exposure. Monitoring for anomalous application crashes or memory errors related to XML parsing is recommended to detect potential exploitation attempts. Security teams should also review vendor advisories for products bundling libexpat and apply vendor patches promptly. Given the high severity, organizations should prioritize patching in critical environments and consider threat hunting for signs of exploitation. Finally, maintaining up-to-date backups and incident response plans will help mitigate impact if exploitation occurs.

Description

libexpat before 2.4.9 has a use-after-free in the doContent function in xmlparse.c.

References

Community reviews

Loading reviews…