# CVE-2024-56378: Memory corruption in n/a

> An out-of-bounds read in Poppler's JBIG2Bitmap::combine function allows attackers to cause denial of service or disclose information via crafted PDFs.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Dec 2024
- **Updated:** 3 Nov 2025
- **Also known as:** BELL-CVE-2024-56378, CLSA-2026-1787750503, CLSA-2026-1788270342, DEBIAN-CVE-2024-56378, GHSA-h369-f67q-2q4c, JLSEC-2026-83, MGASA-2025-0022, OESA-2024-2602, OESA-2025-1018, SUSE-SU-2024:4421-1, SUSE-SU-2024:4422-1, SUSE-SU-2024:4423-1, SUSE-SU-2024:4432-1, SUSE-SU-2024:4435-1, UBUNTU-CVE-2024-56378, USN-7213-1, openSUSE-SU-2025:14616-1

## What is CVE-2024-56378?

CVE-2024-56378 is a medium-severity memory corruption vulnerability in Freedesktop Poppler, published on 22 Dec 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

libpoppler.so in Poppler through 24.12.0 has an out-of-bounds read vulnerability within the JBIG2Bitmap::combine function in JBIG2Stream.cc.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2024-56378?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `poppler` | SUSE:Linux Enterprise Module for Basesystem 15 SP6 | All versions | 0.79.0-150200.3.35.1 |
| `poppler` | SUSE:Linux Enterprise Module for Basesystem 15 SP6 | All versions | 24.03.0-150600.3.5.1 |
| `poppler` | SUSE:Linux Enterprise Module for Package Hub 15 SP6 | All versions | 24.03.0-150600.3.5.1 |
| `poppler-qt5` | SUSE:Linux Enterprise Module for Package Hub 15 SP6 | All versions | 24.03.0-150600.3.5.1 |
| `poppler-qt6` | SUSE:Linux Enterprise Module for Package Hub 15 SP6 | All versions | 24.03.0-150600.3.5.1 |
| `poppler` | SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5 | All versions | 0.43.0-16.52.1 |
| `poppler-qt` | SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5 | All versions | 0.43.0-16.52.1 |
| `poppler` | openSUSE:Leap 15.5 | All versions | 23.01.0-150500.3.14.1 |
| `poppler-qt5` | openSUSE:Leap 15.5 | All versions | 23.01.0-150500.3.14.1 |
| `poppler-qt6` | openSUSE:Leap 15.5 | All versions | 23.01.0-150500.3.14.1 |
| `poppler` | openSUSE:Leap 15.6 | All versions | 24.03.0-150600.3.5.1 |
| `poppler-qt5` | openSUSE:Leap 15.6 | All versions | 24.03.0-150600.3.5.1 |
| `poppler-qt6` | openSUSE:Leap 15.6 | All versions | 24.03.0-150600.3.5.1 |
| `poppler` | openSUSE:Tumbleweed | All versions | 24.12.0-1.1 |

Products: Freedesktop Poppler.

## How do I fix CVE-2024-56378?

Upgrade to a fixed version.

## Is CVE-2024-56378 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-56378 exists.

## Other vulnerabilities in Freedesktop Poppler

- [CVE-2018-21009](https://insights.sbomify.com/CVE-2018-21009/): Integer overflow in n/a (high 8.8)
- [CVE-2019-12293](https://insights.sbomify.com/CVE-2019-12293/): Memory corruption in n/a (high 8.8)
- [CVE-2019-10872](https://insights.sbomify.com/CVE-2019-10872/): Memory corruption in n/a (high 8.8)
- [CVE-2019-9543](https://insights.sbomify.com/CVE-2019-9543/): Denial of service in n/a (high 8.8)
- [CVE-2019-9545](https://insights.sbomify.com/CVE-2019-9545/): Denial of service in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-56378 and fix it if it is affected.

What it is: CVE-2024-56378 is a medium-severity memory corruption vulnerability in Freedesktop Poppler, published on 22 Dec 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-56378 exists.

Affected product: Freedesktop Poppler. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-56378/ (Markdown: https://insights.sbomify.com/CVE-2024-56378/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-56378
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-56378
- OSV: https://osv.dev/vulnerability/CVE-2024-56378

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-56378/
Summaries are generated and may contain mistakes; the official description above is the record.