CVE-2026-65388: Containerization vulnerability

Published Sep 16, 2026
·
Updated

A remote attacker who controls a container registry may be able to direct a client's token request to a host of the attacker's choice, and disclose the victim's registry credentials to that host. This vulnerability is addressed in containerization version 0.41.0.

Affected Software

1 affected component
containerization<0.41.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade containerization to a version that resolves this vulnerability.

    Fixed in 0.41.0

Event History

Sep 16, 2026
CVE Published
via MITRE·10:24 PM
Data Sourced
via MITRE·10:24 PM
DescriptionWeakness

Frequently Asked Questions

1

What must an attacker control to exploit this issue?

The attacker must control a container registry. They may then direct a client's token request to an attacker-chosen host and receive the victim's registry credentials.

2

Which versions are affected?

The issue is addressed in containerization version 0.41.0. The provided information does not specify the first affected version or whether versions after 0.41.0 are affected.

3

What is the immediate remediation?

Update containerization to version 0.41.0, which addresses the vulnerability.

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