Evidence used
- No CISA KEV confirmation is currently recorded.
- The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
- EPSS is 6.46% for the current model date.
BlackTreeCVE IntelligenceUnknown · Unknown
Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.
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 | libxslt | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 1.1.34-r0 | Alpine Security Database ↗Source updated 3 Oct 2026 |
| Alpine v3.22v3.22 · main | libxslt | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 1.1.34-r0 | Alpine Security Database ↗Source updated 3 Oct 2026 |
| Alpine v3.21v3.21 · main | libxslt | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 1.1.34-r0 | Alpine Security Database ↗Source updated 3 Oct 2026 |
| Debian trixietrixie · source | libxslt | Vendor fix publishedDebian records a fixed source-package version for this release. | 1.1.32-2.1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian bookwormbookworm · source | libxslt | Vendor fix publishedDebian records a fixed source-package version for this release. | 1.1.32-2.1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian forkyforky · source | libxslt | Vendor fix publishedDebian records a fixed source-package version for this release. | 1.1.32-2.1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian sidsid · source | libxslt | Vendor fix publishedDebian records a fixed source-package version for this release. | 1.1.32-2.1 | 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.10.5 | 1.10.5 | OSV record ↗aggregator derived · 10 Jun 2026 |
| rubygemsnokogiri | < 1.10.5 | 1.10.5 | GitHub advisory ↗github reviewed aggregator · 9 Jun 2026 |
Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.
Patch availableIn numbers.c in libxslt 1.1.33, an xsl:number with certain format strings could lead to a uninitialized read in xsltNumberFormatInsertNumbers. This could allow an attacker to discern whether a byte on the stack contains the characters A, a, I, i, or 0, or any other character.
In numbers.c in libxslt 1.1.33, an xsl:number with certain format strings could lead to a uninitialized read in xsltNumberFormatInsertNumbers. This could allow an attacker to discern whether a byte on the stack contains the characters A, a, I, i, or 0, or any other character.
The product uses or accesses a resource that has not been initialized.
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
In numbers.c in libxslt 1.1.33, an xsl:number with certain format strings could lead to a uninitialized read in xsltNumberFormatInsertNumbers. This could allow an attacker to discern whether a byte on the stack contains the characters A, a, I, i, or 0, or any other character.
The product uses or accesses a resource that has not been initialized.
An attacker operating through a network path may attempt exploitation without authentication or 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-908: Use of Uninitialized Resource. The product uses or accesses a resource that has not been initialized.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:NCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
Operational remediation based on structured source evidence.
Published 1 Jul 2019 · Last source change 28 May 2026, 18:31 UTC · CWE-908 · Use of Uninitialized Resource
Missing structured fields: affected product. Missing data is not evidence of low risk; review the primary advisory.