Skip to main content
No exploitation reportedFix available

CVE-2009-2416

No exploitation reported by the sources we read.

  • Published2009-08-11
  • WeaknessCWE-416

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

Multiple use-after-free vulnerabilities in libxml2 2.5.10, 2.6.16, 2.6.26, 2.6.27, and 2.6.32, and libxml 1.8.17, allow context-dependent attackers to cause a denial of service (application crash) via crafted (1) Notation or (2) Enumeration attribute types in an XML file, as demonstrated by the Codenomicon XML fuzzing framework.

Timeline

dates in UTC
  1. 2009-08-1118:30CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-10-23 21:37 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2009-2416?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2009-2416?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD
Xmlsoft libxml2
BranchAffectedFixed in
2.5= 2.5.10no fix published
2.6= 2.6.16no fix published
2.6= 2.6.26no fix published
2.6= 2.6.27no fix published
2.6= 2.6.32no fix published
Canonical ubuntu linux
BranchAffectedFixed in
6.6= 6.06no fix published
8.4= 8.04no fix published
8.10= 8.10no fix published
9.4= 9.04no fix published
Apple mac os x
BranchAffectedFixed in
10.6≥ 10.6.0, < 10.6.210.6.2
10.5≥ 10.5.0, < 10.5.810.5.8
10.4< 10.4.1110.4.11

16 more products in the sources.

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Vendor advisories

  • CVE-2009-2416 Red Hat Product Security381 products fixed

    mingw32-libxml2: Pointer use-after-free flaws by parsing Notation and Enumeration attribute types

  • RHSA-2009:1206 Red Hat Product Security211 products fixed

    Red Hat Security Advisory: libxml and libxml2 security update

Full record on NVD

Fix

  1. Vendor fix Red Hat Product Security RHSA-2009:1206 · 211 productsBefore applying this update, make sure that all previously-released errata relevant to your system have been applied. This update is available via Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at http://kbase.redhat.com/faq/docs/DOC-11259

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
none listed
PoC-in-GitHub

Sources

  • CISA-ADPSSVC decisionnone2024-02-06
  • OpenCVESSVC decisionnone—
  • CISA-ADPCVSS 3.16.52025-01-21
  • NVDCVSS 3.16.5read 2026-10-23
  • NVDCVSS 2.04.3read 2026-10-23
  • CISA-ADPweakness (CWE)CWE-4162025-01-21
  • NVDweakness (CWE)CWE-416read 2026-10-23
  • FIRST EPSSEPSS score2.0 %2026-10-23

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
Published
2009-08-11
Last Modified
2026-04-23
NVD status
Modified

Frequently asked questions

What is CVE-2009-2416?

Multiple use-after-free vulnerabilities in libxml2 2.5.10, 2.6.16, 2.6.26, 2.6.27, and 2.6.32, and libxml 1.8.17, allow context-dependent attackers to cause a denial of service (application crash) via crafted (1) Notation or (2) Enumeration attribute types in an XML file, as demonstrated by the Codenomicon XML fuzzing framework.

Is CVE-2009-2416 actively exploited?

Active exploitation of CVE-2009-2416 has not been confirmed. Its EPSS score was 2.0% on 2026-10-23, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2009-2416?

CVE-2009-2416 has a CVSS v3 base score of 6.5 (MEDIUM severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H.

Running mingw32-libxml2? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month