How severe is GHSA-3cw6-2j68-868p?

GHSA-3cw6-2j68-868p has a CVSS score of 5.9/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-3cw6-2j68-868p?

GHSA-3cw6-2j68-868p affects the following packages: github.com/envoyproxy/envoy (Go), github.com/envoyproxy/envoy (Go), github.com/envoyproxy/envoy (Go), github.com/envoyproxy/envoy (Go). Ecosystems affected: Go.

How do I fix GHSA-3cw6-2j68-868p?

No patched version of github.com/envoyproxy/envoy has shipped for GHSA-3cw6-2j68-868p yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect GHSA-3cw6-2j68-868p in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/envoyproxy/envoy. 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-3cw6-2j68-868p 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-3cw6-2j68-868p?

O3 pinpoints whether GHSA-3cw6-2j68-868p 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-3cw6-2j68-868p actively exploited in the wild?

No public exploit code has been indexed for GHSA-3cw6-2j68-868p 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.

What is the EPSS score for GHSA-3cw6-2j68-868p?

GHSA-3cw6-2j68-868p has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 31th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-3cw6-2j68-868p?

GHSA-3cw6-2j68-868p is classified as Improper Input Validation (CWE-20). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-3cw6-2j68-868p published, and has it been updated?

GHSA-3cw6-2j68-868p was published on March 10, 2026 and was last updated on March 13, 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

GHSA-3cw6-2j68-868p

MEDIUM

Envoy vulnerable to crash for scoped ip address during DNS

Also known asBIT-envoy-2026-26310CVE-2026-26310

Published

Mar 10, 2026

Updated

Mar 13, 2026

Affected

4 pkgs

Patched

None yet

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk31th percentile+0.38%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

4 pkgs affected

🐹github.com/envoyproxy/envoy🐹github.com/envoyproxy/envoy🐹github.com/envoyproxy/envoy🐹github.com/envoyproxy/envoy

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

Calling Utility::getAddressWithPort with a scoped IPv6 addresses causes a crash. This utility is called in the data plane from the original_src filter and the dns filter.

Details

The crashing function is Utility::getAddressWithPort. The crash occurs if a string containing a scoped IPv6 address is passed to this function.

This vulnerability affects:

The original src filter: If the filter is configured and the original source is a scoped IPv6 address, it will cause a crash.
DNS response address resolution: If a DNS response contains a scoped IPv6 address, this will also trigger the crash.

PoC

To reproduce the vulnerability:

Method A (Original Src Filter): Configure the original src filter in Envoy and provide a scoped IPv6 address as the original source.
Method B (DNS Resolution): Trigger a DNS resolution process within Envoy where the DNS response contains a scoped IPv6 address.

Impact

This is a Denial of Service (DoS) vulnerability. It impacts users who have the original src filter configured or whose Envoy instances resolve addresses from DNS responses that may contain scoped IPv6 addresses.

Affected Packages

4 total

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/envoyproxy/envoy`	all versions	No fix
🐹Go	`github.com/envoyproxy/envoy`	≥ 1.36.0	No fix
🐹Go	`github.com/envoyproxy/envoy`	≥ 1.35.0	No fix
🐹Go	`github.com/envoyproxy/envoy`	all versions	No fix

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/envoyproxy/envoy. 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.
Remediation status
No patched version of github.com/envoyproxy/envoy has shipped for GHSA-3cw6-2j68-868p yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
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-3cw6-2j68-868p 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-3cw6-2j68-868p. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary Calling `Utility::getAddressWithPort` with a scoped IPv6 addresses causes a crash. This utility is called in the data plane from the original_src filter and the dns filter. ### Details The crashing function is `Utility::getAddressWithPort`. The crash occurs if a string containing a scoped IPv6 address is passed to this function. This vulnerability affects: 1. The **original src filter**: If the filter is configured and the original source is a scoped IPv6 address, it will cause a crash. 2. **DNS response address resolution**: If a DNS response contains a scoped IPv6 address, t

O3 Security · Impact-Aware SCA

Is GHSA-3cw6-2j68-868p in your dependencies?

O3 detects GHSA-3cw6-2j68-868p 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