dbcve.org
Integer OverflowWeakness · CWE-190

CVE-2026-10118

HIGH · 7.8 CVSS v3.1 Published 2026-06-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Integer overflow in Poppler's Splash backend 'tilingPatternFill' function allows a maliciously crafted PDF to allocate undersized heap memory, leading to an out-of-bounds write and potential code execution, information disclosure, or denial of service.

MitigationUpdate Poppler to the patched version when available. Process untrusted PDFs in sandboxed environments with limited privileges to reduce exploitation impact.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Poppler is installed
    Run 'poppler-config --version' or 'pdftotext -v' to check if Poppler utilities are present on the system
    Affected if Poppler is not installed - the system is not vulnerable to this specific flaw
  2. Identify installed Poppler version
    Execute 'poppler-config --version' to obtain the exact version number, then compare against the version that contains the fix for CVE-2026-10118
    Affected if Installed version is older than the fixed version - the integer overflow vulnerability exists in the Splash backend
  3. Confirm PDF processing with Poppler
    Review running services or applications that use Poppler library (such as PDF viewers, converters, or document processing tools) to see if they handle PDF files
    Affected if Applications process PDF files through Poppler - this is the attack vector for the tilingPatternFill flaw
  4. Check if Splash output device is in use
    Examine application configuration or code that specifies the output device for PDF rendering; look for 'splash' or Splash-related backend settings
    Affected if Splash backend is configured as the rendering output device - the tilingPatternFill function is the vulnerable component

The environment is affected if Poppler is installed with a version prior to the fix, AND PDF files are being processed using the Splash backend, as the integer overflow in tilingPatternFill requires both conditions to be exploitable.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Poppler to the patched version when available. Process untrusted PDFs in sandboxed environments with limited privileges to reduce exploitation impact.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-10118 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-10118 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data