The pickle module documentation makes confusing statements about secure alternatives

Documentation

The pickle module states that the xmlrpc marshaling API should be used if the users desire a safe alternative to unpickling untrusted data:

https://docs.python.org/3.14/library/pickle.html:

As our examples shows, you have to be careful with what you allow to be unpickled. Therefore if security is a concern, you may want to consider alternatives such as the marshalling API in xmlrpc.client or third-party solutions.

However, the xmlrpc module has right at the top a warning that says the following:

https://docs.python.org/3.14/library/xmlrpc.client.html#module-xmlrpc.client:

The xmlrpc.client module is not secure against maliciously constructed data. If you need to parse untrusted or unauthenticated data see XML vulnerabilities.

These two statements contradict each other and could lead users to falsely believe that they are using a safe alternative.

Commencez par la déclaration de la documentation du module pickle concernant xmlrpc.client et comparez-la avec l’avertissement de sécurité en haut de la documentation de xmlrpc.client. Révisez les indications contradictoires afin que les utilisateurs ne soient pas amenés à considérer xmlrpc.client comme sûr pour des données non fiables ; le travail est terminé lorsque les deux pages donnent des conseils de sécurité cohérents.