CVE-2024-56826 | Openjpeg: heap buffer overflow in bin/common/color.c

A flaw was found in the OpenJPEG project. A heap buffer overflow condition may be triggered when certain options are specified while using the opj_decompress utility. This can lead to an application crash or other undefined behavior.

Published: 2025-01-09 Last update: 2026-04-15 Assigner: [email protected] Source: [email protected]
NVD Status：Deferred，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2024-56826 is rated Low Risk (25.9/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.03%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2024-56826

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-02-17 0.05% 0.03% -0.02%
2 2025-09-25 0.04% 0.05% +0.01%
3 2025-01-09 — 0.04% —

Full EPSS history (3 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2024-56826

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.6 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.3 4.2 [email protected]

Weakness enumeration for CVE-2024-56826

OS Trackers for CVE-2024-56826

vendor priority summary link
debian not yet assigned CVE-2024-56826 not yet assigned priority: Debian including 1 source packages (openjpeg2), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2024-56826
redhat medium — https://access.redhat.com/security/cve/CVE-2024-56826
suse medium CVE-2024-56826 severity moderate: SUSE including 30 source package names (0.3.2-1.2:libopenjp2-7-2.3.0-150000.3.18.1, 0.9.1-1.2:libopenjp2-7-2.3.0-150000.3.18.1, …), 104 product×package rows across 47 product lines (Container containers/lmcache-vllm-openai, Container containers/open-webui, … (47 product lines)): Known Not Affected 54, Fixed 50. https://www.suse.com/security/cve/CVE-2024-56826/
ubuntu medium CVE-2024-56826 medium priority: Ubuntu including 7 source packages (blender, ghostscript, …), 62 status rows across 10 suites (bionic, focal, jammy, noble, oracular, plucky, questing, trusty, upstream, xenial): needs-triage 27, released 11, DNE 10, not-affected 8, ignored 6. https://ubuntu.com/security/CVE-2024-56826

Affected software / configurations for CVE-2024-56826

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2024-56826

cvelogic Threat Intelligence