CVE-2025-53604 json
Web Push Denial of Service via malicious Web Push endpoint
published last yr. modified 4mo ago also GHSA-287x-9rff-qvcg , GHSA-fc83-9jwq-gc2m , RUSTSEC-2025-0015 , EUVD-2025-20100
- cvss
- 4.0
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 35%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- crates.io web-push 0.10.3, 0.10.4
- pimeys web-push 0.10.3
- github.com/pimeys/rust-web-push@8447ed8 commit
- github.com/pimeys/rust-web-push#68 pull request
Is CVE-2025-53604 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 FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.41% chance of exploitation in the next 30 days, higher than 35% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.0 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:N/A:L |
| GitHub | 3.1 | 4.0 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:N/A:L |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | web-push | <0.10.4 >=0.0.0-0, <0.10.3 |
0.10.4 0.10.3 |
Affected products
- pimeys web-push
Classification
References
-
github.com
/pimeys/rust-web-push/pull/68
web
-
github.com
/pimeys/rust-web-push/commit/8447ed86bf3f24629abd7022b94104bf3cd64453
web
-
rustsec.org
/advisories/RUSTSEC-2025-0015.html
web, advisory
-
crates.io
/crates/web-push
web, package
-
github.com
/pimeys/rust-web-push
package
-
nvd.nist.gov
/vuln/detail/CVE-2025-53604
advisory
Sources
- CVE List CVE-2025-53604
- GitHub Advisory GHSA-fc83-9jwq-gc2m
- GitHub Advisory GHSA-287x-9rff-qvcg
- NVD CVE-2025-53604
- OSV RUSTSEC-2025-0015
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.