CVE-2016-4570

The mxmlDelete function in mxml-node.c in mxml 2.9, 2.7, and possibly earlier allows remote attackers to cause a denial of service (stack consumption) via crafted xml file.

Published: 2017-02-03 Last update: 2026-05-13 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2016-4570 is rated Moderate Risk (41.1/100): CVSS Medium severity, with medium exploitation likelihood (EPSS 0.33%). Mandatory action: Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2016-4570

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-03-03 0.81% 0.33% -0.48%
2 2025-03-30 0.90% 0.81% -0.09%
3 2025-03-29 0.90%

Full EPSS history (7 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2016-4570

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.5 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
1.8 3.6 [email protected]
7.1 2.0 HIGH
AV:N/AC:M/Au:N/C:N/I:N/A:C Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:M)
Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:N)
No confidentiality impact.
Integrity impact (I:N)
No integrity impact.
Availability impact (A:C)
Complete availability impact.
8.6 6.9 [email protected]

Weakness enumeration for CVE-2016-4570

OS Trackers for CVE-2016-4570

vendor priority summary link
debian not yet assigned CVE-2016-4570 not yet assigned priority: Debian including 1 source packages (mxml), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2016-4570
suse low CVE-2016-4570 severity low: SUSE including 6 source package names (libmxml1-2.10-1.1, libmxml1-2.5-24.3.1, libmxml1-32bit-2.10-1.1, mxml-2.10-1.1, mxml-2.5-24.3.1, mxml-devel-2.10-1.1), 6 product×package rows across 2 product lines (SUSE Linux Enterprise Software Development Kit 11 SP4, openSUSE Tumbleweed): Fixed 6. https://www.suse.com/security/cve/CVE-2016-4570/
ubuntu medium CVE-2016-4570 medium priority: Ubuntu including 1 source packages (mxml), 24 status rows across 24 suites (artful, bionic, cosmic, disco, eoan, focal, groovy, hirsute, impish, jammy, kinetic, lunar, mantic, noble, oracular, plucky, precise, questing, trusty, upstream, wily, xenial, yakkety, zesty): not-affected 16, ignored 5, DNE 1, needed 1, needs-triage 1. https://ubuntu.com/security/CVE-2016-4570

Affected software / configurations for CVE-2016-4570

Vendor Product Version Raw CPE
mini-xml_project mini-xml <= 2.7 cpe:2.3:a:mini-xml_project:mini-xml:*:*:*:*:*:*:*:*
mini-xml_project mini-xml 2.9 cpe:2.3:a:mini-xml_project:mini-xml:2.9:*:*:*:*:*:*:*
debian debian_linux 8.0 cpe:2.3:o:debian:debian_linux:8.0:*:*:*:*:*:*:*

References for CVE-2016-4570

cvelogic Threat Intelligence