Hey @Suffocation,
Good report, and the checks line up with how the image is built. Facts first, then where it goes.
ca-certificates
Pi images are built from Raspbian’s plain bookworm suite. The sources.list on your player is exactly what the build writes:
deb http://archive.raspbian.org/raspbian/ bookworm main contrib non-free rpi
There is no security suite because Raspbian does not publish one; it merges Debian’s security uploads into bookworm/main with a lag. That lag is why your 24 March image has 20230311+deb12u1 while Raspbian main is already serving 20250419~deb12u1 today. Debian’s 20250419~deb12u2, the one that drops emSign ECC Root CA - G3 and Comodo AAA Certificate Services, went into bookworm-security on 20 October and has not reached Raspbian main yet. When it does, the next Pi image picks it up without a build change, because the Pi recipe runs apt-get upgrade against Raspbian during the build. The timing of that merge is Raspbian’s, not Volumio’s.
The x86, armv7 and armv8 images are a different story: they use deb.debian.org bookworm only, and Debian’s plain bookworm still carries 20230311+deb12u1. Those need bookworm-security adding in scripts/rootfs/prepare.sh (there is a USE_EXTRA_REPOS block in that file already, Debian-only and off by default) or the deb sideloaded. That is a PR-sized change.
One caution on the fix itself: removing AAA Certificate Services also drops any legitimate chain that still terminates there. Ubuntu, who removed the same two roots, call that unlikely but possible. It wants checking against the endpoints that matter before it ships in an image.
Node
The backend runs on Node 20.5.1, a Volumio-built static package, started as plain /usr/bin/node /volumio/index.js. So your reading is right: compiled-in root list, no --use-openssl-ca.
Node 20 reached end of life on 30 April 2026. The upstream fix, the NSS 3.131.1 root list plus rejection of any chain containing the eight public keys, was released today in 22.23.4, 24.22.1 and 26.12.1. There will be no 20.x release with it. That leaves three routes: a major bump to 22 or 24 (node_modules rebuilt, native modules, a new static armhf build), rebuilding the 20.5.1 package with the new root list and the backported key block, or adding --use-openssl-ca to volumio.service so Node follows the system store, which only helps once the ca-certificates update is in and changes trust behaviour for every plugin at once. Which of those and when is a Volumio release decision. I will not guess a date on a forum.
The rest
curl uses the system store, so the package update covers it. go-librespot: Go on Linux reads /etc/ssl/certs by default rather than bundling roots, so the package update is the first thing that matters there too; the compile-time key block arrived in Go 1.27.3 and 1.26.10 and needs a rebuild.
Positioning
This is a home audio player, not an ISA firewall. As you say yourself, the only path that matters needs someone already sitting between the Pi and the internet, and the calls on that path are update checks, plugin downloads and MyVolumio. It is also open source. The build system is GitHub - volumio/volumio-os: Volumio OS Build System · GitHub, the two files above are scripts/rootfs/prepare.sh and recipes/configurations/config.sh, and the static Node package lives in volumio3-os-static-assets. A PR for the Debian-side sources change is welcome and is the fastest way to move that part. If you want the package on your own player sooner, apt will install whatever Raspbian is serving on the day; that is a per-device measure, not a fix for the image.
Kind Regards,