VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

libde265: vulnerability history, versions and safety

libde265 is a package in the Debian ecosystem. Vulert records 5 vulnerabilities for it across 12 releases, from Dec 2022 to Dec 2023. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
5 vulnerabilities recorded U5
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 libde265 vulnerabilities

Vulert verdict on libde265 i

Updated on 23 Oct 2026

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

Long-term outlook: usable, with an upgrade 5 vulnerabilities on record across 1 year, 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 5 over 1 year · 0 in the last year i
  • Latest disclosure 30 Dec 2023 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 libde265, 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 12 of 12 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 1
  • 2023 4

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

03 Vulnerabilities

Recorded vulnerabilities for libde265

The 5 most severe of 5 vulnerabilities recorded for this package

Search all 5 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Vulnerability in libde265 - Heap Buffer Overflow N/A unrated 1.0.3-1+deb10u1 15 Dec 2022
Vulnerability in libde265: Multiple Buffer Overflow Issues N/A unrated 1.0.3-1+deb10u3 24 Jan 2023
Vulnerability in libde265 - Buffer Overflow and Denial of Service N/A unrated 1.0.11-0+deb10u4 04 Mar 2023
Vulnerability in libde265 - Security Update N/A unrated 1.0.11-0+deb10u5 30 Nov 2023
Security Update for libde265 N/A unrated 1.0.11-0+deb10u6 30 Dec 2023

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 libde265

Is libde265 safe to use?

Vulert records 5 vulnerabilities for libde265 in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 5 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 libde265 have?

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

0 vulnerabilities were recorded for libde265 in the last 12 months, and the oldest entry in this database dates to 15 Dec 2022. 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 libde265 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 libde265 for upcoming vulnerabilities?

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