CVE Intelligence
Critical Memory corruption

CVE-2019-12900 — BZ2_decompress in decompress.c in bzip2 through 1.0.6 has an out-of-bounds write when there are...

BZ2_decompress in decompress.c in bzip2 through 1.0.6 has an out-of-bounds write when there are many selectors.

Published Jun 19, 2019 · Updated Oct 14, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: mitre

Who exploits it and how urgent it is

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

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 8% (30-day exploitation probability)+14
  • Technical severity (critical)+10
  • Automatable exploitation (SSVC)+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.98%
ahead of 95% of scored CVEs · Oct 14, 2026
Affects
Bzip
Bzip2 and 5 more
CVSS base
9.8
Critical · 4 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
Yes
can an attacker script the kill-chain steps
Technical impact
Total
partial · total control of the vulnerable component

Remediation

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

  • Documented patch — gitlab.com (NIST National Vulnerability Database)
  • Documented patch — seclists.org (NIST National Vulnerability Database)
  • Documented patch — security.FreeBSD.org (NIST National Vulnerability Database)
  • Documented patch — www.oracle.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 (Bzip Bzip2, Canonical Ubuntu Linux, Debian Debian Linux…).
  2. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
  3. Apply the fixed version or the patch documented under Remediation.
  4. EPSS ahead of 95% 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
Bzip Bzip2 ≤ 1.0.6 Vulnerable NIST National Vulnerability Database
Canonical Ubuntu Linux version 12.04version 19.04version 18.04version 14.04version 16.04 Vulnerable NIST National Vulnerability Database
Debian Debian Linux version 8.0 Vulnerable NIST National Vulnerability Database
Freebsd Freebsd version 11.2-p6version 12.0-p5version 12.0-p4version 12.0-p3version 12.0-p2version 12.0-p1version 12.0version 11.3-p1
and 16 more version 11.3version 11.2-rc3version 11.2-p9version 11.2-p8version 11.2-p7version 11.2-p5version 11.2-p4version 11.2-p3version 11.2-p2version 11.2-p12version 11.2-p11version 11.2-p10version 11.2version 12.0-p6version 12.0-p7version 12.0-p8
Vulnerable NIST National Vulnerability Database
Opensuse Leap version 15.0version 15.1 Vulnerable NIST National Vulnerability Database
Python Python ≥ 3.10.0 and < 3.10.3≥ 3.9.0 and < 3.9.11≥ 3.8.0 and < 3.8.13≥ 3.7.0 and < 3.7.13 Vulnerable NIST National Vulnerability Database

Attack characteristics

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

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
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
9.8 CVSS 3.1 Critical 3.9 5.9 nvd@nist.gov via NIST National Vulnerability Database
9.8 CVSS 3.1 Critical 3.9 5.9 134c704f-9b21-4f2e-91b3-4a467353bcc0 via NIST National Vulnerability Database
9.8 CVSS 3.1 Critical — — GitHub, Inc. via GitHub Security Advisories
9.8 CVSS 3.1 Critical — — CISA-ADP via CVE Program (cve.org) e CISA ADP
7.5 CVSS 2.0 High 10.0 6.4 nvd@nist.gov via NIST National Vulnerability Database
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (score shown at the top: nvd@nist.gov)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-787 · Out-of-bounds Write

Other CVEs with this weakness →

EPSS over time FIRST

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

Detection

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

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Correlate service crashes/restarts with inbound traffic; repeated crashes may indicate attempts.
web/proxy/WAF logsnetwork IDS/IPSendpoint telemetry (EDR)crash dumps

Timeline

What happened to this CVE, newest first.

  • 2026
  • SSVC assessment updated
    Oct 14, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 14, 2026
  • Fix documented
    Oct 14, 2026 · NIST National Vulnerability Database
  • Affected products added · bzip/bzip2, debian/debian linux, opensuse/leap, canonical/ubuntu linux, freebsd/freebsd, python/python
    Oct 14, 2026 · NIST National Vulnerability Database
  • CVSS changed · 9.8
    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
  • 2019
  • CVE published
    Jun 19, 2019 · mitre

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

35 on the record

Elsewhere on this site

Bzip
every CVE for this vendor
Memory corruption
same class
CWE-787
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-101310 Multiple vulnerabilities in bhyve device models 13h
  • CVE-2026-101311 Multiple vulnerabilities in bhyve device models 13h
  • CVE-2026-101309 Multiple vulnerabilities in bhyve device models 13h
  • CVE-2026-58100 Memory safety bugs in kqueue copy-on-fork implementation 14h
  • CVE-2026-58098 Heap out-of-bounds access in semop(2) 14h
  • CVE-2026-58099 Memory safety bugs in kqueue copy-on-fork implementation 14h

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 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-2019-12900 is "BZ2_decompress in decompress.c in bzip2 through 1.0.6 has an out-of-bounds write when there are...", rated Critical. It affects Bzip2 (Bzip); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 9.8 describes technical severity. EPSS 7.98% 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.