The issue is that a specific function is not thread safe, changing the umask for the whole process, meaning multiple uses
of libarchive in different threads could cause a race condition that could have various consequences. The issue was fixed
with added documentation that specifies that the function is not thread safe.
https://github.com/libarchive/libarchive/issues/1876
https://security-tracker.debian.org/tracker/CVE-2023-30571
The documentation change which was merged to master https://github.com/libarchive/libarchive/pull/1875