How severe is GHSA-rhr9-hgcm-x289?

No CVSS score has been assigned to GHSA-rhr9-hgcm-x289 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-rhr9-hgcm-x289?

GHSA-rhr9-hgcm-x289 affects the following packages: github.com/gravitl/netmaker (Go). Ecosystems affected: Go.

How do I fix GHSA-rhr9-hgcm-x289?

Update github.com/gravitl/netmaker to 1.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rhr9-hgcm-x289 is resolved across your whole dependency graph.

How do I detect GHSA-rhr9-hgcm-x289 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-rhr9-hgcm-x289 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-rhr9-hgcm-x289?

O3 pinpoints whether GHSA-rhr9-hgcm-x289 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-rhr9-hgcm-x289 actively exploited in the wild?

No public exploit code has been indexed for GHSA-rhr9-hgcm-x289 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 type of vulnerability is GHSA-rhr9-hgcm-x289?

GHSA-rhr9-hgcm-x289 is classified as CWE-404 (CWE-404). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-rhr9-hgcm-x289 published, and has it been updated?

GHSA-rhr9-hgcm-x289 was published on March 4, 2026 and was last updated on March 23, 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

Not in CISA KEV

GHSA-rhr9-hgcm-x289

GHSA-rhr9-hgcm-x289 is a CWE-404 vulnerability in github.com/gravitl/netmaker. O3 Security confirms whether GHSA-rhr9-hgcm-x289 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Netmaker Vulnerable to Denial of Service via Server Shutdown Endpoint

Also known asCVE-2026-29771GO-2026-4608

Published

Mar 4, 2026

Updated

Mar 23, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Mar 23, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐹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

The /api/server/shutdown endpoint allows termination of the Netmaker server process via syscall.SIGINT. This allows any user to repeatedly shut down the server, causing cyclic denial of service with approximately 3-second restart intervals.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/gravitl/netmaker`	all versions	1.2.0

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 1.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rhr9-hgcm-x289 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-rhr9-hgcm-x289 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-rhr9-hgcm-x289. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-rhr9-hgcm-x289 in your dependencies?

O3 detects GHSA-rhr9-hgcm-x289 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