https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 05 Oct 2026 04:11:32 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-249277 EUVD-2026-249277 https://cve.radiocsirt.org/vuln/euvd-2026-249277 https://cve.radiocsirt.org/vuln/fkie_cve-2025-54799 <p>Let&#39;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&#39;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.</p> <p>Let&#39;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&#39;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.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2025-54799 https://cve.radiocsirt.org/vuln/ghsa-q82r-2j7m-9rv4 <p><strong>Affected:</strong> Go: github.com/go-acme/lego, Go: github.com/go-acme/lego/v3, Go: github.com/go-acme/lego/v4</p> <p>## Summary</p> <p>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&#39;t enforce HTTPS when talking to CAs as an ACME client.</p> <p>## Details</p> <p>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)</p> <p>&gt; Each ACME function is accomplished by the client sending a sequence &gt; of HTTPS requests to the server [[RFC2818](https://datatracker.ietf.org/doc/html/rfc2818)], carrying JSON messages &gt; [[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) &gt; below describes the message formats used by the function and the &gt; order in which messages are sent.</p> <p>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.</p> <p>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 an…</p> <p><strong>Affected:</strong> Go: github.com/go-acme/lego, Go: github.com/go-acme/lego/v3, Go: github.com/go-acme/lego/v4</p> <p>## Summary</p> <p>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&#39;t enforce HTTPS when talking to CAs as an ACME client.</p> <p>## Details</p> <p>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)</p> <p>&gt; Each ACME function is accomplished by the client sending a sequence &gt; of HTTPS requests to the server [[RFC2818](https://datatracker.ietf.org/doc/html/rfc2818)], carrying JSON messages &gt; [[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) &gt; below describes the message formats used by the function and the &gt; order in which messages are sent.</p> <p>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.</p> <p>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 an…</p> https://cve.radiocsirt.org/vuln/ghsa-q82r-2j7m-9rv4 https://cve.radiocsirt.org/vuln/opensuse-su-2025:15434-1 <p>govulncheck-vulndb-0.0.20250811T192933-1.1 on GA media</p> <p>govulncheck-vulndb-0.0.20250811T192933-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2025:15434-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-54799 <p><strong>Affected:</strong> Ubuntu:18.04:LTS: golang-github-xenolf-lego, Ubuntu:20.04:LTS: golang-github-xenolf-lego, Ubuntu:22.04:LTS: golang-github-xenolf-lego, Ubuntu:Pro:24.04:LTS: golang-github-xenolf-lego, Ubuntu:25.10: golang-github-xenolf-lego, Ubuntu:26.04:LTS: golang-github-xenolf-lego</p> <p>Let&#39;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&#39;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.</p> <p><strong>Affected:</strong> Ubuntu:18.04:LTS: golang-github-xenolf-lego, Ubuntu:20.04:LTS: golang-github-xenolf-lego, Ubuntu:22.04:LTS: golang-github-xenolf-lego, Ubuntu:Pro:24.04:LTS: golang-github-xenolf-lego, Ubuntu:25.10: golang-github-xenolf-lego, Ubuntu:26.04:LTS: golang-github-xenolf-lego</p> <p>Let&#39;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&#39;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.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-54799