Can confirm — hit the same issue on Debian 10 (buster, EOL) and Debian 12 (bookworm, ca-certificates 20230311+deb12u1, latest available) validating a certificate issued by SSL.com through "SSL.com TLS Issuing RSA CA R1", chaining to the same missing "SSL.com TLS RSA Root CA 2022" root. Worked around it the same way — manually adding the root cert and running update-ca-certificates. This is affecting production TLS validation for our infrastructure (client-facing services), not just a corner case. Would be good to see this root added to ca-certificates in stable, same as requested in the original report.
