If a configured path contains non-ASCII characters, a local attacker capable of creating files or folders in accessible locations can cause the server to load malicious files instead of intended configuration files. This may lead to:

• Authentication bypass via a rogue certificate authority.
• Interception and modification of object store messages.
• Exfiltration of ACME-managed private keys.
• Denial of service by preventing TLS ports from starting.

This vulnerability is not present in default configurations, as default settings use ASCII file names and disable features like client-certificate authentication, the object store, and ACME. Linux builds are not affected.