CVE-2016-1683

What it is

numbers.c in libxslt before 1.1.29, as used in Google Chrome before 51.0.2704.63, mishandles namespace nodes, which allows remote attackers to cause a denial of service (out-of-bounds heap memory access) or possibly have unspecified other impact via a crafted document.

At a glance

Exploitability

Can be exploited over the network without logging in, but needs a user to act. High risk of data exposure, data tampering, service disruption.

Exploit odds

2.1% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2016-06-05 23:59 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 00:42 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 2.1% in the next 30 days (EPSS).
• Severity: 7.5 HIGH (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2016-06-05 23:59 UTC

Last modified

2026-06-17 00:42 UTC

Exploit probability

2.1% · EPSS, next 30 days

Weakness

CWE-119 · Buffer errors

Record status

Modified

Affected

• Xmlsoft Libxslt ≤ 1.1.28
• Canonical Ubuntu Linux 14.04
• Canonical Ubuntu Linux 15.10
• Canonical Ubuntu Linux 16.04
• Debian Linux 8.0
• Opensuse Leap 42.1
• Opensuse 13.2
• Redhat Enterprise Linux Desktop 6.0

Attack profile CVSS 3.0 · 7.5

Attack vector

Network

Complexity

High

Privileges needed

None

User interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2016-1683.md and follow it. Check whether this project is affected by CVE-2016-1683. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge