VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

libraw: vulnerability history, versions and safety

libraw is a package in the Debian ecosystem. Vulert records 103 vulnerabilities for it across 23 releases, from May 2017 to Apr 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
103 vulnerabilities recorded U103
i
10 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
8 in the last 12 months

Most recent disclosure 07 Apr 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all libraw vulnerabilities

Vulert verdict on libraw i

Updated on 23 Oct 2026

Careful: 10 of the 103 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 103 vulnerabilities on record across 8 years, 8 in the last year.

What to do: Plan around the 10 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 103 over 8 years · 8 in the last year i
  • Latest disclosure 07 Apr 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 10 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for libraw, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

Newest 23 of 23 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2017 8
  • 2018 45
  • 2019 6
  • 2020 6
  • 2021 2
  • 2022 12
  • 2023 7
  • 2025 9
  • 2026 8

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 8 of the 103 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for libraw

The 5 most severe of 103 vulnerabilities recorded for this package

Search all 103 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Heap-Based Buffer Overflow in LibRaw: CVE-2026-21413 Vulnerability 9.8 critical No fix published 07 Apr 2026
Heap-Based Buffer Overflow in LibRaw: CVE-2026-20911 9.8 critical No fix published 07 Apr 2026
LibRaw Vulnerability CVE-2025-43964: Insufficient Tag Processing in Phase One Correction 9.8 critical 0.20.2-1+deb11u2 21 Apr 2025
Heap-Based Buffer Overflow in LibRaw: CVE-2026-20889 9.8 critical No fix published 07 Apr 2026
Out-of-Bounds Read Vulnerability in LibRaw Package 9.1 critical 0.20.2-1+deb11u2 21 Apr 2025

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About libraw

Is libraw safe to use?

Vulert records 103 vulnerabilities for libraw in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 103 not yet rated. 10 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does libraw have?

103 vulnerabilities are recorded for libraw in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 103 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new libraw vulnerabilities disclosed?

8 vulnerabilities were recorded for libraw in the last 12 months, and the oldest entry in this database dates to 16 May 2017. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of libraw are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor libraw for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the libraw version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.