Critical Keycloak Vulnerability (CVSS 9.1) - CVE-2026-18963 (access.redhat.com)
from exu@feditown.com to selfhosted@lemmy.world on 25 Aug 10:48
https://feditown.com/post/3464667

Update your Keycloak

For community, version 26.7.2 has the fix:
www.keycloak.org/2026/08/keycloak-2672-released

#selfhosted

threaded - newest

plateee@piefed.social on 25 Aug 12:14 collapse

This one is bad - unauthenticated user account take over.

If you’re like me and only using it internally on a homelab, the risks are lessened, but if you expose keycloak to by the Internet - boy howdy

exu@feditown.com on 25 Aug 13:05 next collapse

Especially in an enterprise environment where plenty of people use first.lastname@company

iamthetot@piefed.ca on 25 Aug 13:54 collapse

Out of curiosity, what is the advantage of using something like this on LAN only?

Dunstabzugshaubitze@feddit.org on 25 Aug 14:11 next collapse

for many people homelabbing is a way to gain knowledge they can use on the job.

other than that: proper single sign on across your services is nice even if you don’t expose them to anybody else.

possiblylinux127@lemmy.zip on 25 Aug 14:31 next collapse

Not being impacted by security issues like these for one

B0rax@feddit.org on 25 Aug 14:31 next collapse

It will still sync to all devices. And if you have an always on vpn to your home network, there really is no need to expose it to the public

NarrativeBear@lemmy.world on 25 Aug 17:29 next collapse

When you host something on LAN only you are not exposing the service to the wider internet directly.

This means someone would need access to your LAN or local area network first (such as your WiFi password) before being able to reach said service.

Now when you expose something directly to the internet, in a way that for example it displays a publicly accessible webpage, it makes it easier for anyone to reach that webpage, and potentially figure out your login and password information through brute force. Or some other type of exploit that allows full bypass of the login credentials.

Some self-hoster’s choose to keep their “more sensitive” services on the LAN only, and then use a VPN (that’s hosted privately) to access their LAN remotely from anywhere in the world.

With a VPN hosted on your LAN it provides a good layer of security as someone would first need to have access to your VPN to then potentially try and get access into your services.

iamthetot@piefed.ca on 25 Aug 18:30 collapse

I appreciate you taking the time to write this out, but I knew all of that and didn’t really address the question. I was asking why the commenter above mine was using an auth service, like Keycloak, on LAN.

It has been answered a few times, thanks.

NarrativeBear@lemmy.world on 25 Aug 18:57 collapse

No worries, not sure how I misunderstood the question, but hopefully it helps someone else out who’s getting into self-hosting.

plateee@piefed.social on 26 Aug 00:38 collapse

For me, I have multiple OIDC compatible systems (Proxmox, Netbox, Synology, Zabbix, Vault, etc).

So keycloak offers a SSO option to make my life easier with a single account to worry about instead of individual ones.

Plus MFA because it’s cool?