Vulnerability Database · npm · openframe-image · Version
openframe-image 0.1.1
0.1.1 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: 0.2.3.
Critical 0 High 1 Medium 0 Low 0 Unrated 0
-
Released 17 Feb 2016
Licence GPL-3.0
Also known from other sources 1
Newer releases 11
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
openframe-image 0.1.1 vulnerabilities
1 vulnerability cover openframe-image 0.1.1. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| CVE-2016-10616: Insecure Resource Downloads in openframe-image | N/A high | No fix published | 18 Feb 2019 |
Looking for another version, or everything Vulert holds for openframe-image?
Questions
About openframe-image 0.1.1
Is openframe-image 0.1.1 vulnerable?
Yes. 1 vulnerability in the Vulert database cover openframe-image 0.1.1: 0 critical, 1 high, 0 medium and 0 low. The upgrade Vulert recommends is 0.2.3, and each entry above names the fixed version to move to.
Which version of openframe-image should I use instead of 0.1.1?
0.2.3 is the version Vulert recommends for this release line. The version table on the package page lists every release with the vulnerabilities recorded against it.
Is 0.1.1 the latest release of openframe-image?
No. 0.1.1 was published 17 Feb 2016, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.
How do I monitor openframe-image for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the openframe-image version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.