Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Seroval versions before 1.6.3 are affected. When deserializing TypedArray data from JSON, the library does not validate the input's type or bound the element count, so a small JSON payload that specifies a very large length can make the deserializer allocate a large amount of memory synchronously. An unauthenticated remote attacker who can send untrusted Seroval JSON to a service that deserializes it could exhaust CPU and memory and stall the event loop, with no confidentiality or integrity impact. Upgrade to seroval 1.6.3 or later, which is listed as the fixed version.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 7.5 | High | 3.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0043, the 37th percentile, on 13 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 13:34 UTC First seen by agentprime
- 31 Oct 2026, 13:34 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-jp82-f5mq-hwhp
- OSV: GHSA-jp82-f5mq-hwhp
- github.com/lxsmnsyc/seroval/security/advisories/GHSA-jp82-f5mq-hwhp
- nvd.nist.gov/vuln/detail/CVE-2026-104845
- github.com/lxsmnsyc/seroval/commit/ac0163e420ac7dcbbefac4d069bcefad300a4851
- github.com/lxsmnsyc/seroval/commit/e54a6f62784b9e48e3a5fa2ab4089ca69fb8996e
- github.com/lxsmnsyc/seroval