# CVE-2025-32365: Memory corruption in Poppler

> Crafted input files trigger out-of-bounds reads in Poppler, potentially causing crashes or information disclosure.

- **Severity:** Medium 4.0 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Apr 2025
- **Updated:** 3 Nov 2025
- **Also known as:** ALSA-2026:0126, ALSA-2026:0128, ALSA-2026:0130, BELL-CVE-2025-32365, CLSA-2025-1761261363, CLSA-2025-1763139862, CLSA-2025-1764868919, DEBIAN-CVE-2025-32365, GHSA-r4rq-7765-p57x, JLSEC-2026-86, RHSA-2026:0126, RHSA-2026:0128, RHSA-2026:0130, RHSA-2026:0772, RHSA-2026:0773, RHSA-2026:0774, RHSA-2026:0795, RHSA-2026:0796, RHSA-2026:0797, RHSA-2026:0799, RHSA-2026:1090, RHSA-2026:1091, RLSA-2026:0126, RLSA-2026:0128, RLSA-2026:0130, UBUNTU-CVE-2025-32365

## What is CVE-2025-32365?

CVE-2025-32365 is a medium-severity memory corruption vulnerability in Freedesktop Poppler, published on 5 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Poppler before 25.04.0 allows crafted input files to trigger out-of-bounds reads in the JBIG2Bitmap::combine function in JBIG2Stream.cc because of a misplaced isOk check.

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

## Which versions are affected by CVE-2025-32365?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `poppler-glib-doc` | AlmaLinux:10 | All versions | 24.02.0-7.el10_1 |
| `poppler` | AlmaLinux:8 | All versions | 20.11.0-13.el8_10 |
| `poppler-cpp` | AlmaLinux:8 | All versions | 20.11.0-13.el8_10 |
| `poppler-cpp-devel` | AlmaLinux:8 | All versions | 20.11.0-13.el8_10 |
| `poppler-devel` | AlmaLinux:8 | All versions | 20.11.0-13.el8_10 |
| `poppler-glib` | AlmaLinux:8 | All versions | 20.11.0-13.el8_10 |
| `poppler-glib-devel` | AlmaLinux:8 | All versions | 20.11.0-13.el8_10 |
| `poppler-glib-doc` | AlmaLinux:8 | All versions | 20.11.0-13.el8_10 |
| `poppler-qt5` | AlmaLinux:8 | All versions | 20.11.0-13.el8_10 |
| `poppler-qt5-devel` | AlmaLinux:8 | All versions | 20.11.0-13.el8_10 |
| `poppler-utils` | AlmaLinux:8 | All versions | 20.11.0-13.el8_10 |
| `poppler` | AlmaLinux:9 | All versions | 21.01.0-23.el9_7 |
| `poppler-cpp` | AlmaLinux:9 | All versions | 21.01.0-23.el9_7 |
| `poppler-cpp-devel` | AlmaLinux:9 | All versions | 21.01.0-23.el9_7 |
| `poppler-devel` | AlmaLinux:9 | All versions | 21.01.0-23.el9_7 |
| `poppler-glib` | AlmaLinux:9 | All versions | 21.01.0-23.el9_7 |
| `poppler-glib-devel` | AlmaLinux:9 | All versions | 21.01.0-23.el9_7 |
| `poppler-glib-doc` | AlmaLinux:9 | All versions | 21.01.0-23.el9_7 |
| `poppler-qt5` | AlmaLinux:9 | All versions | 21.01.0-23.el9_7 |
| `poppler-qt5-devel` | AlmaLinux:9 | All versions | 21.01.0-23.el9_7 |
| `poppler-utils` | AlmaLinux:9 | All versions | 21.01.0-23.el9_7 |
| `poppler` | Red Hat:enterprise_linux:10.1 | All versions | 0:24.02.0-7.el10_1 |
| `poppler-cpp` | Red Hat:enterprise_linux:10.1 | All versions | 0:24.02.0-7.el10_1 |
| `poppler-cpp-debuginfo` | Red Hat:enterprise_linux:10.1 | All versions | 0:24.02.0-7.el10_1 |
| `poppler-cpp-devel` | Red Hat:enterprise_linux:10.1 | All versions | 0:24.02.0-7.el10_1 |
| `poppler-debuginfo` | Red Hat:enterprise_linux:10.1 | All versions | 0:24.02.0-7.el10_1 |
| `poppler-debugsource` | Red Hat:enterprise_linux:10.1 | All versions | 0:24.02.0-7.el10_1 |
| `poppler-devel` | Red Hat:enterprise_linux:10.1 | All versions | 0:24.02.0-7.el10_1 |
| `poppler-glib` | Red Hat:enterprise_linux:10.1 | All versions | 0:24.02.0-7.el10_1 |
| `poppler-glib-debuginfo` | Red Hat:enterprise_linux:10.1 | All versions | 0:24.02.0-7.el10_1 |
| `poppler-glib-devel` | Red Hat:enterprise_linux:10.1 | All versions | 0:24.02.0-7.el10_1 |
| `poppler-glib-doc` | Red Hat:enterprise_linux:10.1 | All versions | 0:24.02.0-7.el10_1 |
| `poppler-qt6` | Red Hat:enterprise_linux:10.1 | All versions | 0:24.02.0-7.el10_1 |
| `poppler-qt6-debuginfo` | Red Hat:enterprise_linux:10.1 | All versions | 0:24.02.0-7.el10_1 |
| `poppler-qt6-devel` | Red Hat:enterprise_linux:10.1 | All versions | 0:24.02.0-7.el10_1 |
| `poppler-utils` | Red Hat:enterprise_linux:10.1 | All versions | 0:24.02.0-7.el10_1 |
| `poppler-utils-debuginfo` | Red Hat:enterprise_linux:10.1 | All versions | 0:24.02.0-7.el10_1 |
| `poppler` | Red Hat:enterprise_linux:8::appstream | All versions | 0:20.11.0-13.el8_10 |
| `poppler-cpp-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:20.11.0-13.el8_10 |
| `poppler-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:20.11.0-13.el8_10 |

Products: Freedesktop Poppler.

## How do I fix CVE-2025-32365?

Upgrade to a fixed version.

## Is CVE-2025-32365 being exploited?

There is no known exploitation of CVE-2025-32365 in the wild and no public exploit code.

## 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-2025-32365 and fix it if it is affected.

What it is: CVE-2025-32365 is a medium-severity memory corruption vulnerability in Freedesktop Poppler, published on 5 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-32365 in the wild and no public exploit code.

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-2025-32365/ (Markdown: https://insights.sbomify.com/CVE-2025-32365/index.md)
```

## Sources

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

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