Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Lego does not enforce HTTPS

CVSS 4.0 2.3 LOWEUVD CVSS 4.0 2.3 CVSS 4.0 · [email protected] · Secondary 2.3 LOWCVSS_V4 Publisher rating LOWFixed by github.com/go-acme/lego/v4 4.25.2osv · severity unknownFixed by github.com/go-acme/lego/v4 4.25.2KEV status unknown

cve-program · CVE-2025-54799

Published

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.

Read the publisher's advisory

euvd · EUVD-2025-23896

Published

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.

Read the publisher's advisory

nvd · CVE-2025-54799

Published

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.

Read the publisher's advisory

osv · GHSA-q82r-2j7m-9rv4

Published

## Summary It was discovered that 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. ## Details 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. This is stated in 6.1 of RFC 8555: [https://datatracker.ietf.org/doc/html/rfc8555#section-6.1](https://datatracker.ietf.org/doc/html/rfc8555#section-6.1) > Each ACME function is accomplished by the client sending a sequence > of HTTPS requests to the server [[RFC2818](https://datatracker.ietf.org/doc/html/rfc2818)], carrying JSON messages > [[RFC8259](https://datatracker.ietf.org/doc/html/rfc8259)]. Use of HTTPS is REQUIRED. Each subsection of [Section 7](https://datatracker.ietf.org/doc/html/rfc8555#section-7) > below describes the message formats used by the function and the > order in which messages are sent. 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 the library user accidentally inputs an HTTP URL, or the CA similarly misconfigures its endpoints, this will cause the relevant parts of the protocol to be performed over HTTP. This can result, at the very least, in a lost of privacy of the request/response details, such as account and request identifiers (which could be intercepted by an attacker in a privileged network position). We did not investigate whether other more serious threats could result from the ability to impersonate a CA for some of the protocol requests, but enforcing HTTPS usage is definitely the safe choice. ## Reproducing This is illustrated in the attached http_acme_test.go. Since it uses private field Core.directory, this test must be placed inside the source directory of https://github.com/go-acme/lego/v4/acme/api to run. Please note that this only checks getting the directory and creating a new account, but other ACME functions are likely impacted as well, such as creating orders, getting and checking order authorizations. <details> ```go package api import ( "crypto/ecdsa" "crypto/elliptic" "crypto/rand" "fmt" "net/http" "strings" "testing" "time" "github.com/go-acme/lego/v4/acme" ) const letsEncryptURLHTTP = "http://acme-v02.api.letsencrypt.org/directory" const letsEncryptURLHTTPS = "https://acme-v02.api.letsencrypt.org/directory" func changeToHTTP(url *string) { if strings.HasPrefix(*url, "https:") { *url = "http" + (*url)[len("https"):] } } func changeToHTTPS(url *string) { if strings.HasPrefix(*url, "http:") { *url = "https" + (*url)[len("http"):] } } func TestHTTPURLs(t *testing.T) { privateKey, err := ecdsa.GenerateKey(elliptic.P256(), rand.Reader) if err != nil { t.Fatalf("error generating a private key: %v", err) } func() { t.Log("testing that Discover enforces https") _, err := New(&http.Client{ Transport: &httpsOnlyRoundTripper{inner: http.DefaultTransport}, Timeout: 20 * time.Second, }, "", letsEncryptURLHTTP, "", privateKey) if err != nil { t.Errorf("New error: %v", err) } }() core, err := New(&http.Client{ Transport: &httpsOnlyRoundTripper{inner: http.DefaultTransport}, Timeout: 20 * time.Second, }, "", letsEncryptURLHTTPS, "", privateKey) if err != nil { t.Fatalf("New error: %v", err) } func() { t.Log("testing that account creation enforces https") // Simulate a misconfigured CA that gives out HTTP directory URLs and when // we're done change it back to HTTPS to test the rest. changeToHTTP(&core.directory.NewAccountURL) defer changeToHTTPS(&core.directory.NewAccountURL) _, err := core.Accounts.New(acme.Account{ TermsOfServiceAgreed: true, Contact: []string{}, }) if err != nil { t.Errorf("core.Accounts.New error: %v", err) } }() _, err = core.Accounts.New(acme.Account{ TermsOfServiceAgreed: true, Contact: []string{}, }) if err != nil { t.Fatalf("core.Accounts.New error: %v", err) } } type httpsOnlyRoundTripper struct { inner http.RoundTripper } func (r *httpsOnlyRoundTripper) RoundTrip(req *http.Request) (*http.Response, error) { if req.URL.Scheme != "https" { return nil, fmt.Errorf("non-https request is being sent") } return r.inner.RoundTrip(req) } ``` </details> _

Read the publisher's advisory

osv · GO-2025-3847

Published

Github.com/go-acme/lego/v4/acme/api does not enforce HTTPS in github.com/go-acme/lego

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2025-54799

Published

lego

Vendor product

Publisher's version information

Shown as published. These rules are not interpreted as NuGet package version ranges.

{
                    "vendor": "go-acme",
                    "product": "lego",
                    "versions": [
                        {
                            "version": "< 4.25.2",
                            "status": "affected"
                        }
                    ]
                }

Original source record · Cite this exact observation · Complete original publisher JSON

euvd · EUVD-2025-23896

Published

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Aug 7, 2025, 12:04:14 AM

dateUpdated: Aug 7, 2025, 2:07:32 PM

1 related source bulletins · separate from aliases

openSUSE-SU-2025:15434-1: govulncheck-vulndb-0.0.20250811T192933-1.1 on GA media

CVE-2021-21411 · CVE-2025-44779 · CVE-2025-50738 · CVE-2025-53534 · CVE-2025-53942 · CVE-2025-54386 · CVE-2025-54388 · CVE-2025-54410 · CVE-2025-54424 · CVE-2025-54576 · CVE-2025-54799 · CVE-2025-54801 · CVE-2025-54996 · CVE-2025-54997 · CVE-2025-54998 · CVE-2025-54999 · CVE-2025-55000 · CVE-2025-55001 · CVE-2025-55003 · CVE-2025-5999 · CVE-2025-6000 · CVE-2025-6004 · CVE-2025-6011 · CVE-2025-6013 · CVE-2025-6014 · CVE-2025-6015 · CVE-2025-6037 · CVE-2025-7195 · CVE-2025-8341

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

nvd · CVE-2025-54799

Published

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Deferred

Weakness classifications: CWE-319

Original publisher date fields

published: 2025-08-07T01:15:26.370

lastModified: 2026-06-17T09:40:43.547

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GHSA-q82r-2j7m-9rv4

Published

github.com/go-acme/lego

Go

SEMVER · introduced 0 → last_affected 4.25.1

github.com/go-acme/lego/v3

Go

SEMVER · introduced 0 → last_affected 4.25.1

github.com/go-acme/lego/v4

Go

SEMVER · introduced 0 → fixed 4.25.2

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GO-2025-3847

Published

github.com/go-acme/lego/v4

Go

SEMVER · introduced 0 → fixed 4.25.2

Original source record · Cite this exact observation · Complete original publisher JSON

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 16 Nov 11:47 UTC · 274 of 275 readable · 250 fully read · 20 waiting for GitHub's hourly limit · documentation 469/469 current