CVE-2021-41103: Insufficiently restricted permissions on plugin directories in github.com/containerd/containerd

Summary

21/08/2024
Yes i
Moderate
5.9

CVE-2021-41103: Insufficiently restricted permissions on plugin directories in github.com/containerd/containerd. Affects github.com/containerd/containerd across 2 version ranges.

< 1.4.11 >= 1.5.0, < 1.5.7

Fixed in 1.4.11 or 1.5.7, depending on the release line you run. How to fix ↓

Also tracked for

The same CVE-2021-41103 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.

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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

github.com/containerd/containerd is an open-source container runtime for Linux that provides a platform-agnostic API for container lifecycle management. It is widely used in various container orchestration systems and platforms. This vulnerability arises from insufficiently restricted permissions on plugin directories within containerd.

Vulnerability Detail

The vulnerability in github.com/containerd/containerd allows an attacker to gain unauthorized access to plugin directories. This could lead to arbitrary code execution, privilege escalation, or unauthorized access to sensitive information. The issue stems from improper permission settings on plugin directories, which can be exploited by an attacker with local access to the system. The vulnerability affects versions 0.x and 1.5.0 to 1.5.6 of containerd.

How To Fix

Latest published version: v1.7.36 as of 22 Oct 2026

go get github.com/containerd/containerd@v1.7.36

Upgrading to it may include breaking changes; the versions below are the minimum fixed release for this vulnerability.

If you can't move to the latest

The minimum fixed version depends on the release line you run.

  • < 1.4.11 1.4.11
    go get github.com/containerd/containerd@v1.4.11
  • >= 1.5.0, < 1.5.7 1.5.7
    go get github.com/containerd/containerd@v1.5.7

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Workaround

There is no known workaround for this vulnerability. It is crucial to update to a patched version of containerd to address the issue.

Conclusion

The vulnerability in github.com/containerd/containerd arises from insufficiently restricted permissions on plugin directories. It is crucial for users to update to a patched version of containerd (1.5.7 or later) to mitigate the risk of unauthorized access and potential exploitation.

See every vulnerability recorded for github.com/containerd/containerd →

Share this vulnerability

FAQ

Containerd is an open-source container runtime for Linux that provides a platform-agnostic API for container lifecycle management. It is widely used in various container orchestration systems and platforms.

The vulnerability allows an attacker to gain unauthorized access to plugin directories, potentially leading to arbitrary code execution, privilege escalation, or unauthorized access to sensitive information.

Users of containerd versions 0.x and 1.5.0 to 1.5.6 are affected by this vulnerability.

No, there is no known workaround for this vulnerability. It is essential to update to a patched version of containerd.

To fix this vulnerability, update containerd to version 1.5.7 or later, which includes the necessary fixes to properly restrict permissions on plugin directories.

Related vulnerabilities

Recent vulnerabilities recorded for github.com/containerd/containerd.

How To Fix

Latest published version: v1.7.36 as of 22 Oct 2026

go get github.com/containerd/containerd@v1.7.36

Upgrading to it may include breaking changes; the versions below are the minimum fixed release for this vulnerability.

If you can't move to the latest

The minimum fixed version depends on the release line you run.

  • < 1.4.11 1.4.11
    go get github.com/containerd/containerd@v1.4.11
  • >= 1.5.0, < 1.5.7 1.5.7
    go get github.com/containerd/containerd@v1.5.7

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. 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