Freedesktop Poppler 26.07.0 SampledFunction poppler/Function.cc BitsPerSample integer overflow
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.9 | $0-$5k | 1.41- |
Summary
A vulnerability was found in Freedesktop Poppler 26.07.0. It has been rated as problematic. Impacted is the function SampledFunction::SampledFunction of the file poppler/Function.cc of the component SampledFunction. This manipulation of the argument BitsPerSample causes integer overflow.
The identification of this vulnerability is CVE-2026-93311. It is possible to initiate the attack remotely. Furthermore, there is an exploit available.
The project was informed of the problem early through a bug report but has not responded yet.
Details
A vulnerability was found in Freedesktop Poppler 26.07.0. It has been declared as problematic. Affected by this vulnerability is the function SampledFunction::SampledFunction of the file poppler/Function.cc of the component SampledFunction. The manipulation of the argument BitsPerSample with an unknown input leads to a integer overflow vulnerability. The CWE definition for the vulnerability is CWE-190. The product performs a calculation that can produce an integer overflow or wraparound, when the logic assumes that the resulting value will always be larger than the original value. This can introduce other weaknesses when the calculation is used for resource management or execution control. As an impact it is known to affect availability.
The advisory is shared at gitlab.freedesktop.org. This vulnerability is known as CVE-2026-93311. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. Technical details and also a public exploit are known.
It is possible to download the exploit at github.com. It is declared as proof-of-concept. The project was informed of the problem early through a bug report but has not responded yet.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 3.9
VulDB Base Score: 4.3
VulDB Temp Score: 3.9
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Integer overflowCWE: CWE-190 / CWE-189
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
09/17/2026 Advisory disclosed09/17/2026 VulDB entry created
09/17/2026 VulDB entry last update
Sources
Advisory: 1758Status: Not defined
CVE: CVE-2026-93311 (🔒)
GCVE (CVE): GCVE-0-2026-93311
GCVE (VulDB): GCVE-100-406609
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 09/17/2026 19:18Changes: 09/17/2026 19:18 (59)
Complete: 🔍
Submitter: r1ck99
Cache ID: 216::103
Submit
Accepted
- Submit #942344: freedesktop.org Poppler 26.07.0 Integer Overflow (by r1ck99)
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.