LiveActive security incident?Get immediate response
CVE Record

CVE-2019-13118: In numbers.c in libxslt 1.1.33, a type holding grouping characters of an xsl:number instruction was too nar...

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2019-13118 is a libxslt flaw where specially malformed XSLT numbering input could cause the library to read uninitialized stack memory. The public bundle does not provide a CVSS score or confirmed exploitation. Treat it as relevant where systems transform untrusted XML or XSLT using libxslt 1.1.33.

Executive priority

Handle through normal security update processes unless a business-critical service accepts untrusted XML/XSLT. Escalate if libxslt 1.1.33 is exposed in externally reachable transformation workflows, because the flaw involves memory disclosure behavior and vendor security updates exist.

Technical view

In libxslt 1.1.33, numbers.c used a type too narrow for grouping characters in an xsl:number instruction. An invalid character and length combination could reach xsltNumberFormatDecimal, causing a read of uninitialized stack data. Public references include an upstream commit, OSS-Fuzz reports, and downstream Apple and Debian security updates.

Likely exposure

Exposure is most likely in applications, OS packages, or embedded components using libxslt 1.1.33 to process attacker-controlled XML/XSLT. Apple and Debian references suggest downstream packaged exposure, but the bundle does not enumerate all affected products or versions.

Exploitation context

The sources support fuzz-discovered memory-read behavior, not confirmed real-world exploitation. KEV is false, and no cited source in the bundle states active exploitation. Practical risk depends on whether untrusted transformation input can reach vulnerable libxslt code paths.

Researcher notes

Evidence is limited: no CVSS, CWE, broad affected CPE list, or exploit confirmation is included. The strongest technical anchors are the CVE description, upstream libxslt commit, OSS-Fuzz references, and downstream Apple/Debian advisories.

Mitigation direction

  • Identify systems and applications using libxslt 1.1.33.
  • Apply vendor security updates for libxslt from OS or product maintainers.
  • Review the upstream GNOME libxslt commit referenced for patch lineage.
  • Prioritize services processing untrusted XML or XSLT input.
  • Check Apple and Debian advisories where those platforms are in scope.

Validation and detection

  • Inventory libxslt versions in operating systems, containers, and bundled application dependencies.
  • Confirm installed packages include the security update referencing CVE-2019-13118.
  • Map XML/XSLT transformation entry points exposed to users or external data feeds.
  • Review dependency manifests and SBOMs for libxslt 1.1.33.
  • Check scanner findings against vendor advisory status before closure.
Prepared
Confidence
medium
Sources
12

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2019-13118 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
28Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.