A flaw was found in Libtiff. This vulnerability is a "write-what-where" condition, triggered when the library processes a specially crafted TIFF image file.
By providing an abnormally large image height value in the file's metadata, an attacker can trick the library into writing attacker-controlled color data to an arbitrary memory location. This memory corruption can be exploited to cause a denial of service (application crash) or to achieve arbitrary code execution with the permissions of the user.
Security readout for executives and security teams
Plain-English summary
CVE-2025-9900 is a high-severity libtiff memory corruption flaw. A malicious TIFF image can trigger an arbitrary memory write when processed, potentially crashing the application or running code with the affected user’s privileges. Business risk is highest where servers or desktops automatically process untrusted image files.
Executive priority
Treat as high priority where TIFF files cross trust boundaries. It is not marked as actively exploited in the supplied sources, but the potential impact includes code execution. Patch affected Red Hat packages through normal emergency or accelerated maintenance processes.
Technical view
The flaw is described as CWE-123 write-what-where in libtiff. A crafted TIFF with an abnormally large image height can cause attacker-controlled color data to be written to an arbitrary memory location. CVSS 3.1 is 8.8 with network attack vector, low complexity, no privileges, and user interaction required.
Likely exposure
Exposure is likely on Red Hat systems carrying affected libtiff-related packages, including RHEL 10, RHEL 8 streams, RHEL 7 ELS, and listed support variants. Relevant package names include libtiff, compat-libtiff3, mingw-libtiff, and spice-client-win.
Exploitation context
The source bundle does not show CISA KEV listing or cited evidence of active exploitation. Practical exposure depends on whether affected software processes attacker-supplied TIFF files, such as uploads, email attachments, shared folders, document pipelines, or image conversion workflows.
Researcher notes
Evidence is strongest for Red Hat-packaged libtiff exposure. The bundle identifies affected package versions and advisories but does not provide exploit maturity, proof-of-concept status, or upstream patch details. Avoid assuming all libtiff deployments are affected without vendor confirmation.
Mitigation direction
Apply the relevant Red Hat security advisories for affected libtiff-related packages.
Prioritize systems that process untrusted or external TIFF image files.
Restrict TIFF upload or processing paths until vendor updates are installed.
Run image-processing services with least privilege and isolation.
Check vendor guidance for non-Red Hat libtiff builds or bundled copies.
Validation and detection
Inventory installed libtiff, compat-libtiff3, mingw-libtiff, and spice-client-win packages.
Map image-processing applications that accept TIFF files from users or external sources.
Confirm patched package versions against the applicable Red Hat advisory.
Review logs for crashes in services that parse TIFF images.
Identify statically bundled libtiff copies in third-party applications.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-123: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
5Timeline events
2ADP providers
39Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-123 · source CWE mapping
Write-what-where Condition
Write-what-where Condition represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.