CVE-2024-40635: containerd has an integer overflow in User ID handling

Published Mar 17, 2025
·
Updated

Impact A bug was found in containerd where containers launched with a User set as a UID:GID larger than the maximum 32-bit signed integer can cause an overflow condition where the container ultimately runs as root (UID 0). This could cause unexpected behavior for environments that require containers to run as a non-root user.

Patches This bug has been fixed in the following containerd versions:

2.0.4 (Fixed in https://github.com/containerd/containerd/commit/1a43cb6a1035441f9aca8f5666a9b3ef9e70ab20) 1.7.27 (Fixed in https://github.com/containerd/containerd/commit/05044ec0a9a75232cad458027ca83437aae3f4da) 1.6.38 (Fixed in https://github.com/containerd/containerd/commit/cf158e884cfe4812a6c371b59e4ea9bc4c46e51a)

Users should update to these versions to resolve the issue.

Workarounds Ensure that only trusted images are used and that only trusted users have permissions to import images.

Credits The containerd project would like to thank Benjamin Koltermann and emxll for responsibly disclosing this issue in accordance with the containerd security policy.

References https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-40635

For more information

If you have any questions or comments about this advisory:

Open an issue in containerd Email us at security@containerd.io

To report a security issue in containerd: Report a new vulnerability Email us at security@containerd.io

Other sources

containerd has an integer overflow in User ID handling

Microsoft

containerd is an open-source container runtime. A bug was found in containerd prior to versions 1.6.38, 1.7.27, and 2.0.4 where containers launched with a User set as a UID:GID larger than the maximum 32-bit signed integer can cause an overflow condition where the container ultimately runs as root (UID 0). This could cause unexpected behavior for environments that require containers to run as a non-root user. This bug has been fixed in containerd 1.6.38, 1.7.27, and 2.04. As a workaround, ensure that only trusted images are used and that only trusted users have permissions to import images.

Debian

Affected Software

15 affected componentsFixes available
debian/containerd<=1.4.13~ds1-1~deb11u4, <=1.4.13~ds1-1~deb11u2, <=1.6.20~ds1-1+deb12u1, <=1.7.24~ds1-4
go/github.com/containerd/containerd<1.6.38
1.6.38
go/github.com/containerd/containerd>=1.7.0-beta.0<1.7.27
1.7.27
go/github.com/containerd/containerd/v2<2.0.4
2.0.4
IBM Concert Software<=1.0.0-1.1.0
linuxfoundation Containerd<1.6.38
linuxfoundation Containerd>=1.7.0<1.7.27
linuxfoundation Containerd>=2.0.0<2.0.4
Debian Debian Linux=11.0
Microsoft azl3 containerd2 2.0.0-8
Microsoft azl3 containerd 1.7.13-8
Microsoft azl3 moby-containerd-cc 1.7.7-9
Microsoft azl3 containerd2 2.0.0-9
Microsoft cbl2 moby-containerd-cc 1.7.7-11
Microsoft cbl2 moby-containerd 1.6.26-11

Event History

Mar 17, 2025
Advisory Published
via GitHub·09:24 PM
CVE Published
via MITRE·09:32 PM
Data Sourced
via MITRE·09:32 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·10:15 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·10:15 PM
RemedyAffected Software
Mar 30, 2025
Data Sourced
via Ubuntu·09:40 PM
RemedyDescriptionSeverityAffected Software
May 5, 2025
Data Sourced
via Microsoft·07:00 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·07:00 AM
Affected Software
Updated
via Microsoft·07:00 AM
DescriptionSeverity
Sep 8, 2025
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2024-40635?

CVE-2024-40635 is considered to have a critical severity as it allows containers to run as root, potentially compromising the host system.

2

How do I fix CVE-2024-40635?

To fix CVE-2024-40635, upgrade containerd to version 1.6.38, 1.7.27, or 2.0.4 or later, depending on your installation.

3

What versions of containerd are affected by CVE-2024-40635?

CVE-2024-40635 affects containerd versions prior to 1.6.38, 1.7.0-beta.0 to 1.7.27, and below 2.0.4.

4

What is the cause of CVE-2024-40635?

CVE-2024-40635 is caused by a bug where containers launched with a User set as a UID:GID larger than the maximum 32-bit signed integer lead to an overflow condition.

5

What impact does CVE-2024-40635 have on container environments?

CVE-2024-40635 can result in unexpected behavior, including containers running with elevated privileges as root, which poses security risks.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203