PT-2026-60100 · Npm · @Feathersjs/Commons
Publicado
2026-07-14
·
Atualizado
2026-07-14
·
CVE-2026-54335
CVSS v3.1
3.7
Baixa
| Vetor | AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N |
Impact
The
.merge(target, source) utility exported by @feathersjs/commons recursively merges source into target by iterating Object.keys(source). When source was produced by JSON.parse and contains a proto (or constructor / prototype) key, that key is returned as an own-enumerable property. The recursive merge then resolves target[' proto '] to Object.prototype and writes the attacker-supplied properties onto it, polluting the prototype for all plain objects in the process for the lifetime of the Node process.Scope of real-world risk is limited. No first-party Feathers package routes input — trusted or untrusted — through
commons. .merge. The @feathersjs/authentication package, which does merge request-influenced data, uses lodash/merge (prototype-pollution-safe since 4.17.12), not this utility. Exploitation therefore requires a downstream plugin or application to pass JSON-parsed, attacker-controlled input directly through the exported .merge.Patches
Fixed in
@feathersjs/commons@5.0.45. The fix skips proto, constructor, and prototype keys during iteration — the standard remediation used by lodash and others.Workarounds
Avoid passing JSON-parsed untrusted input through
commons. .merge. Freezing Object.prototype or validating/sanitizing keys upstream also mitigates.Credit
Reported responsibly by Andrew Ridings (@ridingsa).
Correção
Prototype Pollution
Encontrou algum problema na descrição? Tem algo a acrescentar? Fique à vontade para nos escrever 👾
Enumeração de Fraquezas
Identificadores relacionados
Produtos afetados
@Feathersjs/Commons