How severe is GHSA-3g4q-2f67-2gvh?

No CVSS score has been assigned to GHSA-3g4q-2f67-2gvh yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-3g4q-2f67-2gvh?

GHSA-3g4q-2f67-2gvh affects the following packages: github.com/tinfoil-factory/netfoil (Go). Ecosystems affected: Go.

How do I fix GHSA-3g4q-2f67-2gvh?

Update github.com/tinfoil-factory/netfoil to 0.3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3g4q-2f67-2gvh is resolved across your whole dependency graph.

How do I detect GHSA-3g4q-2f67-2gvh in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/tinfoil-factory/netfoil. 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-3g4q-2f67-2gvh 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-3g4q-2f67-2gvh?

O3 pinpoints whether GHSA-3g4q-2f67-2gvh 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-3g4q-2f67-2gvh actively exploited in the wild?

No public exploit code has been indexed for GHSA-3g4q-2f67-2gvh 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-3g4q-2f67-2gvh published, and has it been updated?

GHSA-3g4q-2f67-2gvh was published on July 7, 2026 and was last updated on July 21, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

GHSA-3g4q-2f67-2gvh: netfoil has a resource leak in LRU cache

Blast Radius

1 pkg affected

🐹github.com/tinfoil-factory/netfoil

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

Summary

When an entry was removed from the LRU cache, a pointer to the removed element was not properly cleaned up.

Impact

A local attacker can get netfoil to use more memory. By default this is limited to 100MB via systemd, which would trigger service restarts when reached.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/tinfoil-factory/netfoil`	all versions	0.3.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/tinfoil-factory/netfoil. 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/tinfoil-factory/netfoil to 0.3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3g4q-2f67-2gvh 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-3g4q-2f67-2gvh 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-3g4q-2f67-2gvh. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary When an entry was removed from the LRU cache, a pointer to the removed element was not properly cleaned up. ### Impact A local attacker can get netfoil to use more memory. By default this is limited to 100MB via systemd, which would trigger service restarts when reached.

O3 Security · Impact-Aware SCA

Is GHSA-3g4q-2f67-2gvh in your dependencies?

O3 detects GHSA-3g4q-2f67-2gvh 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

GHSA-3g4q-2f67-2gvh