Container image tampering via link-followed resources
Published Jul 14, 2026 · Updated Jul 14, 2026
Link-following in Microsoft.NET.Build.Containers in .NET SDK 8.0, 9.0, and 10.0 allows local users to inject container-image resources. Microsoft has not published the specific function; the container build process follows attacker-controlled links when collecting resources for another user's image. A low-privileged attacker must share the build host with another user, and successful exploitation can alter that user's image contents.
Summary
What happened
Link-following in Microsoft.NET.Build.Containers in .NET SDK 8.0, 9.0, and 10.0 allows local users to inject container-image resources. Microsoft has not published the specific function; the container build process follows attacker-controlled links when collecting resources for another user's image. A low-privileged attacker must share the build host with another user, and successful exploitation can alter that user's image contents.
The record
- CVE
- CVE-2026-50526
- Published
- Jul 14, 2026
- Updated
- Jul 14, 2026
- Vendor
- Microsoft
- Product
- .NET 9.0
- Classifications
- CWE-345, CWE-59, T1195.002
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 14, 2026CVE publishedPublication date reported by the CVE source.
- Jul 14, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=9.0.0 <9.0.18
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo