CVE-2025-53604VulnerabilityPublished 5 Jul 2025Updated 8 Jul 2025

CVE-2025-53604: pimeys web-push · Improper Handling of Length Parameter Inconsistency

Affects pimeys web-pushSource CVE Database V5

Not known to be exploited · CVSS 4.0 Medium : upgrade to 0.10.3 when convenient.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

4.0Medium

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

EPSS: 0.4% chance of exploitation in 30 days – higher than 35% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 0.10.3

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

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

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: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
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: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
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: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 5 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 2026-10-26.

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.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC 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.

What to do

Upgrade pimeys/web-push to 0.10.3.

Affected software

Product	Affected	Fixed in
crates.iopimeys/web-push`pkg:cargo/pimeys/web-push`Other threats	Affected <0.10.3	Fixed in 0.10.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should take the following specific steps to mitigate this vulnerability: 1) Upgrade the pimeys web-push crate to version 0.10.3 or later as soon as it becomes available, as this version addresses the improper handling of the Content-Length header. 2) Implement input validation and sanity checks on HTTP headers, particularly Content-Length, to reject or limit excessively large values before processing. 3) Employ resource usage monitoring and limits at the application and operating system levels to detect and prevent abnormal memory consumption patterns indicative of exploitation attempts. 4) Use Web Application Firewalls (WAFs) or network-level filtering to block suspicious requests with unusually large Content-Length headers. 5) Conduct regular code audits and dependency reviews to identify and remediate similar length parameter handling issues. 6) Prepare incident response plans to quickly address potential DoS events affecting web-push services. These measures go beyond generic advice by focusing on proactive validation, resource control, and layered defense specific to the nature of this vulnerability.

Description

The web-push crate before 0.10.3 for Rust allows a denial of service (memory consumption) in the built-in clients via a large integer in a Content-Length header.

Impact

For European organizations utilizing the pimeys web-push crate in their Rust-based applications, this vulnerability poses a risk of denial of service through memory exhaustion. Such DoS attacks can disrupt web push notification services, potentially impacting customer communications, real-time alerts, or other critical notification mechanisms. This disruption could degrade user experience and operational continuity, especially for service providers relying on push notifications for timely information delivery. While the vulnerability does not compromise data confidentiality or integrity, the availability impact can lead to service outages, affecting business operations and customer trust. Organizations with high reliance on web-push notifications in sectors such as finance, healthcare, or public services may face operational risks. Additionally, the medium CVSS score suggests that while the threat is not critical, it should not be ignored, particularly in environments where resource constraints or high availability are critical. The lack of known exploits reduces immediate risk but does not eliminate the need for proactive mitigation.

CWE-130Improper Handling of Length Parameter Inconsistency (opens in a new tab)
Base weakness
The product parses a formatted message or structure, but it does not handle or incorrectly handles a length field that is inconsistent with the actual length of the associated data.
Implementation
When processing structured incoming data containing a size field followed by raw data, ensure that you identify and resolve any inconsistencies between the size field and the actual size of the data.
Implementation
Do not let the user control the size of the buffer.
Implementation
Validate that the length of the user-supplied data is consistent with the buffer size.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
Attack patterns
Buffer Overflow via Parameter Expansion (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

Affected software

Description

AI analysisMachine-generated, updated 14 Jul 2025, 21:25 UTC

WeaknessesCWE-130

Technical details

References

Community reviews

Related threats