Skip to content
Noroxi
CVE-2022-49043· NVD / CVE Program· CNA mitre

xmlXIncludeAddNode in xinclude.c in libxml2 before 2.11.0 has a use-after-free.

Noroxi assessment

Priority: Monitor (action score 31/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.26% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: xmlsoft libxml2 2.11.0; cbl2 libxml2 2.10.4-5 on CBL Mariner 2.0 2.10.4-5; cbl2 libxml2 2.10.4-6 on CBL Mariner 2.0 2.10.4-5.

Low priority for now. Upgrade to xmlsoft libxml2 2.11.0; cbl2 libxml2 2.10.4-5 on CBL Mariner 2.0 2.10.4-5; cbl2 libxml2 2.10.4-6 on CBL Mariner 2.0 2.10.4-5 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Jan 26, 2025
Updated
Jun 17, 2026
EPSS
0.2% · 17th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
7.8
CNA · mitre
8.1
0.3 point gap

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2022-49043

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for xmlsoft records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
xmlsoftlibxml2

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • xmlsoft libxml2before 2.11.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (mitre). Independent of NVD's CPE analysis and usually ahead of it.

  • xmlsoft libxml2

    • 2.0.0 and later · before 2.11.0affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:8libxml2before 2.9.7-18.el8_10.22.9.7-18.el8_10.2
AlmaLinux:8libxml2-develbefore 2.9.7-18.el8_10.22.9.7-18.el8_10.2
AlmaLinux:8python3-libxml2before 2.9.7-18.el8_10.22.9.7-18.el8_10.2
AlmaLinux:9libxml2before 2.9.13-6.el9_5.12.9.13-6.el9_5.1
AlmaLinux:9libxml2-develbefore 2.9.13-6.el9_5.12.9.13-6.el9_5.1
AlmaLinux:9python3-libxml2before 2.9.13-6.el9_5.12.9.13-6.el9_5.1
Debian:11libxml2before 2.9.10+dfsg-6.7+deb11u62.9.10+dfsg-6.7+deb11u6
Debian:12libxml2before 2.9.14+dfsg-1.3~deb12u22.9.14+dfsg-1.3~deb12u2
Debian:13libxml2before 2.12.7+dfsg+really2.9.14-0.42.12.7+dfsg+really2.9.14-0.4
Red Hat:enterprise_linux:8::appstreamlibxml2-debuginfobefore 0:2.9.7-18.el8_10.20:2.9.7-18.el8_10.2
Red Hat:enterprise_linux:8::appstreamlibxml2-debugsourcebefore 0:2.9.7-18.el8_10.20:2.9.7-18.el8_10.2
Red Hat:enterprise_linux:8::appstreamlibxml2-develbefore 0:2.9.7-18.el8_10.20:2.9.7-18.el8_10.2
Red Hat:enterprise_linux:8::appstreampython3-libxml2-debuginfobefore 0:2.9.7-18.el8_10.20:2.9.7-18.el8_10.2
Red Hat:enterprise_linux:8::baseoslibxml2before 0:2.9.7-18.el8_10.20:2.9.7-18.el8_10.2
Red Hat:enterprise_linux:8::baseospython3-libxml2before 0:2.9.7-18.el8_10.20:2.9.7-18.el8_10.2
Red Hat:enterprise_linux:9::appstreamlibxml2-debuginfobefore 0:2.9.13-6.el9_5.10:2.9.13-6.el9_5.1
Red Hat:enterprise_linux:9::appstreamlibxml2-debugsourcebefore 0:2.9.13-6.el9_5.10:2.9.13-6.el9_5.1
Red Hat:enterprise_linux:9::appstreamlibxml2-develbefore 0:2.9.13-6.el9_5.10:2.9.13-6.el9_5.1
Red Hat:enterprise_linux:9::appstreampython3-libxml2-debuginfobefore 0:2.9.13-6.el9_5.10:2.9.13-6.el9_5.1
Red Hat:enterprise_linux:9::baseoslibxml2before 0:2.9.13-6.el9_5.10:2.9.13-6.el9_5.1
Red Hat:enterprise_linux:9::baseospython3-libxml2before 0:2.9.13-6.el9_5.10:2.9.13-6.el9_5.1
Red Hat:rhel_eus:8.8::appstreamlibxml2-debuginfobefore 0:2.9.7-16.el8_8.70:2.9.7-16.el8_8.7
Red Hat:rhel_eus:8.8::appstreamlibxml2-debugsourcebefore 0:2.9.7-16.el8_8.70:2.9.7-16.el8_8.7
Red Hat:rhel_eus:8.8::appstreamlibxml2-develbefore 0:2.9.7-16.el8_8.70:2.9.7-16.el8_8.7

+28

Same product

xmlsoft: all records

Other highest-scoring records for the same primary product.

  • CVE-2008-3529Heap-based buffer overflow in the xmlParseAttValueComplex function in parser.c in libxml2 before 2.7.0 allows context-dependent attackers to
    47Plan
  • CVE-2017-7376Buffer overflow in libxml2 allows remote attackers to execute arbitrary code by leveraging an incorrect limit for port values when handling
    46Plan
  • CVE-2022-40303An issue was discovered in libxml2 before 2.10.3.
    42Plan

Published before and after this one in the same product

  • ← EarlierCVE-2024-34459May 14, 2024 · An issue was discovered in xmllint (from libxml2) before 2.11.8 and 2.12.x before 2.12.7.
    31Monitor
  • ← EarlierCVE-2024-40896Dec 23, 2024 · In libxml2 2.11 before 2.11.9, 2.12 before 2.12.9, and 2.13 before 2.13.3, the SAX parser can produce events for external entities even if c
    36Monitor
  • Later →CVE-2024-56171Feb 18, 2025 · libxml2 before 2.12.10 and 2.13.x before 2.13.6 has a use-after-free in xmlSchemaIDCFillNodeTables and xmlSchemaBubbleIDCNodeTables in xmlsc
    39Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
xmlsoft libxml22.11.0Vendor (CNA)
cbl2 libxml2 2.10.4-5 on CBL Mariner 2.02.10.4-5 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 libxml2 2.10.4-6 on CBL Mariner 2.02.10.4-5 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 libxml2 2.10.4-6 on CBL-Mariner 2.02.10.4-5 · CBL-Mariner ReleasesMicrosoft (MSRC)
almalinux:libxml22.9.13-6.el9_5.1 · AlmaLinux:9Package registry (OSV)
almalinux:libxml2-devel2.9.13-6.el9_5.1 · AlmaLinux:9Package registry (OSV)
almalinux:python3-libxml22.9.13-6.el9_5.1 · AlmaLinux:9Package registry (OSV)
debian:libxml22.9.14+dfsg-1.3~deb12u2 · Debian:12Package registry (OSV)
opensuse:libxml22.10.3-150500.5.20.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:libxml2-python2.10.3-150500.5.20.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:python-libxml2-python2.9.7-150000.3.73.1 · openSUSE:Leap 15.6Package registry (OSV)
red hat:libxml20:2.9.13-6.el9_5.1 · Red Hat:enterprise_linux:9::baseosPackage registry (OSV)
red hat:libxml2-debuginfo0:2.9.13-6.el9_5.1 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:libxml2-debugsource0:2.9.13-6.el9_5.1 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:libxml2-devel0:2.9.13-6.el9_5.1 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:python3-libxml20:2.9.13-6.el9_5.1 · Red Hat:enterprise_linux:9::baseosPackage registry (OSV)
red hat:python3-libxml2-debuginfo0:2.9.13-6.el9_5.1 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
rocky linux:libxml20:2.9.7-18.el8_10.2 · Rocky Linux:8Package registry (OSV)
suse:libxml22.9.4-46.78.1 · SUSE:Linux Enterprise Server 12 SP5-LTSSPackage registry (OSV)
suse:libxml22.9.7-150000.3.73.1 · SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSSPackage registry (OSV)
suse:libxml2-python2.10.3-150500.5.20.1 · SUSE:Linux Enterprise Micro 5.5Package registry (OSV)
suse:libxml2-python2.9.14-150400.5.35.1 · SUSE:Linux Enterprise Micro 5.3Package registry (OSV)
suse:python-libxml22.9.4-46.78.1 · SUSE:Linux Enterprise Server 12 SP5-LTSSPackage registry (OSV)
suse:python-libxml2-python2.9.7-150000.3.73.1 · SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSSPackage registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2024-5617123 days apartlibxml2 before 2.12.10 and 2.13.x before 2.13.6 has a use-after-free in xmlSchemaIDCFillNodeTables and xmlSchemaBubbleIDCNodeTables in xmlsc
    39Monitor
  • CVE-2024-25062357 days apartAn issue was discovered in libxml2 before 2.11.7 and 2.12.x before 2.12.5.
    30Monitor
  • CVE-2026-6653512 days apartlibxml2: Use after free in xmlParseInternalSubset via improper entity resolution handling
    28Monitor
  • CVE-2023-45322478 days apartlibxml2 through 2.11.5 has a use-after-free that can only occur after a certain memory allocation fails.
    26Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

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

nvd-primary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

c
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);

Fixed

c
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (2 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records