GHSA-42mr-jpwh-m9rv
First published: Mon May 05 2025(Updated: )
In Buoyant Edge releases before edge-25.2.1 and Enterprise for Linkerd releases 2.16.* before 2.16.5, 2.17.* before 2.17.2, and 2.18.* before 2.18.0, resource exhaustion can occur for Linkerd proxy metrics.
| Affected Software | Affected Version | How to fix |
|---|---|---|
| go/github.com/linkerd/linkerd2 | <0.6.0-20250501173313-4823b7af3e1e | 0.6.0-20250501173313-4823b7af3e1e |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of GHSA-42mr-jpwh-m9rv?
The severity of GHSA-42mr-jpwh-m9rv is classified as high due to potential resource exhaustion in Linkerd proxy metrics.
How do I fix GHSA-42mr-jpwh-m9rv?
To fix GHSA-42mr-jpwh-m9rv, upgrade to Buoyant Edge version edge-25.2.1 or Linkerd versions 2.16.5, 2.17.2, or 2.18.0 or later.
What symptoms indicate the presence of GHSA-42mr-jpwh-m9rv?
Symptoms of GHSA-42mr-jpwh-m9rv may include degraded performance or unresponsive services due to resource exhaustion.
Which versions are affected by GHSA-42mr-jpwh-m9rv?
GHSA-42mr-jpwh-m9rv affects Buoyant Edge releases prior to edge-25.2.1 and Linkerd versions 2.16.* before 2.16.5, 2.17.* before 2.17.2, and 2.18.* before 2.18.0.
Who should be concerned about GHSA-42mr-jpwh-m9rv?
Organizations using affected versions of Buoyant Edge or Linkerd should be concerned about GHSA-42mr-jpwh-m9rv and take immediate action to remediate.
- collector/github-advisory-latest
- source/GitHub
- alias/GHSA-42mr-jpwh-m9rv
- alias/CVE-2025-43915
- agent/software-canonical-lookup
- agent/last-modified-date
- agent/severity
- agent/references
- agent/weakness
- agent/source
- agent/softwarecombine
- agent/tags
- agent/type
- agent/description
- agent/first-publish-date
- agent/event
- package-manager/go