OESA-2025-2479 (CVE-2025-43718)
Vulnerability from osv_openeuler – Published: 2025-10-17 11:09 – Updated: 2026-08-06 11:09 – Source websiteis a PDF rendering library.
Security Fix(es):
Poppler 24.06.1 through 25.x before 25.04.0 allows stack consumption and a SIGSEGV via deeply nested structures within the metadata (such as GTS_PDFEVersion) of a PDF document, e.g., a regular expression for a long pdfsubver string. This occurs in Dict::lookup, Catalog::getMetadata, and associated functions in PDFDoc, with deep recursion in the regex executor (std::__detail::_Executor).(CVE-2025-43718)
Poppler is a library for rendering PDF files, and examining or modifying their structure. A use-after-free (write) vulnerability has been detected in versions Poppler prior to 25.10.0 within the StructTreeRoot class. The issue arises from the use of raw pointers to elements of a std::vector, which can lead to dangling pointers when the vector is resized. The vulnerability stems from the way that refToParentMap stores references to std::vector elements using raw pointers. These pointers may become invalid when the vector is resized. This vulnerability is a common security problem involving the use of raw pointers to std::vectors. Internally, std::vector stores its elements in a dynamically allocated array. When the array reaches its capacity and a new element is added, the vector reallocates a larger block of memory and moves all the existing elements to the new location. At this point if any pointers to elements are stored before a resize occurs, they become dangling pointers once the reallocation happens. Version 25.10.0 contains a patch for the issue.(CVE-2025-52885)
| URL | Type |
|---|---|
| https://www.openeuler.org/zh/security/security-bu… | ADVISORY |
| https://nvd.nist.gov/vuln/detail/CVE-2025-43718 | ADVISORY |
| https://nvd.nist.gov/vuln/detail/CVE-2025-52885 | ADVISORY |
| Ecosystem | Package | Version |
|---|---|---|
| openEuler:22.03-LTS-SP4 |
poppler
pkg:rpm/openEuler/poppler&distro=openEuler-22.03-LTS-SP4
|
Affected: < 0.90.0-15.oe2203sp4 (ecosystem)
|
{
"affected": [
{
"ecosystem_specific": {
"aarch64": [
"poppler-0.90.0-15.oe2203sp4.aarch64.rpm",
"poppler-cpp-0.90.0-15.oe2203sp4.aarch64.rpm",
"poppler-cpp-devel-0.90.0-15.oe2203sp4.aarch64.rpm",
"poppler-debuginfo-0.90.0-15.oe2203sp4.aarch64.rpm",
"poppler-debugsource-0.90.0-15.oe2203sp4.aarch64.rpm",
"poppler-devel-0.90.0-15.oe2203sp4.aarch64.rpm",
"poppler-glib-0.90.0-15.oe2203sp4.aarch64.rpm",
"poppler-glib-devel-0.90.0-15.oe2203sp4.aarch64.rpm",
"poppler-qt5-0.90.0-15.oe2203sp4.aarch64.rpm",
"poppler-qt5-devel-0.90.0-15.oe2203sp4.aarch64.rpm",
"poppler-utils-0.90.0-15.oe2203sp4.aarch64.rpm"
],
"noarch": [
"poppler-glib-doc-0.90.0-15.oe2203sp4.noarch.rpm",
"poppler-help-0.90.0-15.oe2203sp4.noarch.rpm"
],
"src": [
"poppler-0.90.0-15.oe2203sp4.src.rpm"
],
"x86_64": [
"poppler-0.90.0-15.oe2203sp4.x86_64.rpm",
"poppler-cpp-0.90.0-15.oe2203sp4.x86_64.rpm",
"poppler-cpp-devel-0.90.0-15.oe2203sp4.x86_64.rpm",
"poppler-debuginfo-0.90.0-15.oe2203sp4.x86_64.rpm",
"poppler-debugsource-0.90.0-15.oe2203sp4.x86_64.rpm",
"poppler-devel-0.90.0-15.oe2203sp4.x86_64.rpm",
"poppler-glib-0.90.0-15.oe2203sp4.x86_64.rpm",
"poppler-glib-devel-0.90.0-15.oe2203sp4.x86_64.rpm",
"poppler-qt5-0.90.0-15.oe2203sp4.x86_64.rpm",
"poppler-qt5-devel-0.90.0-15.oe2203sp4.x86_64.rpm",
"poppler-utils-0.90.0-15.oe2203sp4.x86_64.rpm"
]
},
"package": {
"ecosystem": "openEuler:22.03-LTS-SP4",
"name": "poppler",
"purl": "pkg:rpm/openEuler/poppler\u0026distro=openEuler-22.03-LTS-SP4"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "0.90.0-15.oe2203sp4"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"database_specific": {
"severity": "Medium"
},
"details": "is a PDF rendering library.\r\n\r\nSecurity Fix(es):\n\nPoppler 24.06.1 through 25.x before 25.04.0 allows stack consumption and a SIGSEGV via deeply nested structures within the metadata (such as GTS_PDFEVersion) of a PDF document, e.g., a regular expression for a long pdfsubver string. This occurs in Dict::lookup, Catalog::getMetadata, and associated functions in PDFDoc, with deep recursion in the regex executor (std::__detail::_Executor).(CVE-2025-43718)\n\nPoppler is a library for rendering PDF files, and examining or modifying their structure. A use-after-free (write) vulnerability has been detected in versions Poppler prior to 25.10.0 within the StructTreeRoot class. The issue arises from the use of raw pointers to elements of a `std::vector`, which can lead to dangling pointers when the vector is resized. The vulnerability stems from the way that refToParentMap stores references to `std::vector` elements using raw pointers. These pointers may become invalid when the vector is resized. This vulnerability is a common security problem involving the use of raw pointers to `std::vectors`. Internally, `std::vector` stores its elements in a dynamically allocated array. When the array reaches its capacity and a new element is added, the vector reallocates a larger block of memory and moves all the existing elements to the new location. At this point if any pointers to elements are stored before a resize occurs, they become dangling pointers once the reallocation happens. Version 25.10.0 contains a patch for the issue.(CVE-2025-52885)",
"id": "OESA-2025-2479",
"modified": "2026-08-06T11:09:34Z",
"published": "2025-10-17T11:09:34Z",
"references": [
{
"type": "ADVISORY",
"url": "https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2025-2479"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-43718"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-52885"
}
],
"schema_version": "1.7.2",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
],
"summary": "poppler security update",
"upstream": [
"CVE-2025-43718",
"CVE-2025-52885"
]
}
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
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
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.