How severe is GHSA-6c6p-h79f-g6p4?

GHSA-6c6p-h79f-g6p4 has a CVSS score of 7.6/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-6c6p-h79f-g6p4?

GHSA-6c6p-h79f-g6p4 affects the following packages: github.com/istio/istio (Go). Ecosystems affected: Go.

How do I fix GHSA-6c6p-h79f-g6p4?

Update github.com/istio/istio to 1.15.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6c6p-h79f-g6p4 is resolved across your whole dependency graph.

How do I detect GHSA-6c6p-h79f-g6p4 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/istio/istio, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-6c6p-h79f-g6p4 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is GHSA-6c6p-h79f-g6p4 actively exploited in the wild?

No public exploit code has been indexed for GHSA-6c6p-h79f-g6p4 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-6c6p-h79f-g6p4?

GHSA-6c6p-h79f-g6p4 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 45th 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-6c6p-h79f-g6p4?

GHSA-6c6p-h79f-g6p4 is classified as CWE-863 (CWE-863). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-6c6p-h79f-g6p4 published, and has it been updated?

GHSA-6c6p-h79f-g6p4 was published on November 9, 2022 and was last updated on November 8, 2023. 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

HIGH severity

Istio may allow identity impersonation if user has localhost accessGHSA-6c6p-h79f-g6p4

HIGHFix: istio/istio@346260e

GHSA-6c6p-h79f-g6p4 is a high-severity (CVSS 7.6) CWE-863 vulnerability in github.com/istio/istio. A fix is available for github.com/istio/istio — see the affected versions and patch details below.

Also known asCVE-2022-39388

Published

Nov 9, 2022

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-6c6p-h79f-g6p4.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk+0.04%

Lower risk than most CVEs45th percentile — riskier than 45% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

🐹github.com/istio/istio

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

Impact

User can impersonate any workload identity within the service mesh if they have localhost access to the Istiod control plane.

Patches

1.15.3

Workarounds

No. If using 1.15.2 please upgrade to 1.15.3 or later.

References

None at this time.

For more information

If you have any questions or comments about this advisory, please email us at [email protected]

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/istio/istio`	≥ 1.15.0-beta.0&&< 1.15.3	1.15.3`go get github.com/istio/istio@v1.15.3`

Affected Products

1 product · 1 configurations

Application

istioistio

≥ 1.15.0 && ≤ 1.15.2

range

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/istio/istio, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/istio/istio to 1.15.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6c6p-h79f-g6p4 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

### Impact User can impersonate any workload identity within the service mesh if they have localhost access to the Istiod control plane. ### Patches 1.15.3 ### Workarounds No. If using 1.15.2 please upgrade to 1.15.3 or later. ### References None at this time. ### For more information If you have any questions or comments about this advisory, please email us at [[email protected]](mailto:[email protected])