Vulnerability Database · Maven · com.browserup:browserup-proxy · Version
com.browserup:browserup-proxy 1.2.0
1.2.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: 2.1.2.
Critical 0 High 1 Medium 0 Low 0 Unrated 0
-
Released 03 Jun 2019
Licence Apache-2.0
Also known from other sources 1
Newer releases 8
Database updated 23/Oct/2026
Release and licence data published by Maven Central. 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
com.browserup:browserup-proxy 1.2.0 vulnerabilities
1 vulnerability cover com.browserup:browserup-proxy 1.2.0. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| CVE-2020-26282: Server-Side Template Injection in com.browserup:browserup-proxy | 10.0 high | 2.1.2 | 24 Dec 2020 |
Looking for another version, or everything Vulert holds for com.browserup:browserup-proxy?
Questions
About com.browserup:browserup-proxy 1.2.0
Is com.browserup:browserup-proxy 1.2.0 vulnerable?
Yes. 1 vulnerability in the Vulert database cover com.browserup:browserup-proxy 1.2.0: 0 critical, 1 high, 0 medium and 0 low. The upgrade Vulert recommends is 2.1.2, and each entry above names the fixed version to move to.
Which version of com.browserup:browserup-proxy should I use instead of 1.2.0?
2.1.2 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 1.2.0 the latest release of com.browserup:browserup-proxy?
No. 1.2.0 was published 03 Jun 2019, 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 com.browserup:browserup-proxy for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the com.browserup:browserup-proxy version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.