<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet type="text/xsl" href="../assets/feed.xsl"?><rss version="2.0"><channel><title>PatchTheCVE: goldenfrog</title><link>https://patchthecve.com/</link><description>CVEs with upgrade or downgrade fix steps</description><item><title>CVE-2018-13133: Golden Frog VyprVPN before 2018-06-21 has a vulnerability associated with the installation process on Windows.</title><link>https://patchthecve.com/cve/CVE-2018-13133.html</link><guid>https://patchthecve.com/cve/CVE-2018-13133.html</guid><pubDate>Wed, 17 Jun 2026 01:38:54 +0000</pubDate><description>HIGH 7.8: Golden Frog VyprVPN before 2018-06-21 has a vulnerability associated with the installation process on Windows.</description></item><item><title>CVE-2018-10645: Golden Frog VyprVPN 2.12.1.8015 for Windows suffers from a SYSTEM privilege escalation vulnerability through t</title><link>https://patchthecve.com/cve/CVE-2018-10645.html</link><guid>https://patchthecve.com/cve/CVE-2018-10645.html</guid><pubDate>Wed, 17 Jun 2026 01:34:22 +0000</pubDate><description>HIGH 7.8: Golden Frog VyprVPN 2.12.1.8015 for Windows suffers from a SYSTEM privilege escalation vulnerability through the &quot;VyprVPN&quot; service. This service establishes a NetNamedPipe endpoint that allows applications to connect and call publicly exposed methods. The &quot;SetProperty&quot; method allows an attacker to c</description></item><item><title>CVE-2017-17809: In Golden Frog VyprVPN before 2.15.0.5828 for macOS, the vyprvpnservice launch daemon has an unprotected XPC s</title><link>https://patchthecve.com/cve/CVE-2017-17809.html</link><guid>https://patchthecve.com/cve/CVE-2017-17809.html</guid><pubDate>Wed, 17 Jun 2026 01:11:41 +0000</pubDate><description>HIGH 7.8: In Golden Frog VyprVPN before 2.15.0.5828 for macOS, the vyprvpnservice launch daemon has an unprotected XPC service that allows attackers to update the underlying OpenVPN configuration and the arguments passed to the OpenVPN binary when executed. An attacker can abuse this vulnerability by forcing </description></item></channel></rss>