Urgent.News

What's breaking now, across thousands of outlets.

Tech

Keycloak CVE-2026-18963: Unauthenticated Password Reset Hands Over Any Account, Including Admins

TL;DR what: Red Hat and the Keycloak project patched CVE-2026-18963, an improper state validation bug in the reset-credentials authentication flow that lets an unauthenticated remote attacker jump straight to the password update phase without the emailed action token. impact: Successful exploitation is a full takeover of any account on the server, including administrative accounts, and everything…

Red Hat and the Keycloak project have patched a critical vulnerability, CVE-2026-18963, that allows an unauthenticated attacker to reset any account's password, including those of administrators, without needing an emailed action token or any user interaction. This flaw is caused by an improper state validation issue within the reset-credentials authentication flow used by Keycloak.

The bug enables an attacker to craft a request to the reset-credentials endpoint, advancing the authentication session directly to the password update phase without the necessary email token. As a result, the attacker gains full control over any account on the server, including administrative accounts, and any systems protected by Keycloak as the identity provider.

The vulnerability has been rated with a CVSS score of 9.1, indicating a high severity. To mitigate the risk, organizations running Keycloak or Red Hat builds of Keycloak with the forgotten-password feature enabled should upgrade to version 26.7.2 (released August 19, 2026) or Red Hat builds of Keycloak 26.4.15 and 26.6.6. As a temporary mitigation before upgrading, organizations can disable the Forgot password feature in all realms through the Keycloak administration console.

If immediate patching is not possible, this setting must be applied to every realm to prevent exploitation. The vulnerability affects any organization running Keycloak or a Red Hat build of Keycloak with the forgotten-password feature enabled and reachable through an internet-accessible login endpoint.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

This story

This is one outlet's version. Read the fullest account.

Read the original at dev.to →

More in Tech

How Kafka Saved a Failing System -The Story of Arjun & Meera

Modern systems run on data in the form of fast, real-time, continuous streams. But what happens when your system grows faster than your architecture can handle?

  • SwiftKart's orders surged from 4,000 to 40,000 daily in two months, causing system chaos.
  • DevOps engineer Meera observed red indicators of distress on the monitoring dashboard.

Meteor 3.5: accounts-express Brings Meteor Accounts to Express

Bring authenticated Meteor users into Express routes without building a second session system. Meteor 3 is modernizing the framework in two complementary ways: adopting proven tools from the wider…

  • accounts-express package integrates Meteor Accounts with Express routes.
  • Middleware reads Meteor login token, attaches user ID to req.userId.
  • Enables authenticated requests to Express routes using authenticated fetch.

More from Monday 24 August →