Frigate NVR Critical RCE Vulnerability
from Dust0741@lemmy.world to selfhosted@lemmy.world on 28 Jan 2026 19:13
https://lemmy.world/post/42328318
from Dust0741@lemmy.world to selfhosted@lemmy.world on 28 Jan 2026 19:13
https://lemmy.world/post/42328318
Severity 9.1 - Authenticated user container escape.
The latest release fixes this.
See details here
threaded - newest
This is why you don’t expose services to the Internet, especially with weak or no authentication.
I’m not sure why anyone would want to expose Frigate of all things to the open internet.
So they could view their cameras while they’re away?
That’s my use case. But my frigate-box is strictly behind firewall and I access it over wireguard when I’m away.
I second this. I have notifications set up via homeassistant, and if I want to view a feed I just VPN in
There are far better, more secure ways to do this. You could use a reverse proxy. You could use tailscale. You could use wireguard.
The last thing you should do is open Frigate’s port to the net.
Just answering the question you asked.
I know, but it seemed like there was confusion about my intended point, which is that you should never expose it to the open internet. It wasn’t a question I really intended to be answered since I know that was their intention. My confusion is why do that when there are secure alternatives, some of which are easier than opening a port.
Inexperience or lack of effort. I don’t know any method easier than just opening the port.
“This vulnerability is only exploitable by an administrator or users who have exposed their Frigate install to the open internet with no authentication which allows anyone full administrative control.” High, but not critical