VulertSecurity VulertSecurity

Vulnerability Database · OSS-Fuzz · Package report

libvips: vulnerability history, versions and safety

libvips is a package in the OSS-Fuzz ecosystem. Vulert records 32 vulnerabilities for it across 12 releases, from Jun 2020 to Feb 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
32 vulnerabilities recorded H13 M15 U4
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all libvips vulnerabilities

Vulert verdict on libvips i

Updated on 23 Oct 2026

Every vulnerability Vulert records for this package has a fix, and the newest was recorded 16 Feb 2025. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 32 vulnerabilities on record across 4 years, none in the last year.

What to do: Move the affected dependencies to the fixed versions listed below, then keep the package monitored so the next vulnerability reaches you. Fix it, then keep watch: Vulert alerts you when a new vulnerability affects the version you run. Monitor it with Vulert →

  • Vulnerabilities on record 32 over 4 years · 0 in the last year i
  • Latest disclosure 16 Feb 2025 i
  • Highest CVSS n/a i
  • With no published fix 0 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 libvips, 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.

i
Version Vulert vulnerabilities Fix published Details
v8.16.1 H1 Yes Details →
v8.13.0-rc1 U1 Yes Details →
v8.12.2 M3 Yes Details →
v8.12.1 M3 Yes Details →
v8.12.0 M3 Yes Details →
v8.11.4 H1 M1 Yes Details →
v8.11.3 H1 M1 Yes Details →
v8.11.2 H1 Yes Details →
v8.11.1 H1 Yes Details →
v8.11.0 H1 Yes Details →
v8.11.0-rc1 H1 Yes Details →
v8.11 H1 Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 4
  • 2021 7
  • 2022 17
  • 2023 1
  • 2024 1
  • 2025 2

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

03 Vulnerabilities

Recorded vulnerabilities for libvips

The 5 most severe of 32 vulnerabilities recorded for this package

Search all 32 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Heap-use-after-free in start_pass_phuff_decoder in libvips N/A high 2dc319b1b1610e4c8ae95b8ca47b46926cd41ce1 05 Apr 2022
Heap-use-after-free vulnerability in libvips N/A high 0f30690360a647360b0c712bd97401caf21f8007 05 Apr 2022
Heap-buffer-overflow in libvips: RegionItem::parse N/A medium e34cbae4b7162db783d3677ac09112394690ccb1 20 Apr 2023
Heap-buffer-overflow in libvips: gif_internal_decode_frame N/A high f726edb7f71f05f2af6f08a7442354c1b70e9383 04 Apr 2021
Heap-buffer-overflow in libvips: jxl::N_AVX2::BlendingStage::ProcessRow N/A medium eaf34b8f13d22b35acf2e07775c12ae5ccd615fd 21 Mar 2022

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 libvips

Is libvips safe to use?

Vulert records 32 vulnerabilities for libvips in OSS-Fuzz: 0 critical, 13 high, 15 medium and 0 low, plus 4 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

How many vulnerabilities does libvips have?

32 vulnerabilities are recorded for libvips in the OSS-Fuzz ecosystem: 0 critical, 13 high, 15 medium and 0 low, plus 4 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 libvips vulnerabilities disclosed?

0 vulnerabilities were recorded for libvips in the last 12 months, and the oldest entry in this database dates to 24 Jun 2020. 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 libvips 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 libvips for upcoming vulnerabilities?

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