122
AI Agent Uncovers 21 Zero-Days in FFmpeg; Chrome Patches Record 429 Bugs
(thehackernews.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 07 Jun 2026
122 points (84.3% liked)
Technology
89488 readers
4411 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 3 years ago
MODERATORS
With a competently crafted payload, you could perhaps get in via someone's transcoding pipeline.
Does nobody isolate ffmpeg and friends from their application?
I can't imagine you'd have much fun breaking into a container that terminates the moment the original ffmpeg stops, or over-runs its max execution time..
Container escapes do exist, and they have shared kernel with the host
If you're running rootless containers, it's less of a concern. I'm trying to move all of my public containers to podman for this reason
Sure, you'd need a second exploit to escalate from there.
ffmpeg is expected to run for extended periods of time, given its use in transcoding.