CVE Intelligence
Medium Memory corruption exploit reference

CVE-2016-1839 — The xmlDictAddString function in libxml2 before 2.9.4, as used in Apple iOS before 9.3.2, OS X...

The xmlDictAddString function in libxml2 before 2.9.4, as used in Apple iOS before 9.3.2, OS X before 10.11.5, tvOS before 9.2.1, and watchOS before 2.2.1, allows remote attackers to cause a denial of service (heap-based buffer over-read) via a crafted XML document.

Published May 20, 2016 · Updated Oct 14, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: apple

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

How the score was calculated
  • Public exploit/PoC (exploitdb)+8
  • EPSS 7.3% (30-day exploitation probability)+14
  • Technical severity (medium)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
7.35%
ahead of 94% of scored CVEs · Oct 14, 2026
Affects
Apple
Iphone Os and 13 more
CVSS base
5.5
Medium · 2 source(s)

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

  • Documented patch — git.gnome.org (NIST National Vulnerability Database)
  • Documented patch — kc.mcafee.com (NIST National Vulnerability Database)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Apple Iphone Os, Apple Mac Os X, Apple Tvos…).
  2. Apply the fixed version or the patch documented under Remediation.
  3. Exploitation requires user interaction: tighten email/web filtering and warn affected users.
  4. EPSS ahead of 94% of scored CVEs: prioritize it in the patch queue.
  5. Search available logs for exploit probes matching the vulnerability class (memory corruption), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Apple Iphone Os < 9.3.2 Vulnerable NIST National Vulnerability Database
Apple Mac Os X < 10.11.5 Vulnerable NIST National Vulnerability Database
Apple Tvos < 9.2.1 Vulnerable NIST National Vulnerability Database
Apple Watchos < 2.2.1 Vulnerable NIST National Vulnerability Database
Canonical Ubuntu Linux version 12.04version 14.04version 15.10version 16.04 Vulnerable NIST National Vulnerability Database
Debian Debian Linux version 8.0 Vulnerable NIST National Vulnerability Database
Mcafee Web Gateway ≥ 7.6.0.0 and ≤ 7.6.2.3≥ 7.5.0.0 and ≤ 7.5.2.10 Vulnerable NIST National Vulnerability Database
Red Hat Enterprise Linux Desktop version 6.0version 7.0 Vulnerable NIST National Vulnerability Database
Red Hat Enterprise Linux Server version 7.0version 6.0 Vulnerable NIST National Vulnerability Database
Red Hat Enterprise Linux Server Aus version 7.2version 7.6version 7.4version 7.3 Vulnerable NIST National Vulnerability Database
Red Hat Enterprise Linux Server Eus version 7.2version 7.3version 7.4version 7.5version 7.6 Vulnerable NIST National Vulnerability Database
Red Hat Enterprise Linux Server Tus version 7.2version 7.3version 7.6 Vulnerable NIST National Vulnerability Database
Red Hat Enterprise Linux Workstation version 6.0version 7.0 Vulnerable NIST National Vulnerability Database
Xmlsoft Libxml2 < 2.9.4 Vulnerable NIST National Vulnerability Database

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Local
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
5.5 CVSS 3.0 Medium 1.8 3.6 nvd@nist.gov via NIST National Vulnerability Database
5.5 CVSS 3.0 Medium — — GitHub, Inc. via GitHub Security Advisories
4.3 CVSS 2.0 Medium 8.6 2.9 nvd@nist.gov via NIST National Vulnerability Database
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H (score shown at the top: nvd@nist.gov)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-125 · Out-of-bounds Read

Other CVEs with this weakness →

Public exploits, PoCs and detection templates

Public code that demonstrates or tests the flaw raises the odds of mass exploitation — and Nuclei templates help find vulnerable assets in your environment.

Exploit-DB

Warning: public PoCs are sometimes disguised malware. Use them only for authorized testing in an isolated environment. This portal does not host exploit code — it only points to the sources.

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 7.35%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
  • Correlate service crashes/restarts with inbound traffic; repeated crashes may indicate attempts.
endpoint telemetry (EDR)crash dumps

Timeline

What happened to this CVE, newest first.

  • 2026
  • Record published
    Oct 14, 2026
  • Fix documented
    Oct 14, 2026 · NIST National Vulnerability Database
  • Affected products added · apple/iphone os, apple/mac os x, apple/tvos, apple/watchos, canonical/ubuntu linux, debian/debian linux, redhat/enterpri
    Oct 14, 2026 · NIST National Vulnerability Database
  • CVSS changed · 5.5
    Oct 14, 2026 · NIST National Vulnerability Database
  • Source status changed · → Modified
    Oct 14, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 14, 2026 · Alertas do Telegram
  • 2016
  • CVE published
    May 20, 2016 · apple

Source activity

Repeated readings are counted rather than listed.

  • 2× References added · Oct 14, 2026 – Oct 14, 2026
  • 1× Official description updated · Oct 14, 2026 – Oct 14, 2026

References

26 on the record

Elsewhere on this site

Apple
every CVE for this vendor
CWE-125
other pages naming this weakness

Related CVEs (same products)

  • High CVE-2026-86950 Apple Multiple Products Out-of-Bounds Write Vulnerability KEV 17d
  • Medium CVE-2026-86924 Improper Input Validation in Apple Ipados Sep 14, 2026
  • High CVE-2026-86904 A privacy issue was addressed with improved state management. This issue is fixed in iOS… Sep 14, 2026
  • Medium CVE-2026-86905 Improper Access Control in Apple Ipados Sep 14, 2026
  • Medium CVE-2026-86903 Out-of-bounds Read in Apple Ipados Sep 14, 2026
  • High CVE-2026-86895 Exposure of Sensitive Information in Apple Ipados Sep 14, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No CISA SSVC assessment.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2016-1839 is "The xmlDictAddString function in libxml2 before 2.9.4, as used in Apple iOS before 9.3.2, OS X...", rated Medium. It affects Iphone Os (Apple); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 5.5 describes technical severity. EPSS 7.35% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.