Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-54335 low CVSS 3.7

Vulnerability in @feathersjs/commons (CVE-2026-54335)

Summary

Vulnerability in @feathersjs/commons (CVE-2026-54335). Risk of unauthorized operations or information disclosure. Exploitable via source. Mitigation: upgrade to 5.0.45 or later.

Original description

The description as published by the source.

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).

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-54335 has been found in @feathersjs/commons.
Attackers can target a specific entry point like source over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 3.7/10.
What to do: upgrade @feathersjs/commons to 5.0.45 or later.
If unsure, ask your IT team or search "@feathersjs/commons CVE-2026-54335" on the vendor's site.

CVE-2026-54335 (@feathersjs/commons) — CWE-1321 / CVSS v3 3.7
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: source / target / JSON.parse / __proto__
Patched: 5.0.45 — apply immediately
Workaround: Avoid passing JSON-parsed untrusted input through commons._.merge.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-1321) exists in @feathersjs/commons. Attackers reach the vulnerable code path via source without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of @feathersjs/commons. Attack surface: source / target / JSON.parse / __proto__.

🔥 Severity

Severity: Low (CVSS 3.7/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 5.0.45.

🛡️ Workaround

Workaround: Avoid passing JSON-parsed untrusted input through commons._.merge.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@feathersjs/commons' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r '@feathersjs/commons' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で @feathersjs/commons を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply temporary workaround mitigate 
    Avoid passing JSON-parsed untrusted input through `commons._.merge`.

    パッチが適用されるまでの応急処置として、Avoid passing JSON-parsed untrusted input through commons._.merge. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch 
    Upgrade @feathersjs/commons to 5.0.45

    ステージング環境で 5.0.45 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  4. 4
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

npm @feathersjs/commons
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"5.0.45"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details