CVE-2025-54472VulnerabilityPublished 14 Aug 2025Updated 5 Nov 2025

redis protocol parser · Unlimited Memory Allocation

Source GCVE Database

Compare

Authoritative record:CVE-2025-54472· High 7.5

Not known to be exploited · CVSS 7.5 High · fixed in 1.14.1 : patch affected systems soon.

Data as of 4 Nov 2026, 17:56 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CISA-ADP	CVSS 3.1	7.5

Patch: Available – fixed in 1.14.1

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 14 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 4 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-fgf7-x5pv-vcc3

What to do

AI-suggested

Upgrade Apache bRPC to version 1.14.1, which contains the official fix for this vulnerability. Alternatively, apply the patch available at https://github.com/apache/brpc/pull/3050 manually. Note that the patch limits the maximum memory allocation size to 64MB by default, which can be adjusted via the gflag redis_max_allocation_size if larger Redis requests or responses are expected. No other actions are required beyond applying the fix or patch.

Description

A vulnerability in Apache bRPC's Redis protocol parser allows attackers to cause unlimited memory allocation leading to service crashes. This affects all versions prior to 1.14.1, including version 1.14.0 due to an incomplete fix. The issue arises from improper handling of integer values read from the network, which can cause integer overflow and excessive memory allocation. This can be exploited to perform denial-of-service attacks when bRPC is used as a Redis server or client with untrusted sources. The issue is fixed in version 1.14.1, and a patch is available to limit memory allocation size with a default maximum of 64MB.

Impact

Successful exploitation results in denial-of-service (DoS) by crashing the bRPC service through excessive memory allocation. This affects availability but does not impact confidentiality or integrity. The vulnerability can be triggered remotely without authentication by sending malicious network packets to the Redis protocol parser in bRPC.

Summary

The Apache bRPC Redis protocol parser allocates memory for arrays or strings based on integer values received from the network. If these integers are excessively large, the parser attempts to allocate an unlimited amount of memory, causing a bad alloc error and crashing the service. Version 1.14.0 attempted to mitigate this by limiting allocation size, but due to integer overflow in the limitation check, it remains vulnerable. Versions prior to 1.14.1 are affected. Attackers can exploit this by sending specially crafted packets to cause denial-of-service. The vulnerability is addressed in bRPC 1.14.1 by properly limiting memory allocation size, with a configurable limit (default 64MB).

CWE-190Integer Overflow or Wraparound (opens in a new tab)
Base weaknessLikelihood of exploit: Medium
The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.
Requirements
Ensure that all protocols are strictly defined, such that all out-of-bounds behavior can be identified simply, and require strict conformance to the protocol.
Requirements · Language Selection
Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V5.4.3 (opens in a new tab)
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
Attack patterns
Forced Integer Overflow (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 4 Nov 2026, 17:56 UTC

WeaknessesCWE-190

Technical details

References

Community reviews

Related threats