How severe is GHSA-4ph6-mjv7-3fq6?

No CVSS score has been assigned to GHSA-4ph6-mjv7-3fq6 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-4ph6-mjv7-3fq6?

GHSA-4ph6-mjv7-3fq6 affects the following packages: github.com/tinfoil-factory/netfoil (Go). Ecosystems affected: Go.

How do I fix GHSA-4ph6-mjv7-3fq6?

Update github.com/tinfoil-factory/netfoil to 0.5.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4ph6-mjv7-3fq6 is resolved across your whole dependency graph.

How do I detect GHSA-4ph6-mjv7-3fq6 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-4ph6-mjv7-3fq6 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-4ph6-mjv7-3fq6?

O3 pinpoints whether GHSA-4ph6-mjv7-3fq6 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-4ph6-mjv7-3fq6 actively exploited in the wild?

No public exploit code has been indexed for GHSA-4ph6-mjv7-3fq6 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-4ph6-mjv7-3fq6 published, and has it been updated?

GHSA-4ph6-mjv7-3fq6 was published on August 24, 2026 and was last updated on August 26, 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-4ph6-mjv7-3fq6

Fix: tinfoil-factory/netfoil@58cfb0c

GHSA-4ph6-mjv7-3fq6 is a security vulnerability in github.com/tinfoil-factory/netfoil. O3 Security confirms whether GHSA-4ph6-mjv7-3fq6 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

netfoil vulnerable to improper handling of untrusted DoH response data

Also known asGO-2026-6277

Published

Aug 24, 2026

Updated

Aug 26, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Aug 26, 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

HTTPS RR data returned from the DoH server was not properly handled. Unverified APLN data (which could contain arbitrary byte sequences) was written directly to the log. It could also cause unnecessary memory usage. The single-byte response code was also written directly to the log.

Affected Packages

1 total 1 fixed

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

Frequently Asked Questions

### Summary HTTPS RR data returned from the DoH server was not properly handled. Unverified APLN data (which could contain arbitrary byte sequences) was written directly to the log. It could also cause unnecessary memory usage. The single-byte response code was also written directly to the log.

O3 Security · Impact-Aware SCA

Is GHSA-4ph6-mjv7-3fq6 in your dependencies?

O3 detects GHSA-4ph6-mjv7-3fq6 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