Description
Let's Encrypt client and ACME library written in Go (Lego). In versions 4.25.1 and below, the github.com/go-acme/lego/v4/acme/api package (thus the lego library and the lego cli as well) don't enforce HTTPS when talking to CAs as an ACME client. Unlike the http-01 challenge which solves an ACME challenge over unencrypted HTTP, the ACME protocol requires HTTPS when a client communicates with the CA to performs ACME functions. However, the library fails to enforce HTTPS both in the original discover URL (configured by the library user) and in the subsequent addresses returned by the CAs in the directory and order objects. If users input HTTP URLs or CAs misconfigure endpoints, protocol operations occur over HTTP instead of HTTPS. This compromises privacy by exposing request/response details like account and request identifiers to network attackers. This was fixed in version 4.25.2.
INFO
Published Date :
2025-08-07T00:04:14.718Z
Last Modified :
2025-08-07T14:07:32.104Z
Source :
GitHub_M
AFFECTED PRODUCTS
The following products are affected by CVE-2025-54799 vulnerability.
| Vendors | Products |
|---|---|
| Lego Project |
|
REFERENCES
Here, you will find a curated list of external links that provide in-depth information to CVE-2025-54799.
