Evidence used
- No CISA KEV confirmation is currently recorded.
- EPSS is 21.86% for the current model date.
BlackTreeCVE IntelligenceUnknown · libxml2
Official source article: Siemens SSA-398330 ↗. Check the applicable product and release in the original source.
High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 5 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
Verified remediation exists for at least one product or source, but 5 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
Alpine, Debian findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.
A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.
| Distribution release | Source package | Vendor state | Fixed version | Evidence |
|---|---|---|---|---|
| Alpine v3.23v3.23 · main | libxml2 | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 2.9.11-r0 | Alpine Security Database ↗Source updated 3 Oct 2026 |
| Alpine v3.22v3.22 · main | libxml2 | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 2.9.11-r0 | Alpine Security Database ↗Source updated 3 Oct 2026 |
| Alpine v3.21v3.21 · main | libxml2 | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 2.9.11-r0 | Alpine Security Database ↗Source updated 3 Oct 2026 |
| Debian trixietrixie · source | libxml2 | Vendor fix publishedDebian records a fixed source-package version for this release. | 2.9.10+dfsg-6.6 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian bookwormbookworm · source | libxml2 | Vendor fix publishedDebian records a fixed source-package version for this release. | 2.9.10+dfsg-6.6 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian forkyforky · source | libxml2 | Vendor fix publishedDebian records a fixed source-package version for this release. | 2.9.10+dfsg-6.6 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian sidsid · source | libxml2 | Vendor fix publishedDebian records a fixed source-package version for this release. | 2.9.10+dfsg-6.6 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.
| Ecosystem and package | Affected range | First fixed version | Evidence |
|---|---|---|---|
| RubyGemsnokogiri | ECOSYSTEM: introduced 0; fixed 1.11.4 | 1.11.4 | OSV record ↗aggregator derived · 9 Mar 2024 |
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
The vendor explicitly identifies these products as affected by this CVE.
The vendor explicitly identifies these products as affected by this CVE.
High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 5 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
Fix availability varies by productThere's a flaw in libxml2 in versions before 2.9.11. An attacker who is able to submit a crafted file to be processed by an application linked with libxml2 could trigger a use-after-free. The greatest impact from this flaw is to confidentiality, integrity, and availability.
There's a flaw in libxml2 in versions before 2.9.11. An attacker who is able to submit a crafted file to be processed by an application linked with libxml2 could trigger a use-after-free. The greatest impact from this flaw is to confidentiality, integrity, and availability.
The program can continue using memory after it has been released, producing unsafe and attacker-influenceable behaviour.
An attacker operating through a network path may attempt exploitation without authentication after a user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
There's a flaw in libxml2 in versions before 2.9.11. An attacker who is able to submit a crafted file to be processed by an application linked with libxml2 could trigger a use-after-free. The greatest impact from this flaw is to confidentiality, integrity, and availability.
The program can continue using memory after it has been released, producing unsafe and attacker-influenceable behaviour.
An attacker operating through a network path may attempt exploitation without authentication after a user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
CWE-416: Use After Free. The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory belongs to the code that operates on the new pointer.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
Operational remediation based on structured source evidence.
Published 18 May 2021 · Last source change 3 Aug 2024, 17:01 UTC · CWE-416 · Use After Free
Missing structured fields: affected product. Missing data is not evidence of low risk; review the primary advisory.