CVE-2019-25072: Due to support of Gzip compression in request bodies, as well as a lack of limiting response body sizes, a mal

Q: How do I fix CVE-2019-25072?

tendermint: upgrade to 0.31.1. Exact commands for each OS are on this page.

Q: Is CVE-2019-25072 being exploited?

CVE-2019-25072 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2019-25072 affect?

CVE-2019-25072 affects tendermint. Severity is high (CVSS 7.5). Due to support of Gzip compression in request bodies, as well as a lack of limiting response body sizes, a malicious server can cause a client to consume a significant amount of system resources, which may be used as a denial of service vec

Q: How urgent is CVE-2019-25072?

Priority 48/100. High severity; Remotely exploitable, no login, no user action

This month

HIGH 7.5REMOTEUPGRADE

CVE-2019-25072 is a high-severity flaw (CVSS 7.5) affecting tendermint. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Due to support of Gzip compression in request bodies, as well as a lack of limiting response body sizes, a malicious server can cause a client to consume a significant amount of system resources, which may be used as a denial of service vector.

Why this priority

High severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.2% (top 31%)
CISA exploited list	No
Weakness	CWE-400
Published	2022-12-27
Last modified	2026-06-17

Publisher (CNA): Go Project · Vendor: tendermint

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2022-12-27 22:15 UTCPublished CVE record published
2026-06-17 02:31 UTCUpdated Record last modified

tendermint tendermint UPGRADE

Affected: < 0.31.1

Fixed in: 0.31.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy tendermint || rpm -q tendermint || tendermint --version

2. UPGRADE to 0.31.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade tendermint

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade tendermint

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2019-25072?

tendermint: upgrade to 0.31.1. Exact commands for each OS are on this page.

Is CVE-2019-25072 being exploited?

CVE-2019-25072 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2019-25072 affect?

CVE-2019-25072 affects tendermint. Severity is high (CVSS 7.5). Due to support of Gzip compression in request bodies, as well as a lack of limiting response body sizes, a malicious server can cause a client to consume a significant amount of system resources, which may be used as a denial of service vec

How urgent is CVE-2019-25072?

Priority 48/100. High severity; Remotely exploitable, no login, no user action

Related CVEs

CVE-2021-21271 MEDIUM 6.5 UPGRADE Tendermint Core is an open source Byzantine Fault Tolerant (BFT) middleware that takes a state transition mach
CVE-2020-5303 LOW 3.1 UPGRADE Tendermint before versions 0.33.3, 0.32.10, and 0.31.12 has a denial-of-service vulnerability
CVE-2020-15091 MEDIUM 6.5 UPGRADE TenderMint from version 0.33.0 and before version 0.33.6 allows block proposers to include signatures for the

References

← Back to latest CVEs