Vulnerability Database · npm · op-browser · Version
op-browser 1.0.5
1.0.5 is affected by 1 vulnerability.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to.
Critical 1 High 0 Medium 0 Low 0 Unrated 0
-
Released 13 Sep 2017
Licence MIT
Also known from other sources 1
Newer releases 10
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
op-browser 1.0.5 vulnerabilities
1 vulnerability cover op-browser 1.0.5. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| CVE-2020-7625: Command Injection in op-browser | 9.8 critical | No fix published | 10 Feb 2022 |
Looking for another version, or everything Vulert holds for op-browser?
Questions
About op-browser 1.0.5
Is op-browser 1.0.5 vulnerable?
Yes. 1 vulnerability in the Vulert database cover op-browser 1.0.5: 1 critical, 0 high, 0 medium and 0 low. Each entry above names the fixed version to move to.
Is 1.0.5 the latest release of op-browser?
No. 1.0.5 was published 13 Sep 2017, 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 op-browser for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the op-browser version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.