Skip to content
Noroxi
CVE-2019-13118· NVD / CVE Program· CNA mitre

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

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.

MediumCVSS 5.3 · v3.1—No exploit Fix available
Published
Jun 30, 2019
Updated
Jun 16, 2026
EPSS
5.2% · 92th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

23

Monitor

Low priority for now.

CVSS
21 / 40 · 5.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
2 / 30 · 5.2%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Affected systems

VendorProduct
xmlsoftlibxslt
opensuseleap
netappactive iq unified manager
netappcloud backup
netappclustered data ontap
netappe-series performance analyzer
netappe-series santricity management plug-ins
netappe-series santricity os controller
netappe-series santricity storage manager
netappe-series santricity web services
netapponcommand insight
netapponcommand 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.

EcosystemPackageAffected rangeFix
Alpine:v3.10libxsltbefore 1.1.33-r31.1.33-r3
Alpine:v3.11libxsltbefore 1.1.34-r01.1.34-r0
Debian:12libxsltbefore 1.1.32-2.11.1.32-2.1
Debian:8libxsltbefore 1.1.28-2+deb8u51.1.28-2+deb8u5
openSUSE:Leap 15.1libxsltbefore 1.1.32-lp151.3.6.11.1.32-lp151.3.6.1
openSUSE:Leap 15.1libxslt-pythonbefore 1.1.32-lp151.3.6.11.1.32-lp151.3.6.1
openSUSE:Tumbleweedlibxsltbefore 1.1.34-3.21.1.34-3.2
RubyGemsnokogiribefore 1.10.51.10.5
SUSE:Linux Enterprise Desktop 12 SP4libxsltbefore 1.1.28-17.6.11.1.28-17.6.1
SUSE:Linux Enterprise Module for Basesystem 15 SP1libxsltbefore 1.1.32-3.8.241.1.32-3.8.24

Other 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 r
    41Plan
  • CVE-2008-2935Multiple heap-based buffer overflows in the rc4 (1) encryption (aka exsltCryptoRc4EncryptFunction) and (2) decryption (aka exsltCryptoRc4Dec
    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 neve
    31Monitor
  • CVE-2024-55549xsltGetInheritedNsList in libxslt before 1.1.43 has a use-after-free issue related to exclusion of result prefixes.
    31Monitor
  • CVE-2019-5815Type confusion in xsltNumberFormatGetMultipleLevel prior to libxslt 1.1.33 could allow attackers to potentially exploit heap corruption via
    31Monitor
  • CVE-2019-18197In 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 / packageFixed versionSource
alpine:libxslt1.1.33-r3 · Alpine:v3.10Package registry (OSV)
debian:libxslt1.1.32-2.1 · Debian:12Package registry (OSV)
opensuse:libxslt1.1.32-lp151.3.6.1 · openSUSE:Leap 15.1Package registry (OSV)
opensuse:libxslt-python1.1.32-lp151.3.6.1 · openSUSE:Leap 15.1Package registry (OSV)
RubyGems:nokogiri1.10.5Package registry (OSV)
suse:libxslt1.1.28-17.6.1 · SUSE:Linux Enterprise Desktop 12 SP4Package 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.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Finders, 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

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.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records