CVE-2016-1684 · cross-distro fix matrix

CVE-2016-1684: numbers.c in libxslt before 1.1.29, as used in Google Chrome before 51.0.2704.63, mishandles the i format token for xsl:number data, which allows remote attackers to cause a denial of service (integer overflow or resource consumption) or possibly have unspecified other impact via a crafted document.

Affects 3 Linux releases across 3 (distro × package) combinations.

Fix per ecosystem

Each block below is a distro release where CVE-2016-1684 has a known fix. Run the listed command on that distro to remediate.

Debian bullseye

Source: Debian Security Tracker

libxslt→ fixed in1.1.29-1urgency: not yet assigned
```
sudo apt-get install --only-upgrade -y libxslt
```

Debian bookworm

Source: Debian Security Tracker

libxslt→ fixed in1.1.29-1urgency: not yet assigned
```
sudo apt-get install --only-upgrade -y libxslt
```

Debian trixie

Source: Debian Security Tracker

libxslt→ fixed in1.1.29-1urgency: not yet assigned
```
sudo apt-get install --only-upgrade -y libxslt
```

Are YOU affected by CVE-2016-1684?

5-second check on your actual server. Reads /etc/os-release, uname -r, and the distro's package manager; matches against this same cross-source index live.

curl https://mindsparkstack.com/scan.sh | bash

Form-based quickscan View on NVD

Continuous monitoring beats manual checking

CVE-2016-1684dropped silently in your distro's update channel. Every new CVE is the same story. StackPatch runs the matcher hourly against all 5 sources and emails the exact remediation when something new applies to one of your servers. $99 lifetime, 50 founder seats, 30-day refund.

See StackPatch ($99 lifetime)