OESA-2025-2048 (CVE-2025-8534)
Vulnerability from osv_openeuler – Published: 2025-08-15 11:09 – Updated: 2026-08-06 11:09 – Source websiteThis provides support for the Tag Image File Format (TIFF), a widely used format for storing image data. The latest version of the TIFF specification is available on-line in several different formats.And contains command-line programs for manipulating TIFF format image files using the libtiff library.
Security Fix(es):
LibTIFF is a library for reading and writing TIFF (label image file format) files that are open source. This library contains some command-line tools for handling TIFF files. There is a security vulnerability in the 4.6.0 version of LibTIFF, which originates from the dereference of the null pointer of the function PS_Lvl2page in the file tools/tiff2ps.c.(CVE-2025-8534)
A vulnerability was found in LibTIFF up to 4.5.1 (Image Processing Software). It has been rated as critical.Using CWE to declare the problem leads to CWE-121. A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function).Impacted is confidentiality, integrity, and availability.Applying the patch 8a7a48d7a645992ca83062b3a1873c951661e2b3 is able to eliminate this problem. The bugfix is ready for download at gitlab.com.(CVE-2025-8851)
| URL | Type | |
|---|---|---|
{
"affected": [
{
"ecosystem_specific": {
"aarch64": [
"libtiff-4.3.0-42.oe2203sp3.aarch64.rpm",
"libtiff-debuginfo-4.3.0-42.oe2203sp3.aarch64.rpm",
"libtiff-debugsource-4.3.0-42.oe2203sp3.aarch64.rpm",
"libtiff-devel-4.3.0-42.oe2203sp3.aarch64.rpm",
"libtiff-static-4.3.0-42.oe2203sp3.aarch64.rpm",
"libtiff-tools-4.3.0-42.oe2203sp3.aarch64.rpm"
],
"noarch": [
"libtiff-help-4.3.0-42.oe2203sp3.noarch.rpm"
],
"src": [
"libtiff-4.3.0-42.oe2203sp3.src.rpm"
],
"x86_64": [
"libtiff-4.3.0-42.oe2203sp3.x86_64.rpm",
"libtiff-debuginfo-4.3.0-42.oe2203sp3.x86_64.rpm",
"libtiff-debugsource-4.3.0-42.oe2203sp3.x86_64.rpm",
"libtiff-devel-4.3.0-42.oe2203sp3.x86_64.rpm",
"libtiff-static-4.3.0-42.oe2203sp3.x86_64.rpm",
"libtiff-tools-4.3.0-42.oe2203sp3.x86_64.rpm"
]
},
"package": {
"ecosystem": "openEuler:22.03-LTS-SP3",
"name": "libtiff",
"purl": "pkg:rpm/openEuler/libtiff\u0026distro=openEuler-22.03-LTS-SP3"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "4.3.0-42.oe2203sp3"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"database_specific": {
"severity": "Medium"
},
"details": "This provides support for the Tag Image File Format (TIFF), a widely\nused format for storing image data. The latest version of the TIFF specification\nis available on-line in several different formats.And contains command-line programs\nfor manipulating TIFF format image files using the libtiff library.\r\n\r\nSecurity Fix(es):\n\nLibTIFF is a library for reading and writing TIFF (label image file format) files that are open source. This library contains some command-line tools for handling TIFF files.\n There is a security vulnerability in the 4.6.0 version of LibTIFF, which originates from the dereference of the null pointer of the function PS_Lvl2page in the file tools/tiff2ps.c.(CVE-2025-8534)\n\nA vulnerability was found in LibTIFF up to 4.5.1 (Image Processing Software). It has been rated as critical.Using CWE to declare the problem leads to CWE-121. A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function).Impacted is confidentiality, integrity, and availability.Applying the patch 8a7a48d7a645992ca83062b3a1873c951661e2b3 is able to eliminate this problem. The bugfix is ready for download at gitlab.com.(CVE-2025-8851)",
"id": "OESA-2025-2048",
"modified": "2026-08-06T11:09:07Z",
"published": "2025-08-15T11:09:07Z",
"references": [
{
"type": "ADVISORY",
"url": "https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2025-2048"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-8534"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-8851"
}
],
"schema_version": "1.7.2",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L",
"type": "CVSS_V3"
}
],
"summary": "libtiff security update",
"upstream": [
"CVE-2025-8534",
"CVE-2025-8851"
]
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.