Evidence used
- No CISA KEV confirmation is currently recorded.
- A structured source references public exploit or proof-of-concept material.
- EPSS is 4.62% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2016
CVE-2016-1834High confidence
Affected product: Heap-based Buffer Overflow
Unknown · Unknown
7.8HighCVSS 3.1
Within 7 days
Patch availableHigh technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityHigh→Operational priority:High, unchanged from published severity.unchanged
Compensating controls
- Validate the affected product branch and deploy the verified fixed release.
- Restrict local access and enforce least privilege on affected hosts.
- Increase monitoring for the attack path and post-exploitation behaviour described in the report.
Verification
- Confirm that the asset runs Unknown Unknown and falls inside the recorded affected range.
- Verify the installed build against the product-specific fixed version after deployment.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Distribution package intelligence
4 package statesRelease-specific package status
Debian findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.
Repository candidate not checked
A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.
| Distribution release | Source package | Vendor state | Fixed version | Evidence |
|---|---|---|---|---|
| Debian trixietrixie · source | libxml2 | Vendor fix publishedDebian records a fixed source-package version for this release. | 2.9.3+dfsg1-1.1 | Debian Security Tracker ↗Source updated 22 Oct 2026 |
| Debian bookwormbookworm · source | libxml2 | Vendor fix publishedDebian records a fixed source-package version for this release. | 2.9.3+dfsg1-1.1 | Debian Security Tracker ↗Source updated 22 Oct 2026 |
| Debian forkyforky · source | libxml2 | Vendor fix publishedDebian records a fixed source-package version for this release. | 2.9.3+dfsg1-1.1 | Debian Security Tracker ↗Source updated 22 Oct 2026 |
| Debian sidsid · source | libxml2 | Vendor fix publishedDebian records a fixed source-package version for this release. | 2.9.3+dfsg1-1.1 | Debian Security Tracker ↗Source updated 22 Oct 2026 |
Direct vendor intelligence
1 current · 1 archivedAuthoritative vendor CSAF and VEX advisories
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
CVE-2016-1834 · CSAF 2.0 · revision 26 · interimSUSE Product Security TeamCVE-2016-1834
The vendor explicitly identifies these products as affected by this CVE.
- libxml2 as component of SUSE Linux Enterprise Server 11 SP4 LTSS
- Summary
- Heap-based buffer overflow in the xmlStrncat 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 execute arbitrary code or cause a denial of service (memory corruption) via a crafted XML document.
- Remediation
- To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2016-1834 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitylibxml2: Heap-buffer-overflow in xmlStrncatNo longer in the provider’s current catalogue
The vendor explicitly identifies these products as affected by this CVE.
- libxml2.src as a component of Red Hat Enterprise Linux 5
- libxml2.src as a component of Red Hat JBoss Enterprise Web Server 3
- Summary
- Heap-based buffer overflow in the xmlStrncat 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 execute arbitrary code or cause a denial of service (memory corruption) via a crafted XML document.
- Remediation
- For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all applications linked to the libxml2 library must be restarted, or the system rebooted.
High technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance.
Patch available01
What, why and how
Heap-based buffer overflow in the xmlStrncat 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 execute arbitrary code or cause a denial of service (memory corruption) via a crafted XML document.
What
Heap-based buffer overflow in the xmlStrncat 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 execute arbitrary code or cause a denial of service (memory corruption) via a crafted XML document.
Why
A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().
How
An attacker operating through local access may attempt exploitation without authentication after a user interaction. If successful, the issue may execute code or commands in the affected security context.
What
Heap-based buffer overflow in the xmlStrncat 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 execute arbitrary code or cause a denial of service (memory corruption) via a crafted XML document.
Why
A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().
How
An attacker operating through local access may attempt exploitation without authentication after a user interaction. If successful, the issue may execute code or commands in the affected security context.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material Reference recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.A structured CVE source labels at least one public reference as exploit material. BlackTree has not independently validated that it is safe, reliable or weaponised.
- Likely attack path
- local access → Heap-based Buffer Overflow → execute code or commands in the affected security context
- Attack surface
- Local
- Privileges required
- None: unauthenticated exploitation is possible
- User interaction
- Required interaction required
- Attack complexity
- Low: no specialised conditions are recorded
- Security boundary
- Unchanged: impact remains within the vulnerable component's security authority
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-122 ↗
CWE-122: Heap-based Buffer Overflow. A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UIRequiredUser interaction: Another user must perform an action for exploitation to succeed.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.- Post-exploitation / living off the land
- After compromise, an attacker may use built-in shells, scripting engines, scheduled tasks and native network utilities for discovery, persistence or movement. This is a plausible LoTL path, not evidence that it has occurred for every attack.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Patch available
- Action
- To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
- Workaround
- No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
Official vendor articles4 stored documents
Linked articles are downloaded and versioned as source evidence. A CVE mention or approved update relationship does not, by itself, verify a fix for every product branch.
- About the security content of tvOS 9.2.1 - Apple Support →Original publisher ↗Searchable text snapshot · Captured 17 Oct 2026Apple Store Mac iPad iPhone Watch Vision AirPods Home Entertainment Accessories Support 0 + "},{"name":"compact","assetInline":" "}],"analyticsAttributes":[{"name":"data-analytics-title","value":"apple home"}]},{"id":"ad4a2a26eb4836393385e9f6c61b526b4a3cb31409c5ed8730ce7a704dd7132f","name":"store","text":"
- About the security content of watchOS 2.2.1 - Apple Support →Original publisher ↗Searchable text snapshot · Captured 17 Oct 2026Apple Store Mac iPad iPhone Watch Vision AirPods Home Entertainment Accessories Support 0 + "},{"name":"compact","assetInline":" "}],"analyticsAttributes":[{"name":"data-analytics-title","value":"apple home"}]},{"id":"ad4a2a26eb4836393385e9f6c61b526b4a3cb31409c5ed8730ce7a704dd7132f","name":"store","text":"
- About the security content of OS X El Capitan v10.11.5 and Security Update 2016-003 - Apple Support →Original publisher ↗Searchable text snapshot · Captured 17 Oct 2026Apple Store Mac iPad iPhone Watch Vision AirPods Home Entertainment Accessories Support 0 + "},{"name":"compact","assetInline":" "}],"analyticsAttributes":[{"name":"data-analytics-title","value":"apple home"}]},{"id":"ad4a2a26eb4836393385e9f6c61b526b4a3cb31409c5ed8730ce7a704dd7132f","name":"store","text":"
- About the security content of iOS 9.3.2 - Apple Support →Original publisher ↗Searchable text snapshot · Captured 17 Oct 2026Apple Store Mac iPad iPhone Watch Vision AirPods Home Entertainment Accessories Support 0 + "},{"name":"compact","assetInline":" "}],"analyticsAttributes":[{"name":"data-analytics-title","value":"apple home"}]},{"id":"ad4a2a26eb4836393385e9f6c61b526b4a3cb31409c5ed8730ce7a704dd7132f","name":"store","text":"
04
Evidence and provenance
Published 20 May 2016 · Last source change 4 Dec 2025, 17:15 UTC · CWE-122 · Heap-based Buffer Overflow
CVE recordCVE.org · 5.2
CVSS sourceCISA ADP
EPSS source FIRST · tracked since 2026-09-01
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2016-2929
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceCISA ADP
NVD statusNVD modified after enrichment
Missing structured fields: affected product. Missing data is not evidence of low risk; review the primary advisory.
Material change intelligence
View recent updates ↗What changed after publication
- Vendor guidanceAuthoritative vendor guidance changed from remediation: access.redhat.com/CVE-2016-1834 to advisory no longer present in the provider's current catalogue.Red Hat Product Security ↗
- Before
- remediation: access.redhat.com/CVE-2016-1834
- After
- advisory no longer present in the provider's current catalogue
- Affected versionsThe structured affected or fixed version information changed.Red Hat Product Security ↗
- Before
- n/a · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
- After
- n/a · Fixed: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all applications linked to the libxml2 library must be restarted, or the system rebooted.
- ENISA EUVD mappingEUVD-2016-2929 was added to the official ENISA EUVD mapping for this CVE.ENISA EUVD ↗
- Before
- not recorded
- After
- {"euvdId":"EUVD-2016-2929"}
- Vendor guidanceAuthoritative vendor guidance changed: added patch: git.gnome.org/commit?id=8fbbf5513d609c1770b391b99e33314cd0742704; added patch: kc.mcafee.com/index?page=content&id=SB10170; removed vendor advisory: access.redhat.com/RHSA-2016:1292; removed vendor advisory: debian.org/dsa-3593; 6 further additions; 2 further removals.git.gnome.org ↗
- Before
- vendor advisory: access.redhat.com/RHSA-2016:1292 · vendor advisory: debian.org/dsa-3593 · vendor advisory: lists.apple.com/msg00001.html · 5 more references
- After
- patch: git.gnome.org/commit?id=8fbbf5513d609c1770b391b99e33314cd0742704 · patch: kc.mcafee.com/index?page=content&id=SB10170 · remediation: git.gnome.org/commit?id=8fbbf5513d609c1770b391b99e33314cd0742704 · 9 more references
- Affected versionsThe structured affected or fixed version information changed.CNA ↗
- Before
- n/a · Fixed: No fixed version is explicitly recorded in the structured CVE data.
- After
- n/a · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
- Remediation statusRemediation status changed from Awaiting fix to Patch available.git.gnome.org ↗
- Before
- Awaiting fix
- After
- Patch available
- Public exploit evidencePublic exploit evidence changed from No public exploit to Public exploit reference.bugzilla.gnome.org ↗
- Before
- No public exploit
- After
- Public exploit reference
- Catalogue recordCVE added to the BlackTree catalogue.CNA ↗
CVE published
Fixed release or patch reference recorded
Fixed release recorded from official guidance
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.