NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
HIGH severity

CVE-2021-42057 — obsidian-dataview

HIGH

CVE-2021-42057 is a high-severity (CVSS 7.8) Code Injection vulnerability in obsidian-dataview. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for obsidian-dataview — see the affected versions and patch details below.

Obsidian Dataview vulnerable to code injection due to unsafe eval

Also known asGHSA-xfg5-vrmc-24wc
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
1 known
Exploitation data as of Nov 4, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.2%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs69th percentile — riskier than 69% of all scored CVEsHighest risk
0.00%0.58%1.16%1.75%0.3%1.2%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

3other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
obsidian-dataviewnpm
3Kdownloads / week

Description

Obsidian Dataview through 0.4.12-hotfix1 allows eval injection. The evalInContext function in executes user input, which allows an attacker to craft malicious Markdown files that will execute arbitrary code once opened. NOTE: 0.4.13 provides a mitigation for some use cases.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmobsidian-dataviewall versions0.4.13npm install obsidian-dataview@0.4.13

Affected Products

1 product · 3 configurations
Application
obsidian dataviewobsidian
≤ 0.4.11
1 version
0.4.12
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Obsidian Dataview through 0.4.12-hotfix1 allows eval injection. The eval…

github.comNVDNov 2021

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for obsidian-dataview, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update obsidian-dataview to 0.4.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-42057 is resolved across your whole dependency graph.

  3. Workarounds

    Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Frequently Asked Questions

Obsidian Dataview through 0.4.12-hotfix1 allows eval injection. The evalInContext function in executes user input, which allows an attacker to craft malicious Markdown files that will execute arbitrary code once opened. NOTE: 0.4.13 provides a mitigation for some use cases.
O3 Security · Impact-Aware SCA

Is CVE-2021-42057 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2021-42057: obsidian-dataview RCE — Fixed in 0.4.13