How severe is GHSA-86mr-6m89-vgj3?

No CVSS score has been assigned to GHSA-86mr-6m89-vgj3 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-86mr-6m89-vgj3?

GHSA-86mr-6m89-vgj3 affects the following packages: node-weakauras-parser (npm), node-weakauras-parser (npm), node-weakauras-parser (npm). Ecosystems affected: npm.

How do I fix GHSA-86mr-6m89-vgj3?

Update node-weakauras-parser to 1.0.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-86mr-6m89-vgj3 is resolved across your whole dependency graph.

How do I detect GHSA-86mr-6m89-vgj3 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for node-weakauras-parser. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-86mr-6m89-vgj3 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.

How does O3 Security protect against GHSA-86mr-6m89-vgj3?

O3 pinpoints whether GHSA-86mr-6m89-vgj3 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-86mr-6m89-vgj3 actively exploited in the wild?

No public exploit code has been indexed for GHSA-86mr-6m89-vgj3 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-86mr-6m89-vgj3 published, and has it been updated?

GHSA-86mr-6m89-vgj3 was published on September 3, 2020 and was last updated on October 4, 2021. 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

GHSA-86mr-6m89-vgj3

Fix: Zireael-N/node-weakauras-parser@bc146da

GHSA-86mr-6m89-vgj3 is a remote code execution vulnerability in node-weakauras-parser. O3 Security confirms whether GHSA-86mr-6m89-vgj3 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Buffer Overflow in node-weakauras-parser

Published

Sep 3, 2020

Updated

Oct 4, 2021

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Oct 4, 2021 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

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

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

node-weakauras-parsernpm

367downloads / week

Description

Affected versions of node-weakauras-parser are vulnerable to a Buffer Overflow. The encode_weakaura function fails to properly validate the input size. A buffer of 13835058055282163711 bytes causes an overflow on 64-bit systems.

Recommendation

Upgrade to versions 1.0.5, 2.0.2, 3.0.1 or later.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`node-weakauras-parser`	≥ 1.0.4&&< 1.0.5	1.0.5
📦npm	`node-weakauras-parser`	≥ 2.0.0&&< 2.0.2	2.0.2
📦npm	`node-weakauras-parser`	≥ 3.0.0&&< 3.0.1	3.0.1

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for node-weakauras-parser. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update node-weakauras-parser to 1.0.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-86mr-6m89-vgj3 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.
How O3 protects you
O3 pinpoints whether GHSA-86mr-6m89-vgj3 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-86mr-6m89-vgj3. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Affected versions of `node-weakauras-parser` are vulnerable to a Buffer Overflow. The `encode_weakaura` function fails to properly validate the input size. A buffer of 13835058055282163711 bytes causes an overflow on 64-bit systems. ## Recommendation Upgrade to versions 1.0.5, 2.0.2, 3.0.1 or later.

O3 Security · Impact-Aware SCA

Is GHSA-86mr-6m89-vgj3 in your dependencies?

O3 detects GHSA-86mr-6m89-vgj3 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works