>It will take some time before there are reliable exploits, and they may require running on infra close to the target.
Think that you're targeting KeyCloak and have a semi-working exploit that dumps some parts of heap memory with live tokens. You can go after 100s of banks globally, whole Tesco infra, dozens of gov.uk websites including HMRC and Home Office, azure containers... you know, anyone mature not do write their own auth server: https://www.shodan.io/search?query=keycloak
keycloak, jira, confluence, kafka -- lots of potential for fuckery.
a bunch of big attacks got in through secondary paths like that, e.g. the Jag-Land-Rover hacks in the UK started in jira with stolen creds and expanded laterally though PM, tracking, and documentation tools.
> anyone mature not do write their own auth server
Anyone mature enough not to write their own auth server? I agree with the sentiment.
Just want to nitpick that keycloak is an extremely well auth solution for small to medium sized business as well (at least internally, especially if people spawn a new vibe coded app every other minute).
Also if you are the default Windows shop that uses the common domain controller infra. And no, Entra is not an alternative if you want any client credential flows because then the largest risk becomes your internet connection.
https://www.keycloak.org/2026/11/java4shell-vulnerability-cv...