This issue was resolved by upgrading to Aspose version 24.12.0.

@Hoodlum, I don't think this is what you're dealing with, but I chose to address the security vulnerability reference in Aspose v 24.12.0's reference to System.Security.Cryptography.Pkcs 8.0 with a direct reference:

<PackageReference Include="System.Security.Cryptography.Pkcs" Version="9.*" />

This override passed our test suite, including the use of password protection (which did not work under Aspose 21.12.0).