Skip to main content
VulnerabilityPublished Updated

CVE-2023-51792: libde265 · Buffer Overflow

Affects libde265Source CVE Database V5

0

Not known to be exploited · CVSS 3.3 Low.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score
3.3Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Apr 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubstrukturag/libde265pkg:github/strukturag/libde265Other threatsAffected
  • =1.0.12
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

  1. Monitor official libde265 repositories and security advisories for patches addressing CVE-2023-51792 and apply updates promptly once available.
  2. Restrict local user permissions to minimize the number of users who can execute or interact with applications using libde265, reducing the attack surface.
  3. Employ application whitelisting and endpoint protection to detect and prevent unauthorized local code execution attempts.
  4. Conduct regular audits of systems running libde265 to identify and isolate vulnerable versions.
  5. Where feasible, sandbox or containerize applications using libde265 to limit the impact of potential crashes or denial of service.
  6. Implement monitoring for abnormal application crashes or resource usage spikes that could indicate exploitation attempts.
  7. Educate system administrators and users about the risks of local privilege abuse and enforce strong access controls. These steps go beyond generic advice by focusing on controlling local access, proactive patch management, and operational monitoring specific to the nature of this vulnerability.

Description

Buffer Overflow vulnerability in libde265 v1.0.12 allows a local attacker to cause a denial of service via the allocation size exceeding the maximum supported size of 0x10000000000.

References

Community reviews

Loading reviews…