We are pleased to announce the latest stable release of Jellyfin, version 10.11.10! This minor release brings several bugfixes to improve your Jellyfin experience. As always, please ensure you take a full backup before upgrading!
You can find the full changelogs on the GitHub releases for the server repository and the web repository.
Release prepared with <3 by @joshuaboniface, the rest of the Jellyfin team, and contributors like you.
Happy watching!
As always, please ensure you stop your Jellyfin server and take a full backup of your metadata/configs before upgrading!
🚀 Jellyfin Server 10.11.10
🔒 Security
Fix GHSA-f47c-m7gr-q92j, by @Shadowghost Fix GHSA-jg92-mrxq-vv75, by @Shadowghost Fix GHSA-wwwm-px48-fpvq, by @Shadowghost📈 General Changes
Fix stale UserData cache [PR #15048], by @theguymadmax Fix/user manager collation [PR #16906], by @JPVenson🚀 Jellyfin Web 10.11.10
🔒 Security
Fix xss in listview [PR #7955], by @thornbillYay, Jellyfin!! :D
I just installed and fixed my setup yesterday. Sigh Guess the backup part is irelevant at least.
Should I worry that this is essentially a security update for vulnerabilities that are (intentionally?) not explained?
Why should you? They got fixed?
Often security vulnabilities do not go public the moment the got discovered. There are often wirhheld to only the researcher and the team or only a few ppl of the team the vulnabilitie related to.
This is to give system admins time to update and patch their systems before more details and the research gets released.
Responsible disclosure is one of those procedures.
I would update. In a few months those will be published I’m sure.
It’s disappointing that we’ve come to this because when you deal with pcidss or some other regulation frameworks you need to patch or eliminate vulnerabilities and when patching is not feasible you can generally make tweaks to eliminate the attack. I like to apply the same level of hardening to all of my servers and services anyway… but without details published I have no idea what the vector is or if the vulnerability even applies in my environment - it’s not uncommon for one to require very specific configuration to either be vulnerable or protected.
Easy enough to smash update in this case but still.
I would update. In a few months those will be published I’m sure.
I mean the patches themself are there and visible. The only thing that is not there is the explenation on what the vulnabilitie is/was.
Just in time for my first deployment.
