How severe is GHSA-86f3-hf24-76q4?

GHSA-86f3-hf24-76q4 has a CVSS score of 7.2/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-86f3-hf24-76q4?

GHSA-86f3-hf24-76q4 affects the following packages: github.com/gravitl/netmaker (Go), github.com/gravitl/netmaker (Go). Ecosystems affected: Go.

How do I fix GHSA-86f3-hf24-76q4?

Update github.com/gravitl/netmaker to 0.8.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-86f3-hf24-76q4 is resolved across your whole dependency graph.

How do I detect GHSA-86f3-hf24-76q4 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/gravitl/netmaker. 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-86f3-hf24-76q4 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-86f3-hf24-76q4?

O3 pinpoints whether GHSA-86f3-hf24-76q4 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-86f3-hf24-76q4 actively exploited in the wild?

No public exploit code has been indexed for GHSA-86f3-hf24-76q4 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-86f3-hf24-76q4?

GHSA-86f3-hf24-76q4 has an EPSS (Exploit Prediction Scoring System) score of 1.5%, placing it in the 71th 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-86f3-hf24-76q4 published, and has it been updated?

GHSA-86f3-hf24-76q4 was published on February 22, 2022 and was last updated on May 19, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

GHSA-86f3-hf24-76q4

HIGH

Use of Hard-coded Cryptographic Key in Netmaker

Also known asCVE-2022-23650GO-2022-0328

Published

Feb 22, 2022

Updated

May 19, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

1.5%probability of exploitation in next 30 days

Lower Risk71th percentile+0.72%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

2 pkgs affected

🐹github.com/gravitl/netmaker🐹github.com/gravitl/netmaker

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Impact

There is a hard-coded cryptographic key in the code base which can be exploited to run admin commands on a remote server, if you know the address and username of the admin. This effects the server (netmaker) component, and not clients.

Patches

This has been patched in Netmaker v0.8.5, v0.9.4, and v0.10.0. If you are running these versions, the fix is to perform the following:

docker-compose down
docker pull gravitl/netmaker:( version )
docker-compose up -d

Additional Information

If you are running any other version, you will need to upgrade to one of these three versions. If you have a special circumstance that requires running a different version, let us know and we may be able to build a custom patch.

For more information

If you have any questions or comments about this advisory:

Email us at [email protected]

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/gravitl/netmaker`	all versions	0.8.5
🐹Go	`github.com/gravitl/netmaker`	≥ 0.9.0&&< 0.9.4	0.9.4

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/gravitl/netmaker. 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 github.com/gravitl/netmaker to 0.8.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-86f3-hf24-76q4 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-86f3-hf24-76q4 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-86f3-hf24-76q4. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact There is a hard-coded cryptographic key in the code base which can be exploited to run admin commands on a remote server, if you know the address and username of the admin. This effects the server (netmaker) component, and not clients. ### Patches This has been patched in Netmaker v0.8.5, v0.9.4, and v0.10.0. If you are running these versions, the fix is to perform the following: 1. docker-compose down 2. docker pull gravitl/netmaker:( version ) 3. docker-compose up -d #### Additional Information If you are running **any other version**, you will need to upgrade to one of these t

O3 Security · Impact-Aware SCA

Is GHSA-86f3-hf24-76q4 in your dependencies?

O3 detects GHSA-86f3-hf24-76q4 across Go 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