No KB update is listed in the collected MSRC record. Check the MSRC advisory for product releases and other remedies.
Affected products
Open Source Software
3 affected products
azl3 moby-engine 25.0.18-1 on Azure Linux 3.0
azl3 moby-engine 25.0.18-2 on Azure Linux 3.0
azl3 moby-engine 25.0.3-20 on Azure Linux 3.0
What changed
Affected products: azl3 moby-engine 25.0.18-1 on Azure Linux 3.0, azl3 moby-engine 25.0.3-20 on Azure Linux 3.0 → azl3 moby-engine 25.0.18-1 on Azure Linux 3.0, azl3 moby-engine 25.0.18-2 on Azure Linux 3.0, azl3 moby-engine 25.0.3-20 on Azure Linux 3.0
Detection template: Unknown: detection-template evidence is incomplete or retained → No Nuclei template listed
Detection template: No Nuclei template listed → Unknown: detection-template evidence is incomplete or retained
Detection template: Unknown: detection-template evidence is incomplete or retained → No Nuclei template listed
Detection template: No Nuclei template listed → Unknown: detection-template evidence is incomplete or retained
Detection template: Unknown: detection-template evidence is incomplete or retained → No Nuclei template listed
Detection template: No Nuclei template listed → Unknown: detection-template evidence is incomplete or retained
Affected products: azl3 moby-engine 25.0.3-20 on Azure Linux 3.0 → azl3 moby-engine 25.0.18-1 on Azure Linux 3.0, azl3 moby-engine 25.0.3-20 on Azure Linux 3.0
Detection template: No Nuclei template listed · Customer action: Required: apply the update → Required: follow the MSRC remediation guidance · Public disclosure: No → Unknown: not stated by MSRC · Exploitation detected: Not reported by MSRC → Unknown: not stated by MSRC
Detection template: Unknown: exploit-code evidence is incomplete or retained → No Nuclei template listed · CISA KEV: Unknown: catalog evidence is incomplete or retained → Not listed in the collected catalog
Detection template: No Nuclei template listed → Unknown: exploit-code evidence is incomplete or retained · CISA KEV: Not listed in the collected catalog → Unknown: catalog evidence is incomplete or retained
Page history
Changes are dated when recorded; day views use the last saved version from that UTC day, and citations stay fixed.
14 Nov 2026 · 08:16:23 UTCAffected productsazl3 moby-engine 25.0.18-1 on Azure Linux 3.0, azl3 moby-engine 25.0.3-20 on Azure Linux 3.0 → azl3 moby-engine 25.0.18-1 on Azure Linux 3.0, azl3 moby-engine 25.0.18-2 on Azure Linux 3.0, azl3 moby-engine 25.0.3-20 on Azure Linux 3.0
13 Nov 2026 · 12:10:20 UTCPublic detection templateUnknown: detection-template evidence is incomplete or retained → No Nuclei template listed
2 Nov 2026 · 09:04:36 UTCAffected productsazl3 moby-engine 25.0.3-20 on Azure Linux 3.0 → azl3 moby-engine 25.0.18-1 on Azure Linux 3.0, azl3 moby-engine 25.0.3-20 on Azure Linux 3.0
CISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
Which CVEs have scores here?
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.
cve-program · CVE-2026-93326
Published
Crafted Git build source can bypass certain policy validation
A build step for a Git source, crafted in a specific way, can bypass some policy validation rules. A malicious build definition can make the repository look like it is coming from a different remote URL than it really is when Git clone is happening. If policy is doing more stricter validation, for example based on commit SHA, commit data, or signatures, then all these validations still apply correctly.
Source: cve-program · CVE Program Terms of Use. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.