cve.bz

CVE-2026-52490 Code Injection

9.8 criticalEPSS 0.5%

Critical (9.8). EPSS 0.5% estimated probability of exploitation activity in the next 30 days.

On this page
An issue in libtiff 85f2ac8e0b01cb7db2bbecf4a3b891bdbef67938 allows an attacker to execute arbitrary code via the process_command_opts() function in tools/tiffcrop.c

Severity

CVSS 3.1

9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
0.5% (down from 0.7% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 44th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: yes · Technical impact: total, assessed 2026-08-25. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-94 Improper Control of Generation of Code (Code Injection)
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-52490 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-52490?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-52490?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-52490 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13tiffno fix listedDEBIAN-CVE-2026-52490
Debian14tiff4.7.2-1DEBIAN-CVE-2026-52490
Red Hatenterprise_linux:8::appstreamlibtiff, libtiff-devel, libtiff-debuginfo and 2 more0:4.0.9-39.el8_10RHSA-2026:69095
Red Hatenterprise_linux:8::crblibtiff-tools, libtiff-debuginfo, libtiff-debugsource and 1 more0:4.0.9-39.el8_10RHSA-2026:69095
Red Hathummingbird:1libtiff, libtiff-devel, libtiff-tools and 1 more0:4.7.2-2.hum1RHSA-2026:53467
Red Hatrhel_els:7libtiff, libtiff-devel, libtiff-tools and 2 more0:4.0.3-35.el7_9.4RHSA-2026:99062
AlmaLinux8libtiff, libtiff-devel, libtiff-tools4.0.9-39.el8_10ALSA-2026:69095
Rocky Linux8libtiff0:4.0.9-39.el8_10RLSA-2026:69095
Alpaquita23tiff4.4.0-r7BELL-CVE-2026-52490
Alpaquita25tiff4.7.1-r1BELL-CVE-2026-52490
Alpaquitastreamtiff4.7.2-r0BELL-CVE-2026-52490
BellSoft Hardened Containers23tiff4.4.0-r7BELL-CVE-2026-52490
BellSoft Hardened Containers25tiff4.7.1-r1BELL-CVE-2026-52490
BellSoft Hardened Containersstreamtiff4.7.2-r0BELL-CVE-2026-52490

From the distributions' data via OSV.dev: the Debian Security Tracker; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; AlmaLinux's OSV database, MIT; Rocky Linux's errata, BSD-3-Clause; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Red Hat · Alpaquita · BellSoft Hardened Containers.

Red Hat

Red Hat rates this Important.

Red Hat's statement

Red Hat has classified this flaw as Important rather than Moderate because an attacker who convinces a user or automated process to run the utility with crafted arguments could execute arbitrary instructions in the security context of the invoking account. This issue is isolated to the standalone tiffcrop binary and does not reside in the core libtiff shared library, meaning third-party software and background system daemons dynamically linked against libtiff remain unaffected. Exploitation requires specific invocation of the CLI tool with malicious command-line options, significantly limiting direct exposure in standard server deployments where the utility is not integrated into automated pipelines.

Red Hat's mitigation

Avoid using the `tiffcrop` utility to process TIFF image files from untrusted sources. If the `libtiff-tools` package, which provides `tiffcrop`, is not required, consider removing it to prevent exploitation.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 8libtiff-0:4.0.9-39.el8_10Fixed 2026-09-21RHSA-2026:69095
Red Hat Hardened Imageslibtiff-main-4.7.2-2.hum1Fixed 2026-08-11RHSA-2026:53467
Red Hat Enterprise Linux 10libtiffNot affected
Red Hat Enterprise Linux 6libtiffOut of support scope
Red Hat Enterprise Linux 7compat-libtiff3Not affected
Red Hat Enterprise Linux 7libtiffAffected
Red Hat Enterprise Linux 8compat-libtiff3Not affected
Red Hat Enterprise Linux 8mingw-libtiffAffected
Red Hat Enterprise Linux 9libtiffNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-52490.

Attack patterns (CAPEC)

  • CAPEC-35 Leverage Executable Code in Non-Executable Files Likelihood: High · Severity: Very High
  • CAPEC-77 Manipulating User-Controlled Variables Likelihood: High · Severity: Very High
  • CAPEC-242 Code Injection Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON