CVE-2025-43915: Resource Exhaustion Vulnerability in Linkerd Package

github.com/linkerd/linkerd2 Updated 02 Oct 2025

Summary

20/05/2025
No i
Moderate
6.5

CVE-2025-43915: Linkerd resource exhaustion vulnerability in github.com/linkerd/linkerd2. Affected versions are not published. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

Linkerd is a service mesh for cloud-native applications, providing features such as load balancing, traffic management, and observability. It is designed to enhance the reliability and security of microservices architectures. However, it is susceptible to resource exhaustion vulnerabilities, which can lead to service disruptions and degraded performance.

Vulnerability Detail

The Linkerd resource exhaustion vulnerability, identified as CVE-2025-43915, arises from improper resource management within the Linkerd package (github.com/linkerd/linkerd2). This vulnerability can be exploited by an attacker to consume excessive resources, potentially leading to denial of service (DoS) conditions. The issue is present in all versions prior to 0.6.0-20250501173313-4823b7af3e1e, making it critical for users to address this flaw promptly.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary measure, users can limit the resource allocation for Linkerd instances to mitigate the impact of potential resource exhaustion. This can be done by configuring resource limits in the deployment specifications, for example:

resources: limits: cpu: "500m" memory: "512Mi"

Conclusion

The Linkerd resource exhaustion vulnerability (CVE-2025-43915) poses a significant risk to applications using the affected package. It is crucial for users to update to the patched version to ensure the security and reliability of their services. Additionally, utilizing tools like Vulert can help in monitoring for such vulnerabilities in the future.

See every vulnerability recorded for github.com/linkerd/linkerd2 →

Share this vulnerability

FAQ

The vulnerability allows attackers to consume excessive resources, potentially leading to service disruptions.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

All versions prior to 0.6.0-20250501173313-4823b7af3e1e are affected by this vulnerability.

Update to the patched version of Linkerd as soon as possible to mitigate the vulnerability.

Yes, Vulert can monitor and alert you in real-time for open-source vulnerabilities in your software using just Gopkg.lock.

Related vulnerabilities

Recent vulnerabilities recorded for github.com/linkerd/linkerd2.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback