REDHAT-BUG-2514177: High severity npm/browserslist vulnerability

Published Aug 11, 2026
·
Updated

Browserslist is a configuration tool for sharing target browsers and Node.js versions between front-end tools. Prior to 4.28.7, normalizeStats() in node.js, reached unconditionally through getStat() and loadStat() on every browserslist() call, processes untrusted browserslist-stats.json, opts.stats, and CLI --stats data with an unguarded for...in loop and plain-object bracket access and assignment, allowing inherited Object.prototype keys including proto, toString, valueOf, constructor, hasOwnProperty, and isPrototypeOf to cause an uncaught TypeError or modify the prototype of the returned normalized object. This issue is fixed in version 4.28.7.

Affected Software

1 affected component
npm/browserslist<4.28.7

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade browserslist to a version that resolves this vulnerability.

    Fixed in 4.28.7

Event History

Aug 11, 2026
Data Sourced
via Red Hat·05:12 PM
DescriptionSeverityAffected Software

Frequently Asked Questions

1

Who is exposed to this issue?

Applications and build or front-end tooling that use npm/browserslist before 4.28.7 and process untrusted browser statistics input are exposed. The affected inputs include browserslist-stats.json, the opts.stats option, and CLI --stats data.

2

What must an attacker control to exploit it?

An attacker needs to supply or influence statistics data processed by Browserslist. Crafted inherited Object.prototype property names, including __proto__, constructor, toString, valueOf, hasOwnProperty, and isPrototypeOf, can trigger an uncaught TypeError or alter the prototype of the normalized result.

3

Is the vulnerable code reached during normal Browserslist use?

Yes. normalizeStats() is reached unconditionally through getStat() and loadStat() on every browserslist() call, so the relevant behavior does not require a separate optional code path once affected statistics input is processed.

4

What should be done if patching is not immediately possible?

Do not accept or process untrusted browserslist-stats.json files, opts.stats values, or CLI --stats input. Restrict these inputs to trusted, validated sources until Browserslist can be updated to 4.28.7.

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