How severe is GHSA-vjgj-42f6-7997?

No CVSS score has been assigned to GHSA-vjgj-42f6-7997 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-vjgj-42f6-7997?

GHSA-vjgj-42f6-7997 affects the following packages: github.com/tinfoil-factory/netfoil (Go). Ecosystems affected: Go.

How do I fix GHSA-vjgj-42f6-7997?

Update github.com/tinfoil-factory/netfoil to 0.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vjgj-42f6-7997 is resolved across your whole dependency graph.

How do I detect GHSA-vjgj-42f6-7997 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-vjgj-42f6-7997 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-vjgj-42f6-7997?

O3 pinpoints whether GHSA-vjgj-42f6-7997 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-vjgj-42f6-7997 actively exploited in the wild?

No public exploit code has been indexed for GHSA-vjgj-42f6-7997 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-vjgj-42f6-7997 published, and has it been updated?

GHSA-vjgj-42f6-7997 was published on April 29, 2026 and was last updated on May 5, 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-vjgj-42f6-7997: netfoil's optional seccomp sandboxing was…

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

The optional flag --filter-system-calls was not applied even if specified.

Details

This is a defense in depth feature to apply additional seccomp filters after the binary has started. The example config also sandboxes the binary with systemd.

Impact

Reduced sandboxing of the netfoil binary.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/tinfoil-factory/netfoil`	all versions	0.2.1

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

Frequently Asked Questions

### Summary The optional flag `--filter-system-calls` was not applied even if specified. ### Details This is a defense in depth feature to apply additional seccomp filters after the binary has started. The example config also sandboxes the binary with systemd. ### Impact Reduced sandboxing of the netfoil binary.

O3 Security · Impact-Aware SCA

Is GHSA-vjgj-42f6-7997 in your dependencies?

O3 detects GHSA-vjgj-42f6-7997 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-vjgj-42f6-7997