CVE-2026-12912 Libtiff: libtiff: heap-based buffer overflow via crafted pixarlog-compressed tiff image
High 7.3
Published
Updated
Check this codebase for CVE-2026-12912 and fix it if it is affected.
What it is: CVE-2026-12912 is a high-severity memory corruption vulnerability in Red Hat Enterprise Linux 10, published on 29 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-12912 in the wild and no public exploit code.
Affected product: Red Hat Enterprise Linux 10. 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-12912/ (Markdown: https://insights.sbomify.com/CVE-2026-12912/index.md)
A heap-based buffer overflow in Libtiff allows remote attackers to execute arbitrary code or cause denial of service via crafted TIFF images.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Local or same network only
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2026-12912?
CVE-2026-12912 is a high-severity memory corruption vulnerability in Red Hat Enterprise Linux 10, published on 29 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 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).
Weakness: CWE-122
Which versions are affected by CVE-2026-12912?
Linux distribution packages (40)
compat-libtiff3 AlmaLinux:8 | All versions | 3.9.4-16.el8_10 |
libtiff AlmaLinux:8 | All versions | 4.0.9-38.el8_10 |
libtiff-devel AlmaLinux:8 | All versions | 4.0.9-38.el8_10 |
libtiff-tools AlmaLinux:8 | All versions | 4.0.9-38.el8_10 |
libtiff AlmaLinux:9 | All versions | 4.4.0-18.el9_8.1 |
libtiff-devel AlmaLinux:9 | All versions | 4.4.0-18.el9_8.1 |
libtiff-tools AlmaLinux:9 | All versions | 4.4.0-18.el9_8.1 |
compat-libtiff3 Red Hat:enterprise_linux:8::appstream | All versions | 0:3.9.4-16.el8_10 |
compat-libtiff3-debuginfo Red Hat:enterprise_linux:8::appstream | All versions | 0:3.9.4-16.el8_10 |
compat-libtiff3-debugsource Red Hat:enterprise_linux:8::appstream | All versions | 0:3.9.4-16.el8_10 |
libtiff Red Hat:enterprise_linux:8::appstream | All versions | 0:4.0.9-38.el8_10 |
libtiff-debuginfo Red Hat:enterprise_linux:8::appstream | All versions | 0:4.0.9-38.el8_10 |
libtiff-debugsource Red Hat:enterprise_linux:8::appstream | All versions | 0:4.0.9-38.el8_10 |
libtiff-devel Red Hat:enterprise_linux:8::appstream | All versions | 0:4.0.9-38.el8_10 |
libtiff-tools-debuginfo Red Hat:enterprise_linux:8::appstream | All versions | 0:4.0.9-38.el8_10 |
libtiff-debuginfo Red Hat:enterprise_linux:8::crb | All versions | 0:4.0.9-38.el8_10 |
libtiff-debugsource Red Hat:enterprise_linux:8::crb | All versions | 0:4.0.9-38.el8_10 |
libtiff-tools Red Hat:enterprise_linux:8::crb | All versions | 0:4.0.9-38.el8_10 |
libtiff-tools-debuginfo Red Hat:enterprise_linux:8::crb | All versions | 0:4.0.9-38.el8_10 |
libtiff Red Hat:enterprise_linux:9::appstream | All versions | 0:4.4.0-18.el9_8.1 |
libtiff-debuginfo Red Hat:enterprise_linux:9::appstream | All versions | 0:4.4.0-18.el9_8.1 |
libtiff-debugsource Red Hat:enterprise_linux:9::appstream | All versions | 0:4.4.0-18.el9_8.1 |
libtiff-devel Red Hat:enterprise_linux:9::appstream | All versions | 0:4.4.0-18.el9_8.1 |
libtiff-tools-debuginfo Red Hat:enterprise_linux:9::appstream | All versions | 0:4.4.0-18.el9_8.1 |
libtiff-debuginfo Red Hat:enterprise_linux:9::crb | All versions | 0:4.4.0-18.el9_8.1 |
libtiff-debugsource Red Hat:enterprise_linux:9::crb | All versions | 0:4.4.0-18.el9_8.1 |
libtiff-tools Red Hat:enterprise_linux:9::crb | All versions | 0:4.4.0-18.el9_8.1 |
libtiff-tools-debuginfo Red Hat:enterprise_linux:9::crb | All versions | 0:4.4.0-18.el9_8.1 |
libtiff Red Hat:hummingbird:1 | All versions | 0:4.7.1-2.4.hum1 |
libtiff-devel Red Hat:hummingbird:1 | All versions | 0:4.7.1-2.4.hum1 |
libtiff-static Red Hat:hummingbird:1 | All versions | 0:4.7.1-2.4.hum1 |
libtiff-tools Red Hat:hummingbird:1 | All versions | 0:4.7.1-2.4.hum1 |
compat-libtiff3 Red Hat:rhel_aus:8.4::appstream | All versions | 0:3.9.4-13.el8_4.3 |
libtiff Red Hat:rhel_aus:8.4::appstream | All versions | 0:4.0.9-18.el8_4.3 |
libtiff-debuginfo Red Hat:rhel_aus:8.4::appstream | All versions | 0:4.0.9-18.el8_4.3 |
libtiff-debugsource Red Hat:rhel_aus:8.4::appstream | All versions | 0:4.0.9-18.el8_4.3 |
libtiff-devel Red Hat:rhel_aus:8.4::appstream | All versions | 0:4.0.9-18.el8_4.3 |
libtiff-tools-debuginfo Red Hat:rhel_aus:8.4::appstream | All versions | 0:4.0.9-18.el8_4.3 |
compat-libtiff3 Red Hat:rhel_aus:8.6::appstream | All versions | 0:3.9.4-13.el8_6.3 |
libtiff Red Hat:rhel_aus:8.6::appstream | All versions | 0:4.0.9-21.el8_6.3 |
How do I fix CVE-2026-12912?
Apply the vendor's patch.
Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.
Is CVE-2026-12912 being exploited?
There is no known exploitation of CVE-2026-12912 in the wild and no public exploit code.
Sources
Also known as ALSA-2026:42668, ALSA-2026:47183, ALSA-2026:47184, AZL-91685, AZL-91688, AZL-91722 and 34 more.