# CVE-2016-0718: Memory corruption in n/a > Attackers can cause crashes or execute arbitrary code via malformed XML input due to a buffer overflow in the Expat library. - **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 26 May 2016 - **Updated:** 8 Oct 2026 - **Also known as:** ALPINE-CVE-2016-0718, CVE-2016-0719, DEBIAN-CVE-2016-0718, GHSA-3f8j-8ww3-q7v6, MGASA-2016-0193, PSF-2016-2, RHSA-2016:2824, UBUNTU-CVE-2016-0718, USN-2983-1 ## What is CVE-2016-0718? CVE-2016-0718 is a critical memory corruption vulnerability in Apple Mac Os X, published on 26 May 2016. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description Expat allows context-dependent attackers to cause a denial of service (crash) or possibly execute arbitrary code via a malformed input document, which triggers a buffer overflow. Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer) ## Which versions are affected by CVE-2016-0718? It affects 14 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `expat` | Red Hat:enterprise_linux:6::client | All versions | 0:2.0.1-13.el6_8 | | `expat-debuginfo` | Red Hat:enterprise_linux:6::client | All versions | 0:2.0.1-13.el6_8 | | `expat-devel` | Red Hat:enterprise_linux:6::client | All versions | 0:2.0.1-13.el6_8 | | `expat` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.0.1-13.el6_8 | | `expat-debuginfo` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.0.1-13.el6_8 | | `expat-devel` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.0.1-13.el6_8 | | `expat` | Red Hat:enterprise_linux:6::server | All versions | 0:2.0.1-13.el6_8 | | `expat-debuginfo` | Red Hat:enterprise_linux:6::server | All versions | 0:2.0.1-13.el6_8 | | `expat-devel` | Red Hat:enterprise_linux:6::server | All versions | 0:2.0.1-13.el6_8 | | `expat` | Red Hat:enterprise_linux:6::workstation | All versions | 0:2.0.1-13.el6_8 | | `expat-debuginfo` | Red Hat:enterprise_linux:6::workstation | All versions | 0:2.0.1-13.el6_8 | | `expat-devel` | Red Hat:enterprise_linux:6::workstation | All versions | 0:2.0.1-13.el6_8 | | `expat` | Red Hat:enterprise_linux:7::client | All versions | 0:2.1.0-10.el7_3 | | `expat-debuginfo` | Red Hat:enterprise_linux:7::client | All versions | 0:2.1.0-10.el7_3 | | `expat-devel` | Red Hat:enterprise_linux:7::client | All versions | 0:2.1.0-10.el7_3 | | `expat-static` | Red Hat:enterprise_linux:7::client | All versions | 0:2.1.0-10.el7_3 | | `expat` | Red Hat:enterprise_linux:7::computenode | All versions | 0:2.1.0-10.el7_3 | | `expat-debuginfo` | Red Hat:enterprise_linux:7::computenode | All versions | 0:2.1.0-10.el7_3 | | `expat-devel` | Red Hat:enterprise_linux:7::computenode | All versions | 0:2.1.0-10.el7_3 | | `expat-static` | Red Hat:enterprise_linux:7::computenode | All versions | 0:2.1.0-10.el7_3 | | `expat` | Red Hat:enterprise_linux:7::server | All versions | 0:2.1.0-10.el7_3 | | `expat-debuginfo` | Red Hat:enterprise_linux:7::server | All versions | 0:2.1.0-10.el7_3 | | `expat-devel` | Red Hat:enterprise_linux:7::server | All versions | 0:2.1.0-10.el7_3 | | `expat-static` | Red Hat:enterprise_linux:7::server | All versions | 0:2.1.0-10.el7_3 | | `expat` | Red Hat:enterprise_linux:7::workstation | All versions | 0:2.1.0-10.el7_3 | | `expat-debuginfo` | Red Hat:enterprise_linux:7::workstation | All versions | 0:2.1.0-10.el7_3 | | `expat-devel` | Red Hat:enterprise_linux:7::workstation | All versions | 0:2.1.0-10.el7_3 | | `expat-static` | Red Hat:enterprise_linux:7::workstation | All versions | 0:2.1.0-10.el7_3 | Products: Apple Mac Os X, Canonical Ubuntu Linux, Debian Debian Linux, Libexpat Project Libexpat, Mcafee Policy Auditor, Mozilla Firefox, Opensuse Leap, Opensuse Opensuse, Python Python, Suse Linux Enterprise Debuginfo, Suse Linux Enterprise Desktop, Suse Linux Enterprise Server, Suse Linux Enterprise Software Development Kit, Suse Studio Onsite. ## How do I fix CVE-2016-0718? Upgrade to a fixed version. ## Is CVE-2016-0718 being exploited? There is no known exploitation of CVE-2016-0718 in the wild and no public exploit code. ## Other vulnerabilities in Apple Mac Os X - [CVE-2014-7169](https://insights.sbomify.com/CVE-2014-7169/): GNU Bourne-Again Shell (Bash) Arbitrary Code Execution (critical 9.8, exploited in the wild) - [CVE-2014-6271](https://insights.sbomify.com/CVE-2014-6271/): GNU Bourne-Again Shell (Bash) Arbitrary Code Execution (critical 9.8, exploited in the wild) - [CVE-2012-1823](https://insights.sbomify.com/CVE-2012-1823/): PHP-CGI Query String Parameter (critical 9.8, exploited in the wild) - [CVE-2021-30713](https://insights.sbomify.com/CVE-2021-30713/): Apple macOS Unspecified (high 7.8, exploited in the wild) - [CVE-2019-8526](https://insights.sbomify.com/CVE-2019-8526/): Apple macOS Use-After-Free (high 7.8, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2016-0718 and fix it if it is affected. What it is: CVE-2016-0718 is a critical memory corruption vulnerability in Apple Mac Os X, published on 26 May 2016. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2016-0718 in the wild and no public exploit code. Affected product: Apple Mac Os X. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2016-0718/ (Markdown: https://insights.sbomify.com/CVE-2016-0718/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2016-0718 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2016-0718 - OSV: https://osv.dev/vulnerability/CVE-2016-0718 --- From sbomify Insights: https://insights.sbomify.com/CVE-2016-0718/ Summaries are generated and may contain mistakes; the official description above is the record.