CVE-2025-57812VulnerabilityPublished 12 Nov 2025

CVE-2025-57812: OpenPrinting libcupsfilters · Out-of-bounds Read

Affects OpenPrinting libcupsfiltersSource CVE Database V5

Not known to be exploited · CVSS 3.7 Low : upgrade to 2.1.1 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

3.7Low

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 2.1.1

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

Attack Vector: Adjacent
Attack Complexity: High
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Adjacent: The vulnerable component is bound to the network stack, but the attack is limited at the protocol level to a logically adjacent topology. This can mean an attack must be launched from the same shared physical (e.g., Bluetooth or IEEE 802.11) or logical (e.g., local IP subnet) network, or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN to an administrative network zone).
Attack Complexity: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 12 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade openprinting/libcupsfilters to 2.1.1.

Affected software

Product	Affected	Fixed in
GitHubopenprinting/libcupsfilters`pkg:github/openprinting/libcupsfilters`Other threats	Affected <2.1.1	Fixed in 2.1.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should immediately identify all printing systems and servers running affected versions of CUPS-Filters (<=1.28.17) or libcupsfilters (>=2.0.0 and <2.1.1). Apply the official patches or upgrade to libcupsfilters 2.1.1 or later where the vulnerability is fixed. Where patching is delayed, restrict network access to printing services to trusted hosts only and implement network segmentation to isolate printers from untrusted networks. Monitor print job logs for unusual TIFF files or abnormal print job options that could indicate exploitation attempts. Employ intrusion detection systems with signatures targeting malformed TIFF files or suspicious print job parameters. Disable or limit the use of the imagetoraster filter if not required by the printing workflow. Educate IT staff on the risks associated with print job processing vulnerabilities and ensure print servers run with the least privileges necessary. Regularly audit and update printer firmware and associated software to maintain security hygiene.

Description

CUPS is a standards-based, open-source printing system, and `libcupsfilters` contains the code of the filters of the former `cups-filters` package as library functions to be used for the data format conversion tasks needed in Printer Applications. In CUPS-Filters versions up to and including 1.28.17 and libscupsfilters versions 2.0.0 through 2.1.1, CUPS-Filters's `imagetoraster` filter has an out of bounds read/write vulnerability in the processing of TIFF image files. While the pixel buffer is allocated with the number of pixels times a pre-calculated bytes-per-pixel value, the function which processes these pixels is called with a size of the number of pixels times 3. When suitable inputs are passed, the bytes-per-pixel value can be set to 1 and bytes outside of the buffer bounds get processed. In order to trigger the bug, an attacker must issue a print job with a crafted TIFF file, and pass appropriate print job options to control the bytes-per-pixel value of the output format. They must choose a printer configuration under which the `imagetoraster` filter or its C-function equivalent `cfFilterImageToRaster()` gets invoked. The vulnerability exists in both CUPS-Filters 1.x and the successor library libcupsfilters (CUPS-Filters 2.x). In CUPS-Filters 2.x, the vulnerable function is `_cfImageReadTIFF() in libcupsfilters`. When this function is invoked as part of `cfFilterImageToRaster()`, the caller passes a look-up-table during whose processing the out of bounds memory access happens. In CUPS-Filters 1.x, the equivalent functions are all found in the cups-filters repository, which is not split into subprojects yet, and the vulnerable code is in `_cupsImageReadTIFF()`, which is called through `cupsImageOpen()` from the `imagetoraster` tool. A patch is available in commit b69dfacec7f176281782e2f7ac44f04bf9633cfa.

Impact

For European organizations, this vulnerability primarily threatens the confidentiality and integrity of data processed by networked printing services using vulnerable versions of CUPS-Filters or libcupsfilters. Attackers with network access to printers can submit malicious print jobs containing crafted TIFF files to exploit the vulnerability, potentially leading to unauthorized memory reads or writes. This could result in leakage of sensitive information processed during printing or corruption of print jobs, undermining data integrity. While the vulnerability does not directly impact system availability, exploitation could be a foothold for further attacks or information gathering. Organizations with extensive printing infrastructure, especially those in sectors handling sensitive documents such as government, finance, healthcare, and legal services, are at higher risk. The low CVSS score indicates limited impact scope, but the ubiquity of CUPS in Linux-based systems and network printers in European enterprises means the exposure is non-negligible. Additionally, the lack of known exploits suggests a window of opportunity for proactive mitigation before active exploitation occurs.

Summary

CVE-2025-57812 is a vulnerability classified under CWE-125 (Out-of-bounds Read) and CWE-787 (Out-of-bounds Write) affecting the imagetoraster filter component within the CUPS-Filters package and its successor library libcupsfilters. CUPS is a widely used open-source printing system, and libcupsfilters provides data format conversion functions essential for printer applications. The flaw arises in the processing of TIFF image files where the pixel buffer allocation is based on the number of pixels multiplied by a pre-calculated bytes-per-pixel value. However, the processing function is called with a size calculated as the number of pixels times three bytes, leading to out-of-bounds memory access when the bytes-per-pixel value is set to one. This discrepancy allows reading or writing beyond the allocated buffer. To exploit this, an attacker must submit a print job containing a specially crafted TIFF file and specify print job options that influence the bytes-per-pixel parameter. The vulnerability exists in CUPS-Filters versions up to 1.28.17 and libcupsfilters versions from 2.0.0 up to but not including 2.1.1. The vulnerable functions are _cupsImageReadTIFF() in CUPS-Filters 1.x and _cfImageReadTIFF() in libcupsfilters 2.x, invoked through imagetoraster or cfFilterImageToRaster() respectively. The attack surface is limited to printer configurations that invoke these filters. A patch addressing this issue has been committed, but no public exploits are known. The CVSS v3.1 score is 3.7, reflecting low severity due to the attack vector requiring local network access, low privileges, and high attack complexity without user interaction, with limited confidentiality and integrity impact and no availability impact.

CWE-125Out-of-bounds Read (opens in a new tab)
Base weaknessCWE Top 25 (2025): #8
The product reads data past the end, or before the beginning, of the intended buffer.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Architecture and Design · Language Selection
Use a language that provides appropriate memory abstractions.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
Attack patterns
Overread Buffers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-787Out-of-bounds Write (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #5
The product writes data past the end, or before the beginning, of the intended buffer.
Requirements · Language Selection
Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Operation · Build and Compilation · Environment Hardening
Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index…
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 19 Nov 2025, 19:05 UTC

WeaknessesCWE-125, CWE-787

Technical details

References

Community reviews

Related threats