CVE-2026-12912: libtiff PixarLog Heap Buffer Overflow Vulnerability Analysis
A vulnerability in libtiff, a widely-used image processing library, allows a local attacker to trigger a heap-based buffer overflow by opening a specially crafted TIFF image file with PixarLog compression. The flaw surfaces specifically when the decoder processes images using the 8-bit ABGR output format combined with a particular stride configuration. An attacker with local file access could potentially execute arbitrary code on the system or crash the application handling the image.
Source data · NVD / CISA · public domain
- CVSS
- 3.1 · 7.3 HIGH · CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
- Weaknesses (CWE)
- CWE-122
- Affected products
- 0 configuration(s)
- Published / Modified
- 2026-06-29 / 2026-08-06
NVD description (verbatim)
A flaw was found in libtiff. A remote attacker could exploit this vulnerability by providing a specially crafted PixarLog-compressed TIFF image. This issue occurs when decoding Pixarlog codec images with the PIXARLOGDATAFMT_8BITABGR output format and a specific stride value, leading to a heap-based buffer overflow. This could potentially result in arbitrary code execution or a denial of service (DoS).
21 reference(s) · View on NVD →
SEC.co analysis · AI-assisted, reviewed against source
Technical summary
CVE-2026-12912 is a heap-based buffer overflow (CWE-122) in libtiff's PixarLog codec decoder. The vulnerability manifests during the decompression of TIFF images encoded with PixarLog compression when the decoder is configured with PIXARLOGDATAFMT_8BITABGR output format and a specific stride value. The insufficient bounds checking during decompression allows out-of-bounds memory writes, enabling code execution or denial of service. The attack vector is local with low attack complexity, requiring user interaction to open a malicious image file.
Business impact
Organizations relying on libtiff for image processing—including document management systems, content management platforms, and image editing tools—face operational risk. A successful exploit could lead to unauthorized code execution on systems processing untrusted TIFF images, potentially enabling lateral movement, data exfiltration, or system compromise. Denial-of-service attacks could disrupt image processing workflows. Systems processing user-supplied images are at highest risk.
Affected systems
Any application statically or dynamically linked against vulnerable versions of libtiff is potentially affected. This includes image viewers, web services handling TIFF uploads, document conversion utilities, and embedded systems using libtiff. The vulnerability requires local access to trigger, narrowing the attack surface to scenarios where users open files from untrusted sources or systems accept file uploads. Verify your libtiff version against the vendor advisory to confirm applicability.
Exploitability
The vulnerability requires local access and user interaction to exploit—an attacker must convince a user to open a malicious TIFF file or upload it to a vulnerable service. The low attack complexity suggests exploitation is straightforward once a user interacts with the payload. While not remotely exploitable, the widespread use of libtiff and commonality of TIFF file handling make this a practical threat in environments where users handle images from external sources or where applications auto-process uploaded files.
Remediation
Update libtiff to a patched version released by the libtiff project. Consult the official libtiff security advisory for the specific patch version addressing CVE-2026-12912. Organizations should prioritize patching systems that process untrusted TIFF images, including web services, document management platforms, and user-facing image tools. Where immediate patching is not feasible, restrict file upload functionality or implement sandboxing for image processing.
Patch guidance
Apply the security update provided by the libtiff project corresponding to this CVE. Verify the patch version against the official libtiff advisory and release notes. Test patches in a non-production environment before enterprise deployment to ensure compatibility with dependent applications. Monitor libtiff's repository and security mailing list for patch availability. For distributions packaging libtiff (Linux vendors, package managers), check for updated packages from your provider.
Detection guidance
Monitor system logs for crashes or unexpected termination of applications processing TIFF files, which may indicate exploitation attempts. Implement file type validation and rejection of suspicious TIFF structures at upload points. Network-based detection is limited due to the local-only attack vector, but monitoring for unusual process execution following TIFF file handling may reveal successful exploitation. Consider deploying application sandboxing or memory protection mechanisms on systems processing user-supplied images.
Why prioritize this
While the local-only attack vector limits immediate Internet-facing risk, the HIGH CVSS score (7.3) reflects the severity of potential impact—code execution with full system privileges. Organizations should prioritize based on exposure: systems handling untrusted TIFF uploads or user-driven image processing are critical; internal-only systems using libtiff for trusted content are lower priority. The widespread deployment of libtiff and prevalence of TIFF handling in enterprise workflows justify urgent patching where exposure exists.
Risk score, explained
The CVSS 3.1 score of 7.3 (HIGH) reflects the combination of high confidentiality, integrity, and availability impact (code execution capability) balanced against the local-only attack vector and requirement for user interaction. The score appropriately captures the real-world threat: while not immediately exploitable via network attack, successful exploitation grants full system compromise. Organizations processing untrusted images should treat this as a HIGH-priority vulnerability.
Frequently asked questions
Can this vulnerability be exploited remotely over the network?
No. The attack vector is strictly local, requiring an attacker to place a malicious TIFF file on the target system or trick a user into opening one. However, web applications that accept TIFF uploads and process them server-side can be compromised if running vulnerable libtiff versions.
What applications should I check for this vulnerability?
Any application or service using libtiff is potentially affected. Common examples include image viewers, document converters, web upload handlers, photography software, and graphics applications. Check vendor documentation or use dependency scanning tools to identify libtiff usage in your environment.
Is there a workaround if I cannot patch immediately?
Mitigations include disabling TIFF file upload or processing capabilities, restricting access to TIFF files to trusted sources only, implementing application sandboxing, and running vulnerable services with minimal privileges. However, these are temporary measures—patching remains the definitive solution.
Does this vulnerability appear on the CISA KEV catalog?
No, this CVE is not currently listed on the CISA Known Exploited Vulnerabilities catalog, indicating no evidence of active exploitation in the wild at this time. However, organizations should not delay patching based on KEV status alone.
This analysis is provided for informational purposes to assist security professionals in understanding and remediating CVE-2026-12912. The vulnerability details, CVSS scoring, and CWE classification are based on official CVE and NVD records published as of the modification date. Organizations must verify patch availability and compatibility against official vendor advisories before deployment. This explainer does not constitute security advice specific to your environment; consult your security team and vendor guidance for implementation decisions. No active exploits or proof-of-concept code are provided. All remediation efforts should be tested in non-production environments before enterprise rollout. Source: NVD (public-domain), retrieved 2026-08-08. Analysis generated by SEC.co (claude-haiku-4-5).
Weaknesses (CWE)
Related vulnerabilities
- CVE-2023-43688HIGHMalwarebytes Heap Buffer Overflow Denial of Service Vulnerability
- CVE-2026-0059HIGHAndroid Heap Buffer Overflow in SDP Discovery – Remote Code Execution
- CVE-2026-0100HIGHAndroid Heap Buffer Overflow Local Privilege Escalation
- CVE-2026-0132HIGHAndroid Modem Heap Buffer Overflow - RCE Vulnerability
- CVE-2026-0149HIGHAndroid RTP Heap Buffer Overflow Leading to Remote Code Execution
- CVE-2026-10929HIGHChrome Android Heap Buffer Overflow & Sandbox Escape Vulnerability
- CVE-2026-10946HIGHChrome Heap Buffer Overflow in Media Processing—Patch Guidance
- CVE-2026-10949HIGHChrome Heap Overflow Sandbox Escape Vulnerability