CVE-2026-4775: libtiff: integer overflow causes heap OOB write

HIGH
Published March 24, 2026
CISO Take

A signed integer overflow in libtiff's putcontig8bitYCbCr44tile function lets a specially crafted TIFF file corrupt heap memory via incorrect pointer math, leading to a crash or potentially arbitrary code execution. This matters because libtiff sits quietly inside 129 downstream packages and, critically, inside Red Hat's AI Inference Server images (rhaiis/vllm-cuda-rhel9, vllm-rocm-rhel9, vllm-spyre-rhel9) — meaning any vision or multimodal inference stack built on those containers inherits the flaw whenever it decodes TIFF images. The actual urgency is moderate: EPSS sits at 0.55% (top 58th percentile), it's not in CISA KEV, there's no public exploit or Nuclei template, and CISA's SSVC decision is TRACK rather than Act. The attack vector is local with required user interaction, so exploitation needs a malicious file to be opened or auto-processed by an image pipeline rather than a bare network hit. Patch libtiff to the fixed version referenced in the RHSA errata (RHSA-2026:12265 and related), rebuild any custom rhaiis/vllm containers from patched base images, and if TIFF ingestion isn't required by your inference or RAG pipeline, disable it or restrict decoding to a sandboxed, resource-limited process.

Sources: NVD EPSS ATLAS access.redhat.com

What is the risk?

CVSS 7.8 (high) reflects severe confidentiality/integrity/availability impact if triggered, but real-world exploitation likelihood is currently low: EPSS is only 0.55% (top 58% percentile, not top-tier), no KEV listing, no public exploit code, and SSVC is TRACK (monitor, not urgent action). The local attack vector plus required user interaction narrows the practical attack surface to scenarios where a crafted TIFF is opened locally or auto-processed by an application — which is exactly the pattern seen in AI image-ingestion services. The 129 downstream dependents and 74 historical CVEs in libtiff indicate a large, recurring attack surface that's worth tracking even at TRACK-level urgency, especially given its direct presence in RHEL AI Inference Server multimodal images.

How does the attack unfold?

Craft malicious TIFF
Adversary builds a TIFF file with manipulated tile/YCbCr parameters designed to trigger the signed integer overflow in putcontig8bitYCbCr44tile.
Delivery via upload/execution
The file is submitted through an image/document upload channel to a RAG or vision-model inference pipeline, or opened locally by a user/admin tool linking libtiff.
AML.T0011
Heap corruption
The overflow causes an out-of-bounds heap write due to incorrect pointer calculations during TIFF decoding.
Impact: DoS or code execution
The corrupted memory crashes the inference/decoding worker or, in a more advanced exploit, enables arbitrary code execution on the host.
AML.T0029

What systems are affected?

Package Ecosystem Vulnerable Range Patched
vLLM pip No patch
89.1K 128 dependents Pushed 2d ago 24% patched ~49d to patch Full package profile →
vLLM pip No patch
89.1K 128 dependents Pushed 2d ago 24% patched ~49d to patch Full package profile →
vLLM pip No patch
89.1K 128 dependents Pushed 2d ago 24% patched ~49d to patch Full package profile →
compat-libtiff3 No patch
libtiff No patch
libtiff-main No patch
mingw-libtiff No patch
rhaiis/model-opt-cuda-rhel9 No patch

How severe is it?

CVSS 3.1
7.8 / 10
EPSS
0.6%
chance of exploitation in 30 days
Higher than 44% of all CVEs
Exploitation Status
No known exploitation
Sophistication
Moderate

What is the attack surface?

AV AC PR UI S C I A
AV Local
AC Low
PR None
UI Required
S Unchanged
C High
I High
A High

What should I do?

1 step
  1. 1) Patch libtiff to the version fixed in the referenced Red Hat errata (RHSA-2026:12265, 12271, 14929, 16055, 19150, 19363, 19585/86, 19604/08) across all affected packages, including compat-libtiff3 and mingw-libtiff builds. 2) Rebuild and redeploy any rhaiis/vllm-cuda-rhel9, vllm-rocm-rhel9, or vllm-spyre-rhel9 container images from the patched base rather than patching in place. 3) If your inference or RAG pipeline doesn't need TIFF support, strip or disable TIFF decoding entirely to eliminate the attack surface. 4) Where TIFF decoding is required, isolate it in a sandboxed/seccomp-restricted worker process with memory limits so a crash doesn't take down the whole inference service. 5) Detection: monitor image-decoding worker crash logs and core dumps for anomalous heap corruption signatures following TIFF uploads, and flag repeated malformed-TIFF submissions to the same endpoint as reconnaissance/exploitation attempts.

What does CISA's SSVC say?

Decision Track
Exploitation none
Automatable No
Technical Impact total

Source: CISA Vulnrichment (SSVC v2.0). Decision based on the CISA Coordinator decision tree.

How is it classified?

Which compliance frameworks are affected?

This CVE is relevant to:

EU AI Act
Article 15 - Accuracy, robustness and cybersecurity
ISO 42001
A.6.2.3 - Third-party and supplier requirements
NIST AI RMF
MAP 3.4 - Third-party resources and dependencies mapped and monitored
OWASP LLM Top 10
LLM03 - Supply Chain Vulnerabilities

Frequently Asked Questions

What is CVE-2026-4775?

A signed integer overflow in libtiff's putcontig8bitYCbCr44tile function lets a specially crafted TIFF file corrupt heap memory via incorrect pointer math, leading to a crash or potentially arbitrary code execution. This matters because libtiff sits quietly inside 129 downstream packages and, critically, inside Red Hat's AI Inference Server images (rhaiis/vllm-cuda-rhel9, vllm-rocm-rhel9, vllm-spyre-rhel9) — meaning any vision or multimodal inference stack built on those containers inherits the flaw whenever it decodes TIFF images. The actual urgency is moderate: EPSS sits at 0.55% (top 58th percentile), it's not in CISA KEV, there's no public exploit or Nuclei template, and CISA's SSVC decision is TRACK rather than Act. The attack vector is local with required user interaction, so exploitation needs a malicious file to be opened or auto-processed by an image pipeline rather than a bare network hit. Patch libtiff to the fixed version referenced in the RHSA errata (RHSA-2026:12265 and related), rebuild any custom rhaiis/vllm containers from patched base images, and if TIFF ingestion isn't required by your inference or RAG pipeline, disable it or restrict decoding to a sandboxed, resource-limited process.

Is CVE-2026-4775 actively exploited?

No confirmed active exploitation of CVE-2026-4775 has been reported, but organizations should still patch proactively.

How to fix CVE-2026-4775?

1) Patch libtiff to the version fixed in the referenced Red Hat errata (RHSA-2026:12265, 12271, 14929, 16055, 19150, 19363, 19585/86, 19604/08) across all affected packages, including compat-libtiff3 and mingw-libtiff builds. 2) Rebuild and redeploy any rhaiis/vllm-cuda-rhel9, vllm-rocm-rhel9, or vllm-spyre-rhel9 container images from the patched base rather than patching in place. 3) If your inference or RAG pipeline doesn't need TIFF support, strip or disable TIFF decoding entirely to eliminate the attack surface. 4) Where TIFF decoding is required, isolate it in a sandboxed/seccomp-restricted worker process with memory limits so a crash doesn't take down the whole inference service. 5) Detection: monitor image-decoding worker crash logs and core dumps for anomalous heap corruption signatures following TIFF uploads, and flag repeated malformed-TIFF submissions to the same endpoint as reconnaissance/exploitation attempts.

What systems are affected by CVE-2026-4775?

This vulnerability affects the following AI/ML architecture patterns: model serving, RAG pipelines, vision-language multimodal inference, data preprocessing pipelines.

What is the CVSS score for CVE-2026-4775?

CVE-2026-4775 has a CVSS v3.1 base score of 7.8 (HIGH). The EPSS exploitation probability is 0.55%.

What is the AI security impact?

Affected AI Architectures

model servingRAG pipelinesvision-language multimodal inferencedata preprocessing pipelines

MITRE ATLAS Techniques

AML.T0010.001 AI Software
AML.T0011 User Execution
AML.T0029 Denial of AI Service

Compliance Controls Affected

EU AI Act: Article 15
ISO 42001: A.6.2.3
NIST AI RMF: MAP 3.4
OWASP LLM Top 10: LLM03

What are the technical details?

Original Advisory

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.

Exploitation Scenario

An adversary crafts a TIFF file with manipulated tile dimensions/YCbCr subsampling parameters designed to trigger the signed integer overflow in putcontig8bitYCbCr44tile. They submit this file through a document or image upload channel feeding a RAG ingestion pipeline or a vision-language model inference endpoint (e.g., a vLLM multimodal API running on a vulnerable rhaiis image) that automatically decodes TIFF thumbnails for preview or embedding generation. When the vulnerable code path processes the file, the overflow miscalculates a memory offset, causing an out-of-bounds heap write — crashing the inference worker (denial of service) or, in a more advanced exploitation chain, corrupting adjacent heap structures to achieve code execution on the inference host.

Weaknesses (CWE)

CWE-190 — Integer Overflow or Wraparound: The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.

  • [Requirements] Ensure that all protocols are strictly defined, such that all out-of-bounds behavior can be identified simply, and require strict conformance to the protocol.
  • [Requirements] Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. If possible, choose a language or compiler that performs automatic bounds checking.

Source: MITRE CWE corpus.

CVSS Vector

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

References

Timeline

Published
March 24, 2026
Last Modified
July 15, 2026
First Seen
June 27, 2026

Related Vulnerabilities