# Weave GitOps leaked cluster credentials into logs on connection errors in github.com/weaveworks/weave-gitops

Advisory record · `GHSA-xggc-qprg-x6mw`

- **Identifiers:** `GHSA-xggc-qprg-x6mw` · `CVE-2022-31098` · `GO-2022-0502`
- **State:** Confirmed
- **Severity:** CVSS 9.0 Critical
- **Critical:** Yes: CVSS 9+
- **Weakness (CWE):** [CWE-532](https://cwe.mitre.org/data/definitions/532.html)
- **Tags:** [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md)
- **Published:** 21 Aug 2024
- **Updated:** 3 Mar 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 21 Aug 2024, 15:11 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Critical

Critical, because:

- CVSS score 9.0: 9.0 or more.

How we decide what’s critical: <https://agentprime.io/advisories/critical.md>

## Affected packages

- `github.com/weaveworks/weave-gitops` (Go): affected `<0.8.1-rc.6`; fixed in `0.8.1-rc.6`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> github.com/weaveworks/weave-gitops before 0.8.1-rc.6 leaked cluster credentials into logs on connection errors. The source gives few details on who can read those logs or what access an attacker would need. Upgrade to 0.8.1-rc.6.

Written 10 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 9.0 Critical, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.013, the 70th percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the GitHub Advisory Database, published 21 Aug 2024. New records show when each source confirmed them.

## Sources

- [GitHub Advisory Database: GHSA-xggc-qprg-x6mw](https://github.com/advisories/GHSA-xggc-qprg-x6mw)
- [OSV: GHSA-xggc-qprg-x6mw](https://osv.dev/vulnerability/GHSA-xggc-qprg-x6mw)
- <https://github.com/weaveworks/weave-gitops/security/advisories/GHSA-xggc-qprg-x6mw>
- <https://nvd.nist.gov/vuln/detail/CVE-2022-31098>
- <https://github.com/weaveworks/weave-gitops/commit/567356f471353fb5c676c77f5abc2a04631d50ca>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-xggc-qprg-x6mw>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-xggc-qprg-x6mw/>. Everything for agents: <https://agentprime.io/llms.txt>.
