GHSA-wp97-x4hv-qvhp: High severity npm/seroval vulnerability

Published Oct 28, 2026
·
Updated

Summary

fromJSON and fromCrossJSON did not check that an array node's element list is an array. A small crafted payload could set the length the decoder used. That length controlled how much memory was allocated and how many times the decoder looped, and it did not depend on the size of the payload.

Impact

A service that passes untrusted input to fromJSON or fromCrossJSON can be made unavailable by an unauthenticated request.

- A small payload can allocate enough memory to end the process. - A small payload can block the thread for seconds, or without end.

This affects any framework that decodes request bodies with these functions before its own validation runs.

This issue is a bypass of the fix for GHSA-66fc-rw6m-c2q6 in 1.4.1.

Patches

Fixed in seroval@1.6.8. The deserializer now rejects any node whose element list is not an array, and throws SerovalMalformedNodeError.

Workarounds

None. Upgrade to 1.6.8.

Affected Software

1 affected componentFixes available
npm/seroval>=1.4.1<=1.6.7
1.6.8

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade npm/seroval to a version that resolves this vulnerability.

    Fixed in 1.6.8
  2. Upgrade

    Upgrade seroval to a version that resolves this vulnerability.

    Fixed in 1.6.8

Event History

Oct 28, 2026
Advisory Published
via GitHub·09:17 PM
Data Sourced
via GitHub·09:17 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

Which deployments are exposed to denial of service?

Any service that passes untrusted input to seroval's fromJSON or fromCrossJSON functions is exposed. This includes frameworks that deserialize request bodies with these functions before their own validation runs.

2

What does an attacker need to exploit this issue?

An attacker can trigger the issue with an unauthenticated request containing a small crafted payload. The payload can cause excessive memory allocation or make a decoder thread loop for seconds or indefinitely.

3

Are there mitigations if upgrading cannot happen immediately?

No workaround is provided. Upgrade seroval to version 1.6.8.

4

How does the fixed version handle malformed input?

Version 1.6.8 rejects nodes whose element list is not an array and throws SerovalMalformedNodeError.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203