CVE-2026-4775
Memory Safety in Redhat Enterprise Linux 10.0 … 9.0
Raw vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HSummary
CVE-2026-4775 is a high-severity Integer Overflow or Wraparound (CWE-190) vulnerability in Redhat Enterprise Linux. Its CVSS base score is 7.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 43th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-4775 is a signed integer overflow vulnerability in the libtiff library, specifically within the putcontig8bitYCbCr44tile function. Published on 2026-03-24, the flaw arises from incorrect memory pointer calculations when processing a specially crafted TIFF file, leading to an out-of-bounds heap write. Affected software includes applications and systems that rely on libtiff for TIFF image processing, such as image viewers, converters, or libraries in distributions like Red Hat and Debian. The vulnerability is classified under CWE-190 with a CVSS v3.1 base score of 7.8 (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H), indicating high impact potential.
A remote attacker can exploit this vulnerability by tricking a user into opening a malicious TIFF file with an affected libtiff-based application. The attack requires local access to execute the file but no privileges (PR:N) and involves user interaction (UI:R), such as clicking to view an image attachment. Successful exploitation could result in denial of service via application crash or arbitrary code execution, granting high confidentiality, integrity, and availability impacts.
Red Hat advisories RHSA-2026:12265, RHSA-2026:12271, and the CVE security page detail patches for affected libtiff versions in Red Hat Enterprise Linux. Debian LTS announcement from April 2026 addresses the issue in their long-term support packages. Security practitioners should update libtiff libraries via these errata and vendor channels, validate TIFF inputs, and consider sandboxing image processing applications to mitigate risks.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-14901
Vulnerability Data
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…
more
incorrect memory pointer calculations, potentially causing a denial of service (application crash) or arbitrary code execution.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V5.2.6
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation (static analysis, fuzzing, unit tests) directly finds integer overflow defects before deployment.
Secure engineering principles require use of safe arithmetic constructs or language features that structurally eliminate integer overflow during calculation.
Input validation enforces bounds on values before arithmetic, stopping the conditions that trigger overflow or wraparound.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require use of safe arithmetic, bounds checks, and testing that prevent integer overflows.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development can detect integer overflows before release.
Secure SDLC mandates input validation and arithmetic checks that prevent integer overflows.
Application security requirements include bounds checking and safe arithmetic to avoid overflow conditions.
Secure architecture principles require defensive coding patterns that mitigate integer wraparound risks.
Secure coding standards explicitly forbid unsafe integer operations and mandate overflow-safe constructs.