Vulnerability Database · npm · ltt · Version
ltt 1.1.0
1.1.0 is affected by 1 vulnerability.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: 1.1.0.
Critical 0 High 1 Medium 0 Low 0 Unrated 0
-
Released 17 May 2016
Status latest release
Licence ISC
Also known from other sources 1
Newer releases 1
Database updated 23/Oct/2026
Release and licence data published by the npm registry. Licence information is not legal advice.
Concerned about your application's security?
Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.
01 Vulnerabilities affecting this version
ltt 1.1.0 vulnerabilities
1 vulnerability cover ltt 1.1.0. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| CVE-2017-16212: Directory Traversal in ltt | 7.5 high | No fix published | 23 Jul 2018 |
Looking for another version, or everything Vulert holds for ltt?
Questions
About ltt 1.1.0
Is ltt 1.1.0 vulnerable?
Yes. 1 vulnerability in the Vulert database cover ltt 1.1.0: 0 critical, 1 high, 0 medium and 0 low. The upgrade Vulert recommends is 1.1.0, and each entry above names the fixed version to move to.
Which version of ltt should I use instead of 1.1.0?
1.1.0 is the version Vulert recommends for this release line, which is also the release the publisher currently ships. The version table on the package page lists every release with the vulnerabilities recorded against it.
Is 1.1.0 the latest release of ltt?
Yes. 1.1.0 is the current release, published 17 May 2016. Staying on the current line is what keeps you inside the publisher's fixes.
How do I monitor ltt for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the ltt version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.