Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') Affecting librechat package, versions <0.8.7-r5
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-CHAINGUARDLATEST-LIBRECHAT-19477736
- published2 Sept 2026
- disclosed1 Aug 2026
Introduced: 1 Aug 2026
CVE-2026-67316 (opens in a new tab)How to fix?
Upgrade Chainguard librechat to version 0.8.7-r5 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream librechat package and not the librechat package as distributed by Chainguard.
See How to fix? for Chainguard relevant fixed versions and status.
axios is vulnerable to read-side prototype-pollution gadgets that can alter request construction when Object.prototype has already been polluted by a separate vulnerability or dependency. In the bodyless method aliases (axios.get(), axios.delete(), axios.head(), axios.options()), inherited data is read via (config || {}).data before config normalization, causing an attacker-controlled body to be sent on requests that did not set one. Additional low-level paths, only reachable when calling exported adapters/helpers (e.g. lib/adapters/http.js, unsafe/helpers/resolveConfig.js) directly with plain configs and no own proxy or paramsSerializer, can inherit polluted proxy values (routing requests through an attacker-controlled proxy) or paramsSerializer values (attacker-controlled URL serialization). These low-level gadgets do not reproduce through normal high-level axios calls on 1.15.2+. The issue is fixed in axios 1.18.0 and 0.33.0.