CVE-2026-70653
Description
A flaw was found in libvips. A heap-based buffer read overflow vulnerability exists in the old-style Radiance RLE decoder. A remote attacker could exploit this by providing a specially crafted Radiance image. This could lead to the disclosure of four bytes of adjacent heap data, potentially revealing sensitive image information.
Statement
This issue is a local out-of-bounds read of four bytes of adjacent heap data in libvips when decoding a crafted Radiance HDR image. It is fixed in libvips 8.18.3. Red Hat Product Security has determined that this vulnerability does not affect any currently supported Red Hat product. This assessment may evolve based on further analysis and discovery.
Mitigation
No mitigation is required for currently supported Red Hat products, which are not affected by this vulnerability. Users of libvips versions before 8.18.3 should upgrade to 8.18.3 or later. Until an upgrade can be applied, the Radiance loader can be disabled in application code:
vips_operation_block_set("VipsForeignLoadRad", TRUE);
Alternatively, set the VIPS_BLOCK_UNTRUSTED environment variable to disable all untrusted image decoders, including the Radiance loader. VIPS_BLOCK_UNTRUSTED is broader than blocking Radiance alone and may disable other loaders the application relies on.
Understanding the Weakness (CWE)
Confidentiality
Technical Impact: Read Memory
An attacker could get secret values such as cryptographic keys, PII, memory addresses, or other information that could be used in additional attacks.
Confidentiality
Technical Impact: Bypass Protection Mechanism
Out-of-bounds memory could contain memory addresses or other information that can be used to bypass ASLR and other protection mechanisms in order to improve the reliability of exploiting a separate weakness for code execution.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
An attacker could cause a segmentation fault or crash by causing memory to be read outside of the bounds of the buffer. This is especially likely when the code reads a variable amount of data and assumes that a sentinel exists to stop the read operation, such as a NUL in a string.
Other
Technical Impact: Varies by Context
The read operation could produce other undefined or unexpected results.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
