VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

vips: vulnerability history, versions and safety

vips is a package in the Debian ecosystem. Vulert records 32 vulnerabilities for it across 42 releases, from Oct 2010 to Aug 2026. 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 U32
i
19 with no fix published

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

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

Most recent disclosure 20 Aug 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all vips vulnerabilities

Vulert verdict on vips i

Updated on 23 Oct 2026

Careful: 19 of the 32 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 32 vulnerabilities on record across 15 years, 18 in the last year.

What to do: Plan around the 19 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 32 over 15 years · 18 in the last year i
  • Latest disclosure 20 Aug 2026 i
  • Highest CVSS 7.5 i
  • With no published fix 19 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 vips, 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 42 of 42 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2010 2
  • 2018 2
  • 2019 2
  • 2020 2
  • 2021 2
  • 2025 4
  • 2026 18

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

03 Vulnerabilities

Recorded vulnerabilities for vips

The 5 most severe of 32 vulnerabilities recorded for this package

Search all 32 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
NULL Function Pointer Dereference Vulnerability in libvips 7.5 high 8.4.5-2 09 Mar 2018
Division-By-Zero Vulnerability in Libvips Package - CVE-2021-27847 6.5 medium 8.8.3-1 15 Jul 2021
Critical Vulnerability in vips Package: CVE-2026-3147 5.3 medium No fix published 25 Feb 2026
Uninitialized Memory Leak in libvips 5.3 medium 8.7.4-1 26 Jan 2019
Memory Corruption Vulnerability in vips Package - CVE-2026-3145 5.3 medium No fix published 25 Feb 2026

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 vips

Is vips safe to use?

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

How many vulnerabilities does vips have?

32 vulnerabilities are recorded for vips in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 32 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 vips vulnerabilities disclosed?

18 vulnerabilities were recorded for vips in the last 12 months, and the oldest entry in this database dates to 20 Oct 2010. 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 vips 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 vips for upcoming vulnerabilities?

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