Breaking News: Thousands Of GitHub Accounts Hijacked With wfx-loot CI Secret
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2016-3709

libxml2: Incorrect server side include parsing can lead to XSS

Overview

Published
28 Jul 2022
Modified
14 Oct 2026
Medium CVE
1 Registry packages
14 OS packages
14 Linux distributions
Yes Fix available

Description

Possible cross-site scripting vulnerability in libxml after commit 960f0e2.

Source: OX vulnerability database

Severity

6.1 · MEDIUM

CVSS 3.1 base score, scored by NVD.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

Weakness: CWE-79

Affected packages · 1

Packages affected by CVE-2016-3709
EcosystemPackageVulnerableFixed in
Julia XML2_jll <2.9.12+0 2.9.12+0

Open a package to see all its vulnerabilities.

Operating systems · 33 fixes

Oracle Linux 1 release · 1 package

fixed 1
libxml2
Oracle Linux fixes for CVE-2016-3709
ReleasePackageFixed in
8 libxml2 +2 2.9.7-15.el8

Photon OS 1 release · 1 package

fixed 1
libxml2
Photon OS fixes for CVE-2016-3709
ReleasePackageFixed in
5.0 libxml2 +2 2.15.3-1.ph5

Red Hat 2 releases · 1 package

eol 1 fixed 2
libxml2
Red Hat fixes for CVE-2016-3709
ReleasePackageFixed inAdvisory
7 libxml2 +3 eol —
8 libxml2 +2 0:2.9.7-13.el8_6.2 RHSA-2023:4767
8 libxml2 +2 0:2.9.7-15.el8 RHSA-2022:7715

SUSE Linux Enterprise 1 release · 2 packages

fixed 2
libxml2-2 python-libxml2
SUSE Linux Enterprise fixes for CVE-2016-3709
ReleasePackageFixed inAdvisory
12.5 libxml2-2 +4 2.9.4-46.59.2 SUSE-SU-2022:3717-1
12.5 python-libxml2 2.9.4-46.59.3 SUSE-SU-2022:3717-1

SUSE Linux Enterprise Micro 2 releases · 1 package

fixed 2
libxml2-2
SUSE Linux Enterprise Micro fixes for CVE-2016-3709
ReleasePackageFixed inAdvisory
5.1 libxml2-2 +1 2.9.7-150000.3.51.1 SUSE-SU-2022:3871-1
5.2 libxml2-2 +2 2.9.7-150000.3.51.1 SUSE-SU-2022:3871-1

alma 1 release · 1 package

fixed 1
libxml2
alma fixes for CVE-2016-3709
ReleasePackageFixed in
8 libxml2 +2 2.9.7-15.el8

alpine 4 releases · 1 package

fixed 4
libxml2
alpine fixes for CVE-2016-3709
ReleasePackageFixed in
3.22 libxml2 2.9.11-r0
3.23 libxml2 2.9.11-r0
3.24 libxml2 2.9.11-r0
edge libxml2 2.9.11-r0

debian 5 releases · 1 package

affected 1 fixed 4
libxml2
debian fixes for CVE-2016-3709
ReleasePackageFixed in
10 libxml2 affected
11 libxml2 2.9.10+dfsg-6.7+deb11u5
12 libxml2 2.9.12+dfsg-3
13 libxml2 2.9.12+dfsg-3
14 libxml2 2.9.12+dfsg-3

echo 1 release · 2 packages

fixed 2
libxml2-2-9-1 libxml2
echo fixes for CVE-2016-3709
ReleasePackageFixed in
libxml2-2-9-1 2.9.1+e1
libxml2 2.9.12+dfsg-3

openSUSE Leap Micro 1 release · 1 package

fixed 1
libxml2-2
openSUSE Leap Micro fixes for CVE-2016-3709
ReleasePackageFixed inAdvisory
5.2 libxml2-2 +2 2.9.7-150000.3.51.1 SUSE-SU-2022:3871-1

rocky 1 release · 1 package

fixed 1
libxml2
rocky fixes for CVE-2016-3709
ReleasePackageFixed in
8 libxml2 +2 2.9.7-15.el8

root.io debian 3 releases · 1 package

fixed 3
rootio-libxml2
root.io debian fixes for CVE-2016-3709
ReleasePackageFixed in
11 rootio-libxml2 2.9.10+dfsg-6.7+deb11u5
12 rootio-libxml2 2.9.12+dfsg-3
13 rootio-libxml2 2.9.12+dfsg-3

seal Red Hat 3 releases · 1 package

fixed 3
libxml2
seal Red Hat fixes for CVE-2016-3709
ReleasePackageFixed in
7 libxml2 +1 2.9.1-6.el7_9.6+sp999
8 libxml2 +1 2.9.7-18.el8_10.1+sp999
9 libxml2 +1 2.9.13-6.el9_4+sp999

ubuntu 4 releases · 1 package

fixed 4
libxml2
ubuntu fixes for CVE-2016-3709
ReleasePackageFixed in
18.04 libxml2 2.9.4+dfsg1-6.1ubuntu1.7
18.04-ESM libxml2 2.9.4+dfsg1-6.1ubuntu1.7
20.04 libxml2 2.9.10+dfsg-5ubuntu0.20.04.4
20.04-ESM libxml2 2.9.10+dfsg-5ubuntu0.20.04.4

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.