Skip to content
Fencer Intel
low 2.3

CVE-2025-54799 json

Lego does not enforce HTTPS

published last yr. modified last mo. also GHSA-q82r-2j7m-9rv4 , GO-2025-3847 , EUVD-2025-23896

cvss
2.3
version 4.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 17%
public exploits
0
none known

Summary

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.

Patch / fix

  • go github.com/go-acme/lego/v4 4.25.2
  • golang-github-xenolf-lego Debian 14 4.35.2-1

debian advisories DEBIAN-CVE-2025-54799

  • govulncheck-vulndb SLE Module for Package Hub 15 SP6, openSUSE Leap 15.6 0.0.20250814T182633-150000.1.98.1

suse advisories SUSE-SU-2025:02912-1

  • govulncheck-vulndb openSUSE Tumbleweed 0.0.20250811T192933-1.1

opensuse advisories openSUSE-SU-2025:15434-1

Is CVE-2025-54799 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2025-54799 updated cvss 5.3

github.com/go-acme/lego: Lego: Unenforced HTTPS Communication Vulnerability

  • Red Hat OpenShift Dev Spaces devspaces/traefik-rhel9, devspaces/dashboard-rhel9, devspaces/configbump-rhel9, devspaces/imagepuller-rhel9, devspaces/devspaces-rhel9-operator, devspaces-tech-preview/jetbrains-ide-rhel9
    affected: workaround, no fix planned “Will not fix”
  • Red Hat OpenShift Dev Spaces devspaces/traefik-rhel8
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.26% chance of exploitation in the next 30 days, higher than 17% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 4.0 2.3 CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:U
CNA 4.0 2.3 CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:U/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Affected packages

ecosystem package affected fixed in
go github.com/go-acme/lego
<=4.25.1
 no fix listed
go github.com/go-acme/lego/v3
<=4.25.1
 no fix listed
go github.com/go-acme/lego/v4
<4.25.2
4.25.2

Affected products

  • go-acme lego

Classification

Weakness
  • CWE-319 Cleartext Transmission of Sensitive Information

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.