https://patchthecve.com/CVEs with upgrade or downgrade fix stepshttps://patchthecve.com/cve/CVE-2019-9150.htmlhttps://patchthecve.com/cve/CVE-2019-9150.htmlWed, 17 Jun 2026 02:43:09 +0000MEDIUM 5.3: Mailvelope prior to 3.3.0 does not require user interaction to import public keys shown on web page. This functionality can be tricked to either hide a key import from the user or obscure which key was imported.https://patchthecve.com/cve/CVE-2019-9149.htmlhttps://patchthecve.com/cve/CVE-2019-9149.htmlWed, 17 Jun 2026 02:43:09 +0000MEDIUM 6.5: Mailvelope prior to 3.3.0 allows private key operations without user interaction via its client-API. By modifying an URL parameter in Mailvelope, an attacker is able to sign (and encrypt) arbitrary messages with Mailvelope, assuming the private key password is cached. A second vulnerability allows ahttps://patchthecve.com/cve/CVE-2019-9148.htmlhttps://patchthecve.com/cve/CVE-2019-9148.htmlWed, 17 Jun 2026 02:43:09 +0000MEDIUM 4.3: Mailvelope prior to 3.3.0 accepts or operates with invalid PGP public keys: Mailvelope allows importing keys that contain users without a valid self-certification. Keys that are obviously invalid are not rejected during import. An attacker that is able to get a victim to import a manipulated key couhttps://patchthecve.com/cve/CVE-2019-9147.htmlhttps://patchthecve.com/cve/CVE-2019-9147.htmlWed, 17 Jun 2026 02:43:09 +0000MEDIUM 4.3: Mailvelope prior to 3.1.0 is vulnerable to a clickjacking attack against the settings page. As the settings page is intended to be accessible from web applications, the browser's extension isolation mechanisms are disabled (web_accessible_resources). Mailvelope implements additional measures to prev