CVE-2019-13118: In numbers.c in libxslt 1.1.33, a type holding grouping characters of an xsl:number instruction was too narrow and an invalid character/leng
Noroxi assessment
Priority: Monitor (action score 23/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: 5.1% (FIRST EPSS); higher than 92.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.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: libxslt (Alpine:v3.10) 1.1.33-r3; libxslt (Alpine:v3.11) 1.1.34-r0; libxslt (Debian:12) 1.1.32-2.1.
Low priority for now. Upgrade to libxslt (Alpine:v3.10) 1.1.33-r3; libxslt (Alpine:v3.11) 1.1.34-r0; libxslt (Debian:12) 1.1.32-2.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 numbers.c in libxslt 1.1.33, a type holding grouping characters of an xsl:number instruction was too narrow and an invalid character/length combination could be passed to xsltNumberFormatDecimal, leading to a read of uninitialized stack data.
- Published
- Jun 30, 2019
- Updated
- Jun 16, 2026
- EPSS
- 5.1% · 92th percentile
- CWE
- CWE-843
Report tools
Action score
23
Monitor
Low priority for now.
- CVSS
- 21 / 40 · 5.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 2 / 30 · 5.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
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.
Running WordPress? Scan your site free with WP Lens
Noroxi 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 |
| opensuse | leap | cpe:2.3:o:opensuse:leap |
| netapp | active iq unified manager | cpe:2.3:a:netapp:active_iq_unified_manager |
| netapp | cloud backup | cpe:2.3:a:netapp:cloud_backup |
| netapp | clustered data ontap | cpe:2.3:a:netapp:clustered_data_ontap |
| netapp | e-series performance analyzer | cpe:2.3:a:netapp:e-series_performance_analyzer |
| netapp | e-series santricity management plug-ins | cpe:2.3:a:netapp:e-series_santricity_management_plug-ins |
| netapp | e-series santricity os controller | cpe:2.3:a:netapp:e-series_santricity_os_controller |
| netapp | e-series santricity storage manager | cpe:2.3:a:netapp:e-series_santricity_storage_manager |
| netapp | e-series santricity web services | cpe:2.3:a:netapp:e-series_santricity_web_services |
| netapp | oncommand insight | cpe:2.3:a:netapp:oncommand_insight |
| netapp | oncommand workflow automation | cpe:2.3:a:netapp:oncommand_workflow_automation |
and 13 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- oracle jdk1.8.0
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.10 | libxslt | before 1.1.33-r3 | 1.1.33-r3 |
| Alpine:v3.11 | libxslt | before 1.1.34-r0 | 1.1.34-r0 |
| Debian:12 | libxslt | before 1.1.32-2.1 | 1.1.32-2.1 |
| Debian:8 | libxslt | before 1.1.28-2+deb8u5 | 1.1.28-2+deb8u5 |
| openSUSE:Leap 15.1 | libxslt | before 1.1.32-lp151.3.6.1 | 1.1.32-lp151.3.6.1 |
| openSUSE:Leap 15.1 | libxslt-python | before 1.1.32-lp151.3.6.1 | 1.1.32-lp151.3.6.1 |
| openSUSE:Tumbleweed | libxslt | before 1.1.34-3.2 | 1.1.34-3.2 |
| RubyGems | nokogiri | before 1.10.5 | 1.10.5 |
| SUSE:Linux Enterprise Desktop 12 SP4 | libxslt | before 1.1.28-17.6.1 | 1.1.28-17.6.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP1 | libxslt | before 1.1.32-3.8.24 | 1.1.32-3.8.24 |
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 r41Plan
- CVE-2008-2935Multiple heap-based buffer overflows in the rc4 (1) encryption (aka exsltCryptoRc4EncryptFunction) and (2) decryption (aka exsltCryptoRc4Dec34Monitor
- 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 neve31Monitor
Published before and after this one in the same product
- ← EarlierCVE-2015-9019Apr 5, 2017 · In libxslt 1.1.29 and earlier, the EXSLT math.random function was not initialized with a random seed during startup, which could cause usage22Monitor
- ← EarlierCVE-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 xsltNumberFormatInsertNumber23Monitor
- Later →CVE-2019-18197Oct 18, 2019 · In xsltCopyText in transform.c in libxslt 1.1.33, a pointer variable isn't reset under certain circumstances.31Monitor
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 |
|---|---|---|
| alpine:libxslt | 1.1.33-r3 · Alpine:v3.10 | Package registry (OSV) |
| debian:libxslt | 1.1.32-2.1 · Debian:12 | Package registry (OSV) |
| opensuse:libxslt | 1.1.32-lp151.3.6.1 · openSUSE:Leap 15.1 | Package registry (OSV) |
| opensuse:libxslt-python | 1.1.32-lp151.3.6.1 · openSUSE:Leap 15.1 | Package registry (OSV) |
| RubyGems:nokogiri | 1.10.5 | Package registry (OSV) |
| suse:libxslt | 1.1.28-17.6.1 · SUSE:Linux Enterprise Desktop 12 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.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
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-843 · Access of Resource Using Incompatible Type ('Type Confusion')CVSS vector
CVSS:3.1/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.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (19 more)Show less
- seclists.org/fulldisclosure/2019/Aug/11
- seclists.org/fulldisclosure/2019/Aug/13
- seclists.org/fulldisclosure/2019/Aug/14
- seclists.org/fulldisclosure/2019/Aug/15
- seclists.org/fulldisclosure/2019/Jul/22
- seclists.org/fulldisclosure/2019/Jul/23
- seclists.org/fulldisclosure/2019/Jul/24
- seclists.org/fulldisclosure/2019/Jul/26
- seclists.org/fulldisclosure/2019/Jul/31
- seclists.org/fulldisclosure/2019/Jul/37
- seclists.org/fulldisclosure/2019/Jul/38
- www.openwall.com/lists/oss-security/2019/11/17/2
- bugs.chromium.org/p/oss-fuzz/issues/detail?id=15069
- gitlab.gnome.org/GNOME/libxslt/commit/6ce8de69330783977dd14f6569419489875fb71b
- support.apple.com/kb/HT210357
- lists.apache.org/thread.html/r58af02e294bd07f487e2c64ffc0a29b837db5600e33b6e698b9d696b%40%3Cissues.bookkeeper.apache.org%3E
- lists.apache.org/thread.html/rf4c02775860db415b4955778a131c2795223f61cb8c6a450893651e4%40%3Cissues.bookkeeper.apache.org%3E
- lists.debian.org/debian-lts-announce/2019/07/msg00020.html
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/IOYJKXPQCUNBMMQJWYXOR6QRUJZHEDRZ/
Vendor advisories and official records. Exploit/PoC links are deliberately left out.