| CVE ID | Severity | Package | Affected Version | Fixed Version | CVSS Score | |||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| CVE-2026-26131 | high | pkg:nuget/Microsoft.NETCore.App.Runtime.linux-x64@10.0.3 | >=10.0.0,<=10.0.3 | 10.0.4 | 7.8 | |||||||||||||||||||||
Microsoft Security Advisory CVE-2026-26131 – .NET Elevation of Privilege VulnerabilityExecutive summaryMicrosoft is releasing this security advisory to provide information about a vulnerability in .NET 10.0. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability. An elevation of privilege vulnerability exists in .NET due to improper authorization. Incorrect packaging permissions could allow an attacker to gain elevated privileges. AnnouncementAnnouncement for this issue can be found at https://github.com/dotnet/announcements/issues/386 CVSS Details
Affected Platforms
Affected Products.NET 10
Advisory FAQHow do I know if I am affected?If using an affected package listed in affected products, you're exposed to the vulnerability. How do I fix the issue?
Once you have installed the updated runtime or SDK, restart your apps for the update to take effect. Additionally, if you've deployed self-contained applications targeting any of the impacted versions, these applications are also vulnerable and must be recompiled and redeployed. Other InformationReporting Security IssuesIf you have found a potential security issue in a supported version of .NET, please report it to the Microsoft Security Response Center (MSRC) via the MSRC Researcher Portal. Further information can be found in the MSRC Report an Issue FAQ. Security reports made through MSRC may qualify for the Microsoft .NET Bounty. Details of the Microsoft .NET Bounty Program including terms and conditions are at https://aka.ms/corebounty. SupportYou can ask questions about this issue on GitHub in the .NET GitHub organization. The main repos are located at https://github.com/dotnet/runtime. The Announcements repo (https://github.com/dotnet/Announcements) will contain this bulletin as an issue and will include a link to a discussion issue. You can ask questions in the linked discussion issue. DisclaimerThe information provided in this advisory is provided "as is" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply. External LinksAcknowledgementsIgor Kovalchuk RevisionsV1.0 (March 10, 2026): Advisory published. Relevance: Since the provided time is in the future (2026) and there is no accompanying text for the CVE description, it is impossible to determine its relevance or criticality for the image. Assuming it follows typical patterns for this image, a vulnerability would likely be critical if it allowed an attacker to bypass RBAC or gain unauthorized access to the Kubernetes secrets and configmaps that the Reflector is designed to manage. Without a specific description of the flaw, its impact remains speculative and dependent on the nature of the exploit. (Note: Relevance analysis is automatically generated and may require verification.) Package URL(s):
More Info (NVD): | ||||||||||||||||||||||||||
| CVE-2026-26127 | high | pkg:nuget/Microsoft.NETCore.App.Runtime.linux-x64@10.0.3 | >=10.0.0,<=10.0.3 | 10.0.4 | 7.5 | |||||||||||||||||||||
| CVE-2026-26130 | high | pkg:nuget/Microsoft.AspNetCore.App.Runtime.linux-x64@10.0.3 | >=10.0.0,<=10.0.3 | 10.0.4 | 7.5 | |||||||||||||||||||||
| CVE-2025-45582 | medium | tar | >=0 | not fixed | 4.1 | |||||||||||||||||||||
| CVE-2026-29111 | medium | systemd | <255.4-1ubuntu8.14 | 255.4-1ubuntu8.14 | 4.1 | |||||||||||||||||||||
| CVE-2024-2236 | low | libgcrypt20 | >=0 | not fixed | 3.1 | |||||||||||||||||||||
| CVE-2024-56433 | low | shadow | >=0 | not fixed | 3.1 | |||||||||||||||||||||
| CVE-2025-5222 | low | icu | >=0 | not fixed | 3.1 | |||||||||||||||||||||
Exploitation could lead to severe consequences, such as system compromise or data loss. Requires immediate attention.
Vulnerability could be exploited relatively easily and lead to significant impact. Requires prompt attention.
Exploitation is possible but might require specific conditions. Impact is moderate. Should be addressed in a timely manner.
Exploitation is difficult or impact is minimal. Address when convenient or as part of regular maintenance.
Severity is not determined, informational, or negligible. Review based on context.
Sliplane is a simple container hosting solution. It enables you to deploy your containers in the cloud within minutes and scale up as you grow.
CVE stands for Common Vulnerabilities and Exposures. It is a standardized identifier for known security vulnerabilities, allowing developers and organizations to track and address potential risks effectively. For more information, visit cve.mitre.org.
The CVE Scanner is a powerful tool that helps you identify known vulnerabilities in your Docker images. By scanning your images against a comprehensive database of Common Vulnerabilities and Exposures (CVEs), you can ensure that your applications are secure and up-to-date. For more details, checkout the NIST CVE Database.
The CVE Scanner analyzes your Docker images against a comprehensive database of known vulnerabilities. It uses Docker Scout under the hood to provide detailed insights into affected packages, severity levels, and available fixes, empowering you to take immediate action.
With the rise of supply chain attacks, ensuring the security of your applications has become more critical than ever. CVE scanning plays a vital role in identifying vulnerabilities that could be exploited by attackers, especially those introduced through dependencies and third-party components. Regularly scanning and securing your Docker images is essential to protect your applications from these evolving threats.
Patching your Docker images is a critical step in maintaining the security and stability of your applications. By regularly updating your images to include the latest security patches, you can address known vulnerabilities and reduce the risk of exploitation. This proactive approach ensures that your applications remain resilient against emerging threats and helps maintain compliance with security best practices.
Try out Sliplane - a simple Docker hosting solution. It provides you with the tools to deploy, manage and scale your containerized applications.