dbcve.org
Hardened ImagesApplication · Redhat

CVE-2026-4775

HIGH · 7.8 CVSS v3.1 Published 2026-03-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A flaw was found in the libtiff library. A remote attacker could exploit a signed integer overflow vulnerability in the putcontig8bitYCbCr44tile function by providing a specially crafted TIFF file. This flaw can lead to an out-of-bounds heap write due to incorrect memory pointer calculations, potentially causing a denial of service (application crash) or arbitrary code execution.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A signed integer overflow vulnerability exists in the putcontig8bitYCbCr44tile function of libtiff. When processing a specially crafted TIFF file, the overflow causes incorrect memory pointer calculations, leading to an out-of-bounds heap write. This can result in denial of service via application crash or potentially allow arbitrary code execution.

MitigationUpgrade libtiff to the latest version containing the patch for this vulnerability. Implement input validation for TIFF files to reject files with potentially malicious YCbCr tile configurations that could trigger the overflow.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Hardened ImagesApplication
Affected:all versions
Debian LinuxOperating system
Affected:= 11.0
Enterprise LinuxOperating system
Affected:= 6.0= 7.0= 8.0= 9.0= 10.0
LibtiffApplication
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if libtiff library is installed
    Run 'dpkg -l libtiff*' on Debian/Ubuntu, 'rpm -qa | grep -i tiff' on RHEL/CentOS, or 'pkg-config --modversion tiff' to query the library version directly
    Affected if libtiff is installed and has a version that matches the affected product ranges (all versions of Libtiff are affected)
  2. Identify TIFF processing applications
    Search for binaries that link against libtiff using 'ldd $(which tiffinfo tiff2pdf tiffcrop 2>/dev/null)' or check common image processing tools that handle TIFF files
    Affected if Applications capable of processing TIFF files are present on the system
  3. Determine if YCbCr 4:4:4 TIFF processing occurs
    Inspect application logs or user workflows for TIFF file processing, particularly files that may use YCbCr color space with 4:4:4 subsampling (the putcontig8bitYCbCr44tile function handles this format)
    Affected if The system processes TIFF images using YCbCr 4:4:4 color representation, which triggers the vulnerable code path in putcontig8bitYCbCr44tile
  4. Check for crafted TIFF file ingestion points
    Review any network-facing services, upload mechanisms, or automated processing pipelines that accept TIFF input from untrusted sources
    Affected if Untrusted TIFF files can be submitted to any application using libtiff for image processing

If libtiff is installed and the system processes TIFF files (especially YCbCr 4:4:4 format) from potentially untrusted sources, the environment is affected by this vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade libtiff to the latest version containing the patch for this vulnerability. Implement input validation for TIFF files to reject files with potentially malicious YCbCr tile configurations that could trigger the overflow.

Fix this in Hardened Images Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-4775 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-4775 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data