---
title: "GHSA-c83g-rgw3-j3cx: Browserslist: Unbounded memory growth (no cache eviction) via distinct query results, leading to eventual OOM"
description: "High severity. Browserslist: Unbounded memory growth (no cache eviction) via distinct query results, leading to eventual OOM."
url: https://inlinr.com/advisories/GHSA-c83g-rgw3-j3cx
lang: en
---

[Packages](https://inlinr.com/packages) / [browserslist](https://inlinr.com/packages/browserslist) / [Security](https://inlinr.com/packages/browserslist/security)

High Vulnerability GHSA-c83g-rgw3-j3cx CVE-2026-73089 Published 1 Sep 2026

# Browserslist: Unbounded memory growth (no cache eviction) via distinct query results, leading to eventual OOM

Your version 

Affected releases · [browserslist](https://inlinr.com/packages/browserslist)

- 4.x 4.0.0 – 4.28.6 Fixed in 4.28.7
- 3.x and older 0.1.0 – 3.2.8 No fix, no longer updated

On 4.x, the newest line:

```
npm install browserslist@4.28.7
```

Every release on a timeline

4.x 

1. Affected

4.0.0 – 4.28.6  
133 releases
2. Fixed

4.28.7 – 4.29.6  
10 releases, latest

3.x 

1. Affected

3.0.0 – 3.2.8  
13 releases

2.x 

1. Affected

2.0.0 – 2.11.3  
30 releases

1.x 

1. Affected

1.0.0 – 1.7.7  
27 releases

0.x 

1. Affected

0.1.0 – 0.5.0  
11 releases

224 stable releases of browserslist, oldest to newest, one row per major.

## What happens

Vulnerability Details

**File**: `index.js` **Location**: `cache` (browserslist()'s result cache, line \~402) and `parseCache` (parseQueries()'s AST cache)

Root Cause

```
var cache = {}
var parseCache = {}

function browserslist(queries, opts) {
  ...
  var cacheKey = JSON.stringify([queries, context])
  if (cache[cacheKey]) return cache[cacheKey]
  ...
  if (!env.env.BROWSERSLIST_DISABLE_CACHE) { cache[cacheKey] = result }
  return result
}

function parseQueries(queries) {
  var cacheKey = JSON.stringify(queries)
  if (cacheKey in parseCache) return parseCache[cacheKey]
  var result = parseWithoutCache(QUERIES, queries)
  if (!env.env.BROWSERSLIST_DISABLE_CACHE) { parseCache[cacheKey] = result }
  ...
}
```

Every distinct `(queries, context)` pair is cached forever — no size cap, TTL, or eviction. `browserslist.clearCaches()` never resets either object (it only resets `node.js`'s own filesystem caches); the only opt-out is the `BROWSERSLIST_DISABLE_CACHE` env var, controlled by the _calling application_, not an attacker.

Some short, valid queries amplify this badly. The `since <year>-<month>-<day>`query type (`/^since (\d+)-(\d+)-(\d+)$/i`) accepts **any** digit combination — `Date.UTC()` normalizes rather than rejects out-of-range values — giving an effectively unbounded space of \~17-byte distinct cache keys, each of which resolves to (and caches) a result close to the full \~8.5 KB browser list for any sufficiently old year.

Measured Impact

20,000 distinct `since <year>-<month>-<day>` queries (\~330 KB total input, `--expose-gc` before/after measurement to rule out uncollected garbage) retained **over 50 MB** of heap permanently — roughly **150x**amplification, growing linearly with no cap observed up to 40,000 queries (52.3 MB).

Attack Scenario

Any long-running process (server, daemon, warm CI worker) that calls `browserslist()` with a query value that varies across requests/items and is influenced, even partially, by external input accumulates one cache entry per distinct value ever seen. An attacker who can influence that value across _many_ requests (this is a volumetric attack, unlike the single-request DoS findings from this same research pass) sends a stream of cheap, distinct queries (e.g. `since 1900-01-01`, `since 1900-01-02`, ...) until the process runs out of memory and crashes.

Recommended Fix (implemented and verified)

Replace both plain-object caches with `Map`s bounded to a fixed maximum entry count, evicting the oldest entry once the cap is reached (`Map`preserves insertion order, so `.keys().next().value` is always oldest):

```
var CACHE_MAX_ENTRIES = 500

function boundedCacheSet(map, key, value) {
  if (map.size >= CACHE_MAX_ENTRIES) {
    map.delete(map.keys().next().value)
  }
  map.set(key, value)
}

var cache = new Map()
var parseCache = new Map()
```

(read sites changed to `.has()`/`.get()`, write sites to `boundedCacheSet()`)

**Verification**:

- `NODE_ENV=test npx uvu test .test.js` → 301/301 pass unmodified (`test/cache.test.js` exercises `clearCaches()`/`BROWSERSLIST_DISABLE_CACHE`against `node.js`'s separate filesystem caches, unaffected here); confirmed a repeated identical call still returns the cached reference.
- Re-ran the memory PoC post-fix: heap stayed flat at \~4.9 MB after 5,000, 10,000, 20,000, and 40,000 distinct `since`\-date queries (was 10.5 → 16.5 → 28.4 → 52.3 MB pre-fix).

Impact

- **Who is affected**: Long-running processes calling `browserslist()` with query values that vary across requests/items and are influenced by external input.
- **What an attacker achieves**: DoS via eventual out-of-memory crash, given sustained traffic over time (not a single small payload).
- **Conditions required**: No authentication; requires volume rather than a single request, hence Medium rather than High severity.

Verification Environment

browserslist @ HEAD (== v4.28.6, current latest stable release) under local Node.js v20.19.5, run with `--expose-gc` for accurate heap measurement.

Note

Found during a broader review of this codebase in the same research pass that produced GHSA-rrmg-cfrq-23vv (parse.js algorithmic complexity), GHSA-g6p8-hj8g-x889 (baseline regexp ReDoS), GHSA-73wf-gq98-2v4g (normalizeStats crash/prototype write), and GHSA-h633-868p-5rfw (SCOPED\_CONFIG\_\_PATTERN ReDoS) — all single-request DoS vectors. This one is different in character (volumetric, not single-request) and is reported separately/scored lower accordingly.

## How it is exploited

Exploitable over the network, with no account and no action from a user.

- **Confidentiality**: none
- **Integrity**: none
- **Availability**: high

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

## References

- [Reference](https://github.com/browserslist/browserslist/security/advisories/GHSA-c83g-rgw3-j3cx "https://github.com/browserslist/browserslist/security/advisories/GHSA-c83g-rgw3-j3cx")  
github.com/browserslist/browserslist/security/a…
- [NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-73089 "https://nvd.nist.gov/vuln/detail/CVE-2026-73089")  
nvd.nist.gov/vuln/detail/CVE-2026-73089
- [Fix commit](https://github.com/browserslist/browserslist/commit/f2931a3ff2a3a31abf84ef01a7400b270aad6405 "https://github.com/browserslist/browserslist/commit/f2931a3ff2a3a31abf84ef01a7400b270aad6405")  
f2931a3
- [Package](https://github.com/browserslist/browserslist "https://github.com/browserslist/browserslist")  
github.com/browserslist/browserslist
- [Reference](https://github.com/browserslist/browserslist/releases/tag/4.28.7 "https://github.com/browserslist/browserslist/releases/tag/4.28.7")  
github.com/browserslist/browserslist/releases/t…

A whole project to check? Paste its package.json in the [dependency check](https://inlinr.com/tools/dependency-check): every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.
