# CVE-2026-10118: Integer overflow in Red Hat AI Inference Server 3.3 > A remote attacker can execute arbitrary code or cause denial of service by tricking a user into opening a malicious PDF file that triggers an integer overflow in Poppler. - **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Local or same network only - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 1 Jun 2026 - **Updated:** 2 Oct 2026 - **Also known as:** ALSA-2026:24984, ALSA-2026:24985, ALSA-2026:25058, BELL-CVE-2026-10118, CLSA-2026-1781354122, CLSA-2026-1781514933, CLSA-2026-1792784815, DEBIAN-CVE-2026-10118, ECHO-c3b3-3988-eeb5, GHSA-469x-qwp6-693q, MGASA-2026-0256, OESA-2026-2603, OESA-2026-2648, OESA-2026-2649, OESA-2026-2650, RHSA-2026:24984, RHSA-2026:24985, RHSA-2026:25058, RHSA-2026:27720, RHSA-2026:27721, RHSA-2026:27722, RHSA-2026:27723, RHSA-2026:27724, RHSA-2026:27725, RHSA-2026:27727, RHSA-2026:29952, RHSA-2026:30044, RHSA-2026:30134, RLSA-2026:24984, RLSA-2026:24985, RLSA-2026:25058, UBUNTU-CVE-2026-10118, USN-8400-1 ## What is CVE-2026-10118? CVE-2026-10118 is a high-severity vulnerability in Red Hat AI Inference Server 3.3, published on 1 Jun 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. ### Official description A flaw was found in Poppler's Splash backend. A remote attacker could exploit this vulnerability by crafting a malicious PDF file that, when rendered, triggers an integer overflow in the `tilingPatternFill` function. This overflow leads to an undersized heap memory allocation, allowing a subsequent out-of-bounds write. Successful exploitation could result in arbitrary code execution, information disclosure, or denial of service within the context of the application processing the PDF. Weakness: CWE-190 (Integer Overflow or Wraparound) ## Which versions are affected by CVE-2026-10118? | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `poppler` | AlmaLinux:10 | All versions | 24.02.0-7.el10_2.2 | | `poppler-cpp` | AlmaLinux:10 | All versions | 24.02.0-7.el10_2.2 | | `poppler-cpp-devel` | AlmaLinux:10 | All versions | 24.02.0-7.el10_2.2 | | `poppler-devel` | AlmaLinux:10 | All versions | 24.02.0-7.el10_2.2 | | `poppler-glib` | AlmaLinux:10 | All versions | 24.02.0-7.el10_2.2 | | `poppler-glib-devel` | AlmaLinux:10 | All versions | 24.02.0-7.el10_2.2 | | `poppler-glib-doc` | AlmaLinux:10 | All versions | 24.02.0-7.el10_2.2 | | `poppler-qt6` | AlmaLinux:10 | All versions | 24.02.0-7.el10_2.2 | | `poppler-qt6-devel` | AlmaLinux:10 | All versions | 24.02.0-7.el10_2.2 | | `poppler-utils` | AlmaLinux:10 | All versions | 24.02.0-7.el10_2.2 | | `poppler` | AlmaLinux:8 | All versions | 20.11.0-14.el8_10 | | `poppler-cpp` | AlmaLinux:8 | All versions | 20.11.0-14.el8_10 | | `poppler-cpp-devel` | AlmaLinux:8 | All versions | 20.11.0-14.el8_10 | | `poppler-devel` | AlmaLinux:8 | All versions | 20.11.0-14.el8_10 | | `poppler-glib` | AlmaLinux:8 | All versions | 20.11.0-14.el8_10 | | `poppler-glib-devel` | AlmaLinux:8 | All versions | 20.11.0-14.el8_10 | | `poppler-glib-doc` | AlmaLinux:8 | All versions | 20.11.0-14.el8_10 | | `poppler-qt5` | AlmaLinux:8 | All versions | 20.11.0-14.el8_10 | | `poppler-qt5-devel` | AlmaLinux:8 | All versions | 20.11.0-14.el8_10 | | `poppler-utils` | AlmaLinux:8 | All versions | 20.11.0-14.el8_10 | | `poppler` | AlmaLinux:9 | All versions | 21.01.0-24.el9_8.1 | | `poppler-cpp` | AlmaLinux:9 | All versions | 21.01.0-24.el9_8.1 | | `poppler-cpp-devel` | AlmaLinux:9 | All versions | 21.01.0-24.el9_8.1 | | `poppler-devel` | AlmaLinux:9 | All versions | 21.01.0-24.el9_8.1 | | `poppler-glib` | AlmaLinux:9 | All versions | 21.01.0-24.el9_8.1 | | `poppler-glib-devel` | AlmaLinux:9 | All versions | 21.01.0-24.el9_8.1 | | `poppler-glib-doc` | AlmaLinux:9 | All versions | 21.01.0-24.el9_8.1 | | `poppler-qt5` | AlmaLinux:9 | All versions | 21.01.0-24.el9_8.1 | | `poppler-qt5-devel` | AlmaLinux:9 | All versions | 21.01.0-24.el9_8.1 | | `poppler-utils` | AlmaLinux:9 | All versions | 21.01.0-24.el9_8.1 | | `poppler` | Red Hat:enterprise_linux:10.2 | All versions | 0:24.02.0-7.el10_2.2 | | `poppler-cpp` | Red Hat:enterprise_linux:10.2 | All versions | 0:24.02.0-7.el10_2.2 | | `poppler-cpp-debuginfo` | Red Hat:enterprise_linux:10.2 | All versions | 0:24.02.0-7.el10_2.2 | | `poppler-cpp-devel` | Red Hat:enterprise_linux:10.2 | All versions | 0:24.02.0-7.el10_2.2 | | `poppler-debuginfo` | Red Hat:enterprise_linux:10.2 | All versions | 0:24.02.0-7.el10_2.2 | | `poppler-debugsource` | Red Hat:enterprise_linux:10.2 | All versions | 0:24.02.0-7.el10_2.2 | | `poppler-devel` | Red Hat:enterprise_linux:10.2 | All versions | 0:24.02.0-7.el10_2.2 | | `poppler-glib` | Red Hat:enterprise_linux:10.2 | All versions | 0:24.02.0-7.el10_2.2 | | `poppler-glib-debuginfo` | Red Hat:enterprise_linux:10.2 | All versions | 0:24.02.0-7.el10_2.2 | | `poppler-glib-devel` | Red Hat:enterprise_linux:10.2 | All versions | 0:24.02.0-7.el10_2.2 | ## How do I fix CVE-2026-10118? Apply the vendor's patch. ## Is CVE-2026-10118 being exploited? There is no known exploitation of CVE-2026-10118 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-10118 and fix it if it is affected. What it is: CVE-2026-10118 is a high-severity vulnerability in Red Hat AI Inference Server 3.3, published on 1 Jun 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2026-10118 in the wild and no public exploit code. Affected product: Red Hat AI Inference Server 3.3. 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-10118/ (Markdown: https://insights.sbomify.com/CVE-2026-10118/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-10118 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-10118 - OSV: https://osv.dev/vulnerability/CVE-2026-10118 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-10118/ Summaries are generated and may contain mistakes; the official description above is the record.