How severe is GHSA-45mx-g85m-wwm3?

GHSA-45mx-g85m-wwm3 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-45mx-g85m-wwm3?

GHSA-45mx-g85m-wwm3 affects the following packages: obsidian (npm). Ecosystems affected: npm.

How do I fix GHSA-45mx-g85m-wwm3?

Update obsidian to 0.12.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-45mx-g85m-wwm3 is resolved across your whole dependency graph.

How do I detect GHSA-45mx-g85m-wwm3 in my npm dependencies?

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

How do I mitigate GHSA-45mx-g85m-wwm3 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-45mx-g85m-wwm3 actively exploited in the wild?

No public exploit code has been indexed for GHSA-45mx-g85m-wwm3 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-45mx-g85m-wwm3?

GHSA-45mx-g85m-wwm3 has an EPSS (Exploit Prediction Scoring System) score of 1.2%, placing it in the 69th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was GHSA-45mx-g85m-wwm3 published, and has it been updated?

GHSA-45mx-g85m-wwm3 was published on May 24, 2022 and was last updated on April 22, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦

📦 npm

Not in CISA KEV

CRITICAL severity

Obsidian does not require user confirmation for non-http/https URLsGHSA-45mx-g85m-wwm3

CRITICAL

GHSA-45mx-g85m-wwm3 is a critical-severity (CVSS 9.8) vulnerability in obsidian. A fix is available for obsidian — see the affected versions and patch details below.

Also known asCVE-2021-38148

Published

May 24, 2022

Updated

Apr 22, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 7, 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

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.

57other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

obsidiannpm

189Kdownloads / week

Description

Obsidian before 0.12.12 does not require user confirmation for non-http/https URLs.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`obsidian`	all versions	0.12.12`npm install obsidian@0.12.12`

Affected Products

1 product · 1 configurations

Application

obsidianobsidian

< 0.12.12

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for obsidian, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update obsidian to 0.12.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-45mx-g85m-wwm3 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

Obsidian before 0.12.12 does not require user confirmation for non-http/https URLs.

O3 Security · Impact-Aware SCA

Is GHSA-45mx-g85m-wwm3 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works