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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-vjgj-42f6-7997 can be triaged on real exposure rather than presence alone.

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 June 25, 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-vjgj-42f6-7997 — netfoil

Fix: tinfoil-factory/netfoil@8c84f1b

GHSA-vjgj-42f6-7997 is a security vulnerability in github.com/tinfoil-factory/netfoil. A fix is available for github.com/tinfoil-factory/netfoil — see the affected versions and patch details below.

netfoil's optional seccomp sandboxing was not applied

Also known asGO-2026-5664

Published

Apr 29, 2026

Updated

Jun 25, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Jun 25, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

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`go get github.com/tinfoil-factory/netfoil@v0.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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-vjgj-42f6-7997 can be triaged on real exposure rather than presence alone.

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 Security finds GHSA-vjgj-42f6-7997 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works