VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

libsdl2-image: vulnerability history, versions and safety

libsdl2-image is a package in the Debian ecosystem. Vulert records 29 vulnerabilities for it across 31 releases, from Oct 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
29 vulnerabilities recorded U29
i
1 with no fix published

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

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

Most recent disclosure 06 Apr 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all libsdl2-image vulnerabilities

Vulert verdict on libsdl2-image i

Updated on 23 Oct 2026

Careful: one of the 29 vulnerabilities Vulert records for this package has no fix yet. Plan around that one, or apply its workaround. The rest have a fixed version to move to.

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

What to do: Plan around the 1 vulnerability 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 29 over 8 years · 1 in the last year i
  • Latest disclosure 06 Apr 2026 i
  • Highest CVSS 8.8 i
  • With no published fix 1 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 libsdl2-image, 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 31 of 31 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2017 1
  • 2018 12
  • 2019 15
  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for libsdl2-image

The 5 most severe of 29 vulnerabilities recorded for this package

Search all 29 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Heap Overflow Vulnerability in SDL2_image Package Leading to Code Execution 8.8 high 2.0.3+dfsg1-3 01 Nov 2018
Heap Out-of-Bounds Read in SDL_image Library - CVE-2026-35444 7.1 high No fix published 06 Apr 2026
Heap-Based Buffer Overflow in SDL2_image Package 6.5 medium 2.0.5+dfsg1-1 20 May 2019
Out-of-Bounds Read Vulnerability in SDL2_image Package 6.5 medium 2.0.5+dfsg1-1 20 May 2019
Buffer Overflow Vulnerability in libsdl2-image and sdl-image1.2 Packages N/A unrated 2.0.1+dfsg-4 11 Oct 2017

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 libsdl2-image

Is libsdl2-image safe to use?

Vulert records 29 vulnerabilities for libsdl2-image in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 29 not yet rated. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

How many vulnerabilities does libsdl2-image have?

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

1 vulnerability was recorded for libsdl2-image in the last 12 months, and the oldest entry in this database dates to 11 Oct 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 libsdl2-image 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 libsdl2-image for upcoming vulnerabilities?

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