CVE-2015-9019: In libxslt 1.1.29 and earlier, the EXSLT math.random function was not initialized with a random seed during startup, which could cause usage…
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 2.4% (FIRST EPSS); higher than 84.4% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: libxslt (openSUSE:Tumbleweed) 1.1.34-3.2; libxslt (SUSE:Linux Enterprise Desktop 12 SP1) 1.1.28-16.1; libxslt (SUSE:Linux Enterprise Software Development Kit 11 SP4) 1.1.24-19.33.1.
Low priority for now. Upgrade to libxslt (openSUSE:Tumbleweed) 1.1.34-3.2; libxslt (SUSE:Linux Enterprise Desktop 12 SP1) 1.1.28-16.1; libxslt (SUSE:Linux Enterprise Software Development Kit 11 SP4) 1.1.24-19.33.1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In libxslt 1.1.29 and earlier, the EXSLT math.random function was not initialized with a random seed during startup, which could cause usage of this function to produce predictable outputs.
- Published
- Apr 5, 2017
- Updated
- Jun 16, 2026
- EPSS
- 2.4% · 84th percentile
- CWE
- CWE-330
Report tools
Action score
22
Low priority for now.
- CVSS
- 21 / 40 · 5.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.4%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| xmlsoft | libxslt | cpe:2.3:a:xmlsoft:libxslt |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- xmlsoft libxsltup to 1.1.29 inclusive
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | libxslt | from 0 | — |
| openSUSE:Tumbleweed | libxslt | before 1.1.34-3.2 | 1.1.34-3.2 |
| SUSE:Linux Enterprise Desktop 12 SP1 | libxslt | before 1.1.28-16.1 | 1.1.28-16.1 |
| SUSE:Linux Enterprise Software Development Kit 11 SP4 | libxslt | before 1.1.24-19.33.1 | 1.1.24-19.33.1 |
| SUSE:Linux Enterprise Software Development Kit 11 SP4 | libxslt-python | before 1.1.24-19.33.3 | 1.1.24-19.33.3 |
Same product
xmlsoft: all recordsOther highest-scoring records for the same primary product.
- CVE-2019-11068libxslt through 1.1.33 allows bypass of a protection mechanism because callers of xsltCheckRead and xsltCheckWrite permit access even upon…41Plan
- CVE-2008-2935Multiple heap-based buffer overflows in the rc4 (1) encryption (aka exsltCryptoRc4EncryptFunction) and (2) decryption (aka…34Monitor
- CVE-2025-24855numbers.c in libxslt before 1.1.43 has a use-after-free because, in nested XPath evaluations, an XPath context node can be modified but…31Monitor
Published before and after this one in the same product
- ← EarlierCVE-2012-6139Apr 12, 2013 · libxslt before 1.1.28 allows remote attackers to cause a denial of service (NULL pointer dereference and crash) via an (1) empty match…21Monitor
- ← EarlierCVE-2013-4520Dec 14, 2013 · xslt.c in libxslt before 1.1.25 allows context-dependent attackers to cause a denial of service (crash) via a stylesheet that embeds a DTD…18Monitor
- Later →CVE-2019-13117Jun 30, 2019 · In numbers.c in libxslt 1.1.33, an xsl:number with certain format strings could lead to a uninitialized read in…23Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| opensuse:libxslt | 1.1.34-3.2 · openSUSE:Tumbleweed | Package registry (OSV) |
| suse:libxslt | 1.1.24-19.33.1 · SUSE:Linux Enterprise Software Development Kit 11 SP4 | Package registry (OSV) |
| suse:libxslt-python | 1.1.24-19.33.3 · SUSE:Linux Enterprise Software Development Kit 11 SP4 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-330 · Use of Insufficiently Random ValuesCVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.