# CVE-2026-107705: Poppler 0.42.0 through 26.10.0 Stack Buffer Overflow via Decrypt::revision6Hash() > Attackers can trigger a stack buffer overflow in Poppler by supplying an overly long password for encrypted PDFs, potentially leading to code execution or crashes. - **Severity:** High 8.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 8 Oct 2026 - **Updated:** 14 Oct 2026 - **Also known as:** BELL-CVE-2026-107705, CLSA-2026-1791810115, DEBIAN-CVE-2026-107705, ECHO-401d-da1f-058c, GHSA-939q-g65h-55jw, RHSA-2026:80172, RHSA-2026:80579, UBUNTU-CVE-2026-107705, USN-8950-1, openSUSE-SU-2026:12145-1 ## What is CVE-2026-107705? CVE-2026-107705 is a high-severity memory corruption vulnerability in freedesktop poppler, published on 8 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description Poppler 0.42.0 through 26.10.0 contains a stack-based buffer overflow in Decrypt::revision6Hash() that allows attackers controlling the password to overwrite stack memory when opening AESV3/R6 encrypted PDFs. Attackers can supply a password longer than 127 bytes through applications using the libpoppler, libpoppler-glib or C++ API to overflow the K1 and E buffers, crashing the process or corrupting memory. Weakness: CWE-121 (Stack-based Buffer Overflow) ## Which versions are affected by CVE-2026-107705? | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `poppler` | Red Hat:hummingbird:1 | All versions | 0:26.08.0-1.3.hum1 | | `poppler` | Red Hat:hummingbird:1 | All versions | 0:26.08.0-1.4.hum1 | | `poppler-cpp` | Red Hat:hummingbird:1 | All versions | 0:26.08.0-1.3.hum1 | | `poppler-cpp` | Red Hat:hummingbird:1 | All versions | 0:26.08.0-1.4.hum1 | | `poppler-cpp-devel` | Red Hat:hummingbird:1 | All versions | 0:26.08.0-1.3.hum1 | | `poppler-cpp-devel` | Red Hat:hummingbird:1 | All versions | 0:26.08.0-1.4.hum1 | | `poppler-devel` | Red Hat:hummingbird:1 | All versions | 0:26.08.0-1.3.hum1 | | `poppler-devel` | Red Hat:hummingbird:1 | All versions | 0:26.08.0-1.4.hum1 | | `poppler-glib` | Red Hat:hummingbird:1 | All versions | 0:26.08.0-1.3.hum1 | | `poppler-glib` | Red Hat:hummingbird:1 | All versions | 0:26.08.0-1.4.hum1 | | `poppler-glib-devel` | Red Hat:hummingbird:1 | All versions | 0:26.08.0-1.3.hum1 | | `poppler-glib-devel` | Red Hat:hummingbird:1 | All versions | 0:26.08.0-1.4.hum1 | | `poppler-glib-doc` | Red Hat:hummingbird:1 | All versions | 0:26.08.0-1.3.hum1 | | `poppler-glib-doc` | Red Hat:hummingbird:1 | All versions | 0:26.08.0-1.4.hum1 | | `poppler-qt6` | Red Hat:hummingbird:1 | All versions | 0:26.08.0-1.3.hum1 | | `poppler-qt6` | Red Hat:hummingbird:1 | All versions | 0:26.08.0-1.4.hum1 | | `poppler-qt6-devel` | Red Hat:hummingbird:1 | All versions | 0:26.08.0-1.3.hum1 | | `poppler-qt6-devel` | Red Hat:hummingbird:1 | All versions | 0:26.08.0-1.4.hum1 | | `poppler-utils` | Red Hat:hummingbird:1 | All versions | 0:26.08.0-1.3.hum1 | | `poppler-utils` | Red Hat:hummingbird:1 | All versions | 0:26.08.0-1.4.hum1 | | `poppler` | openSUSE:Tumbleweed | All versions | 26.10.0-1.1 | ## How do I fix CVE-2026-107705? Apply the vendor's patch. ## Is CVE-2026-107705 being exploited? There is no known exploitation of CVE-2026-107705 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-107705 and fix it if it is affected. What it is: CVE-2026-107705 is a high-severity memory corruption vulnerability in freedesktop poppler, published on 8 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-107705 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-2026-107705/ (Markdown: https://insights.sbomify.com/CVE-2026-107705/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-107705 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-107705 - OSV: https://osv.dev/vulnerability/CVE-2026-107705 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-107705/ Summaries are generated and may contain mistakes; the official description above is the record.