How severe is GHSA-c3px-v9c7-m734?

No CVSS score has been assigned to GHSA-c3px-v9c7-m734 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-c3px-v9c7-m734?

GHSA-c3px-v9c7-m734 affects the following packages: mithril (npm), mithril (npm). Ecosystems affected: npm.

How do I fix GHSA-c3px-v9c7-m734?

Update mithril to 1.1.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-c3px-v9c7-m734 is resolved across your whole dependency graph.

How do I detect GHSA-c3px-v9c7-m734 in my npm dependencies?

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

How do I mitigate GHSA-c3px-v9c7-m734 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-c3px-v9c7-m734 actively exploited in the wild?

No public exploit code has been indexed for GHSA-c3px-v9c7-m734 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.

When was GHSA-c3px-v9c7-m734 published, and has it been updated?

GHSA-c3px-v9c7-m734 was published on September 3, 2020 and was last updated on August 31, 2020. 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

Prototype Pollution in mithrilGHSA-c3px-v9c7-m734

GHSA-c3px-v9c7-m734 is a security vulnerability in mithril. A fix is available for mithril — see the affected versions and patch details below.

Published

Sep 3, 2020

Updated

Aug 31, 2020

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Aug 31, 2020 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

2 pkgs 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.

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

mithrilnpm

20Kdownloads / week

Description

Affected versions of mithrilare vulnerable to prototype pollution. The function parseQueryString may allow a malicious user to modify the prototype of Object, causing the addition or modification of an existing property that will exist on all objects. A payload such as __proto__%5BtoString%5D=123 in the query string would change the toString() function to 123.

Recommendation

If you are using mithril 2.x, upgrade to version 2.0.2 or later. If you are using mithril 1.x, upgrade to version 1.1.7 or later.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`mithril`	all versions	1.1.7`npm install mithril@1.1.7`
📦npm	`mithril`	≥ 2.0.0&&< 2.0.2	2.0.2`npm install mithril@2.0.2`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mithril, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update mithril to 1.1.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-c3px-v9c7-m734 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

Affected versions of `mithril`are vulnerable to prototype pollution. The function `parseQueryString` may allow a malicious user to modify the prototype of `Object`, causing the addition or modification of an existing property that will exist on all objects. A payload such as `__proto__%5BtoString%5D=123` in the query string would change the `toString()` function to `123`. ## Recommendation If you are using mithril 2.x, upgrade to version 2.0.2 or later. If you are using mithril 1.x, upgrade to version 1.1.7 or later.

O3 Security · Impact-Aware SCA

Is GHSA-c3px-v9c7-m734 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works