Report · GCVE DatabaseAbout CVE-2025-8176Published 11 Nov 2025Updated 11 Jul 2026

Red Hat Security Advisory: libtiff security update

Affects Red HatSource GCVE Database

Mentioned vulnerabilities

CVE-2025-9900

Authoritative record:CVE-2025-8176· Medium 4.8

Not known to be exploited · CVSS 4.8 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS base score

4.8Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 18% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

Exploitation evidence

Disclosed: evidence found.
CVE published 26 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Red Hatredhat/libtiff`pkg:rpm/redhat/libtiff`Other threats	Affected =9.8	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Red Hat has released updated libtiff packages for Red Hat Enterprise Linux 9 and related products to fix these vulnerabilities. Users should apply the official security update as described in Red Hat advisory RHSA-2025:20956 and the referenced update article (https://access.redhat.com/articles/11258). No additional mitigations are indicated by the vendor.

Description

The libtiff packages contain a library of functions for manipulating Tagged Image File Format (TIFF) files. Security Fix(es): * libtiff: LibTIFF Use-After-Free Vulnerability (CVE-2025-8176) * libtiff: Libtiff Write-What-Where (CVE-2025-9900) For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

Impact

The vulnerabilities could allow attackers to exploit memory corruption issues in libtiff, potentially leading to arbitrary code execution or denial of service. The advisory rates the impact as Important, indicating a high security risk if unpatched. No known exploits in the wild have been reported at this time.

Summary

The libtiff library in Red Hat Enterprise Linux 9 and related CodeReady Linux Builder products contains two security vulnerabilities: CVE-2025-8176, a Use-After-Free vulnerability, and CVE-2025-9900, a Write-What-Where vulnerability. These issues could potentially allow an attacker to manipulate memory in unintended ways. Red Hat has released updated libtiff packages to address these vulnerabilities as detailed in advisory RHSA-2025:20956.

CWE-825Expired Pointer Dereference (opens in a new tab)
Base weakness
The product dereferences a pointer that contains a location for memory that was previously valid, but is no longer valid.
Architecture and Design
Choose a language that provides automatic memory management.
Implementation
When freeing pointers, be sure to set them to NULL once they are freed. However, the utilization of multiple or complex data structures may lower the usefulness of this strategy.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-123Write-what-where Condition (opens in a new tab)
Base weaknessLikelihood of exploit: High
Any condition where the attacker has the ability to write an arbitrary value to an arbitrary location, often as the result of a buffer overflow.
Architecture and Design · Language Selection
Use a language that provides appropriate memory abstractions.
Operation
Use OS-level preventative functionality integrated after the fact. Not a complete solution.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 12 Jul 2026, 11:13 UTC

WeaknessesCWE-825, CWE-123

Technical details

References

Community reviews

Related threats