Vulnerability in @faker-js/faker (CVE-2026-73231)
Summary
Vulnerability in @faker-js/faker (CVE-2026-73231). Successful exploitation can lead to full system takeover. Exploitable via faker.helpers.fake. Mitigation: upgrade to 10.5.0 or later.
Original description
The description as published by the source.
Summary
faker.helpers.fake can be tricked into arbritary code execution.
Details
fakeEval.resolveProperty resolves properties on functions itself instead of resolving the nested function first.
This can be addressed by recursively calling resolveProperty instead of accessing the property after one iteration.
PoC
Go to https://fakerjs.dev/
Open Browser console and run
await enableFaker(); // or import faker
faker.rawDefinitions.test = (() => () => {}); // Any function that returns a function
faker.helpers.fake(`{{test.constructor(alert('PowerLevel: Eval'))}}`);
Impact
The Fake method claims:
It is also NOT possible to use any non-faker methods or plain javascript in such patterns.
Which is objectively false, since any global gets fully accessible in the fake string.
Source: NIST National Vulnerability Database 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-73231 has been found in @faker-js/faker.
Attackers can target a specific entry point like faker.helpers.fake over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 7.8/10.
What to do: upgrade @faker-js/faker to 10.5.0 or later.
If unsure, ask your IT team or search "@faker-js/faker CVE-2026-73231" on the vendor's site.
CVE-2026-73231 (@faker-js/faker) — CWE-95 / CVSS v3 7.8
Attack vector: local / no user interaction
Attack surface: faker.helpers.fake
Patched: 10.5.0 — apply immediately
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.
A vulnerability (CWE-95) exists in @faker-js/faker. Attackers reach the vulnerable code path via faker.helpers.fake.
Check the vendor advisory for the affected versions of @faker-js/faker. Attack surface: faker.helpers.fake.
Severity: High (CVSS 7.8/10). Successful exploitation can lead to full system takeover.
Update to 10.5.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@faker-js/faker' . 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
-
1Identify exposure identify
grep -r '@faker-js/faker' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@faker-js/fakerを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade @faker-js/faker to 10.5.0ステージング環境で 10.5.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com