Vulnerability · CVE-2025-54799
Let's Encrypt client and ACME library written in Go (Lego).
Published Aug 7, 2025 · catalog updated Aug 7, 2025 · Let's Encrypt client and
Check this week
CVE-2025-54799 is not in CISA KEV. FIRST estimates a 22.00% chance of exploitation in the next 30 days. Check whether you run Let's Encrypt client and.
Gaps on this record
- The stored product name is a package slug. The name on this page is taken from the title (Let's Encrypt client and).
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- Severity
- Low2.3
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 22.00%
- Remediation
- Version ranges on file
- Affected products
- vendor go-acme lego < 4.25.2
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 d
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- vendor go-acme lego < 4.25.2< 4.25.2
How to fix CVE-2025-54799
Recommended remediation
Affected version ranges suggest a fixed boundary. Verify against the vendor advisory for your release.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
CVE-2025-54799 is not in CISA KEV. FIRST estimates a 22.00% chance of exploitation in the next 30 days. Check whether you run Let's Encrypt client and.
Which versions are affected?
Compare what you have installed with go-acme lego < 4.25.2 < 4.25.2. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
No weakness class is stored. EPSS 22.00%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Aug 7, 2025 · EUVD
Detected
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
Aug 7, 2025 · EUVD
Updated
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
Sources
- CVE.orgVulnerability recordCVE-2025-54799
Official CVE identifier
cve.org - EUVDVulnerability recordEUVD-2025-23896
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
euvd.enisa.europa.eu
References
Freshness
Last verified in this catalog Aug 7, 2025. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.