CVE-2025-9900
No exploitation reported by the sources we read.
- Published2025-09-23
- WeaknessCWE-123
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
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.
Timeline
dates in UTC- 2025-09-2317:15CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-23 18:48 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2025-9900?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2025-9900?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
Distribution builds and vendor advisories
Packages from OSV.dev and products from the vendors' CSAF advisories.
version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.
Vendor advisories
Red Hat Security Advisory: Red Hat AI Inference Server 3.2.2 (ROCm)
Red Hat Security Advisory: Red Hat AI Inference Server 3.2.2 (CUDA)
Red Hat Security Advisory: Red Hat AI Inference Server Model Optimization Tools 3.2.2 (CUDA)
Red Hat Security Advisory: Red Hat AI Inference Server 3.2.2 (ROCm)
Red Hat Security Advisory: Red Hat AI Inference Server 3.2.2 (CUDA)
Red Hat Security Advisory: A Subscription Management tool for finding and reporting Red Hat product usage
Fix
- Vendor fix Red Hat Product Security RHSA-2026:3462 · 1 productFor more information visit https://access.redhat.com/errata/RHSA-2026:3462
- Vendor fix Red Hat Product Security RHSA-2026:3461 · 2 productsFor more information visit https://access.redhat.com/errata/RHSA-2026:3461
- Vendor fix Red Hat Product Security RHSA-2025:23080 · 2 productsFor more information visit https://access.redhat.com/errata/RHSA-2025:23080
- Vendor fix Red Hat Product Security RHSA-2025:23079 · 1 productFor more information visit https://access.redhat.com/errata/RHSA-2025:23079
- Vendor fix Red Hat Product Security RHSA-2025:23078 · 2 productsFor more information visit https://access.redhat.com/errata/RHSA-2025:23078
- Vendor fix Red Hat Product Security RHSA-2025:21994 · 2 productsThe containers required to run Discovery can be installed through discovery-installer RPM. See the official documentation for more details.
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
- Published
- 2025-09-23
- Last Modified
- 2026-09-26
- NVD status
- Deferred
Frequently asked questions
What is CVE-2025-9900?
Is CVE-2025-9900 actively exploited?
What is the CVSS score for CVE-2025-9900?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.