GHSA-qqj3-g7mx-5p4w is a high-severity (CVSS 8.6) CWE-295 vulnerability in github.com/neuvector/neuvector. O3 Security confirms whether GHSA-qqj3-g7mx-5p4w is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
NeuVector telemetry sender is vulnerable to MITM and DoS
Real-World Exposure
github.com/neuvector/neuvectorReal-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
Impact
This vulnerability affects NeuVector deployments only when the Report anonymous cluster data option is enabled. When this option is enabled, NeuVector sends anonymous telemetry data to the telemetry server at https://upgrades.neuvector-upgrade-responder.livestock.rancher.io.
In affected versions, NeuVector does not enforce TLS certificate verification when transmitting anonymous cluster data to the telemetry server. As a result, the communication channel is susceptible to man-in-the-middle (MITM) attacks, where an attacker could intercept or modify the transmitted data. Additionally, NeuVector loads the response of the telemetry server is loaded into memory without size limitation, which makes it vulnerable to a Denial of Service(DoS) attack.
The patched version includes the following security improvements:
- NeuVector now verifies the telemetry server’s
TLS certificate chainandhostnameduring the handshake process. This ensures that all telemetry communications occur over a trusted and verified channel. - NeuVector limits the telemetry server’s response to
256 bytes, mitigating the risk of memory exhaustion and DoS attacks.
These security enhancements are enabled by default and require no user action.
Patches
Patched versions include release v5.4.7 and above.
Workarounds
If you cannot update to a patched version, you can temporarily disable the Report anonymous cluster data, which is enabled by default in NeuVector. To change this setting, go to Settings → Configuration → Report anonymous cluster data in the NeuVector UI.
Disabling this option prevents NeuVector from sending telemetry data to the telemetry server, which helps mitigate this vulnerability.
References
If you have any questions or comments about this advisory:
- Reach out to the SUSE Rancher Security team for security related inquiries.
- Open an issue in the NeuVector repository.
- Verify with our support matrix and product support lifecycle.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/neuvector/neuvector | ≥ 0.0.0-20230727023453-1c4957d53911&&< 0.0.0-20251020133207-084a437033b4 | 0.0.0-20251020133207-084a437033b4 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/neuvector/neuvector. 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/neuvector/neuvector to 0.0.0-20251020133207-084a437033b4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qqj3-g7mx-5p4w 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-qqj3-g7mx-5p4w 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-qqj3-g7mx-5p4w. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-qqj3-g7mx-5p4w in your dependencies?
O3 detects GHSA-qqj3-g7mx-5p4w across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.