How to Fix CVE-2026-20889: LibRaw (Bundle Sibling)
*By Sai Kiran Pandrala*
Last verified: 2026-05-25
| Severity | CVSS 9.8, Critical |
|---|---|
| Actively exploited? | No |
| Affected | LibRaw (Commit d20315b) |
| Fixed in | Same patched build as CVE-2026-20884 |
| Type (CWE) | CWE-190: CWE-190: Integer Overflow or Wraparound |
CVE-2026-20889 is a sibling vulnerability in the same Libraw LibRaw advisory bundle as CVE-2026-20884. The same patched build closes every CVE in the bundle, so the remediation procedure for CVE-2026-20889 matches the primary write-up.
What is different about CVE-2026-20889?
A heap-based buffer overflow vulnerability exists in the x3f_thumb_loader functionality of LibRaw Commit d20315b. A specially crafted malicious file can lead to a heap buffer overflow. An attacker can provide a malicious file to trigger this vulnerability.
Impact is consistent with the bundle: memory corruption that can lead to code execution or a crash. The patched build closes every code path in the advisory in one update.
How to fix CVE-2026-20889
Apply the patched build per the primary write-up: How to Fix CVE-2026-20884.
For a quick check, confirm the running version of LibRaw:
# Confirm the installed version via your package manager
dpkg -l | grep -i libraw # Debian/Ubuntu
rpm -qa | grep -i libraw # RHEL/CentOS/Rocky
Frequently asked questions
Is CVE-2026-20889 being actively exploited?
Not at the time of writing. It is not listed in CISA's Known Exploited Vulnerabilities catalog. That status can change, so monitor the vendor advisory and the KEV catalog if the system is exposed.
How severe is CVE-2026-20889?
CVSS rates it 9.8 (Critical). Use that score to set your patch priority alongside the other items in your queue.
Do I have to take LibRaw offline to apply the patch?
It depends on the deployment. High-availability or clustered installs can usually patch one node at a time with no full outage. Standalone installs typically need a short restart. Always follow the vendor's documented upgrade steps.
What if my vulnerability scanner still flags CVE-2026-20889 after I patch?
Re-run the scan after a service restart, then confirm the scanner's plugin set is up to date. Some scanners detect by banner version only and lag the official fix metadata by a release.
References
- Official vendor advisory: https://talosintelligence.com/vulnerability_reports/TALOS-2026-2358
- NVD entry: https://nvd.nist.gov/vuln/detail/CVE-2026-20889
- CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
- Primary write-up: How to Fix CVE-2026-20884
*Written by Sai Kiran Pandrala. Last verified 2026-05-25. Part of the Libraw LibRaw advisory bundle. Full procedure at how-to-fix-cve-2026-20884.*