<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet type="text/xsl" href="../assets/feed.xsl"?><rss version="2.0"><channel><title>PatchTheCVE: keycloak</title><link>https://patchthecve.com/</link><description>CVEs with upgrade or downgrade fix steps</description><item><title>CVE-2017-12161: It was found that keycloak before 3.4.2 final would permit misuse of a client-side /etc/hosts entry to spoof a</title><link>https://patchthecve.com/cve/CVE-2017-12161.html</link><guid>https://patchthecve.com/cve/CVE-2017-12161.html</guid><pubDate>Wed, 17 Jun 2026 01:02:47 +0000</pubDate><description>HIGH 8.8: It was found that keycloak before 3.4.2 final would permit misuse of a client-side /etc/hosts entry to spoof a URL in a password reset request. An attacker could use this flaw to craft a malicious password reset request and gain a valid reset token, leading to information disclosure or further attac</description></item><item><title>CVE-2014-3651: JBoss KeyCloak before 1.0.3.Final allows remote attackers to cause a denial of service (resource consumption) </title><link>https://patchthecve.com/cve/CVE-2014-3651.html</link><guid>https://patchthecve.com/cve/CVE-2014-3651.html</guid><pubDate>Wed, 17 Jun 2026 00:08:41 +0000</pubDate><description>HIGH 7.5: JBoss KeyCloak before 1.0.3.Final allows remote attackers to cause a denial of service (resource consumption) via a large value in the size parameter to auth/qrcode, related to QR code generation.</description></item><item><title>CVE-2017-12159: It was found that the cookie used for CSRF prevention in Keycloak was not unique to each session</title><link>https://patchthecve.com/cve/CVE-2017-12159.html</link><guid>https://patchthecve.com/cve/CVE-2017-12159.html</guid><pubDate>Wed, 17 Jun 2026 01:02:47 +0000</pubDate><description>HIGH 7.5: It was found that the cookie used for CSRF prevention in Keycloak was not unique to each session. An attacker could use this flaw to gain access to an authenticated user session, leading to possible information disclosure or further attacks.</description></item><item><title>CVE-2017-12158: It was found that Keycloak would accept a HOST header URL in the admin console and use it to determine web res</title><link>https://patchthecve.com/cve/CVE-2017-12158.html</link><guid>https://patchthecve.com/cve/CVE-2017-12158.html</guid><pubDate>Wed, 17 Jun 2026 01:02:47 +0000</pubDate><description>MEDIUM 5.4: It was found that Keycloak would accept a HOST header URL in the admin console and use it to determine web resource locations. An attacker could use this flaw against an authenticated user to attain reflected XSS via a malicious server.</description></item><item><title>CVE-2014-3709: The org.keycloak.services.resources.SocialResource.callback method in JBoss KeyCloak before 1.0.3.Final allows</title><link>https://patchthecve.com/cve/CVE-2014-3709.html</link><guid>https://patchthecve.com/cve/CVE-2014-3709.html</guid><pubDate>Wed, 17 Jun 2026 00:08:47 +0000</pubDate><description>HIGH 8.8: The org.keycloak.services.resources.SocialResource.callback method in JBoss KeyCloak before 1.0.3.Final allows remote attackers to conduct cross-site request forgery (CSRF) attacks by leveraging lack of CSRF protection.</description></item><item><title>CVE-2017-7474: It was found that the Keycloak Node.js adapter 2.5 - 3.0 did not handle invalid tokens correctly</title><link>https://patchthecve.com/cve/CVE-2017-7474.html</link><guid>https://patchthecve.com/cve/CVE-2017-7474.html</guid><pubDate>Wed, 17 Jun 2026 01:24:25 +0000</pubDate><description>CRITICAL 9.8: It was found that the Keycloak Node.js adapter 2.5 - 3.0 did not handle invalid tokens correctly.  An attacker could use this flaw to bypass authentication and gain access to restricted information, or to possibly conduct further attacks.</description></item></channel></rss>