Back to vendor advisories
Microsoft Security Response CenterCVE-2026-28387

Potential Use-after-free in DANE Client Code

MediumVendor CVSS 7.0 / 10 1 CVE Published Apr 9, 2026 at 1:02 AM UTC

Summary

Mariner

Products covered

  • azl3 openssl 3.3.5-5 on Azure Linux 3.0

  • cbl2 edk2 20230301gitf80f052277c8-47 on CBL-Mariner 2.0

  • cbl2 openssl 1.1.1k-39 on CBL-Mariner 2.0

  • azl3 openssl 3.3.5-4 on Azure Linux 3.0

  • cbl2 edk2 20230301gitf80f052277c8-47 on CBL Mariner 2.0

  • cbl2 hvloader 1.0.1-18 on CBL Mariner 2.0

  • cbl2 openssl 1.1.1k-39 on CBL Mariner 2.0

  • azl3 nodejs24 24.13.0-3 on Azure Linux 3.0

Show 5 more products
  • azl3 qemu 9.1.0-1 on Azure Linux 3.0

  • azl3 rust 1.75.0-27 on Azure Linux 3.0

  • azl3 rust 1.90.0-6 on Azure Linux 3.0

  • azl3 nodejs24 24.14.1-1 on Azure Linux 3.0

  • cbl2 hvloader 1.0.1-18 on CBL-Mariner 2.0

Remediation

CBL-Mariner Releases Release Notes

Vendor-listed fixes

  • 3.3.7-2

  • 1.1.1k-40

  • 3.3.7-1

CVEs in this advisory 1

Update history

What changed in later vendor updates

SecurityAlert records field-level changes from the point we begin following a bulletin. Earlier vendor changes may not have a field-by-field record.

    • CVSS changed from 8.1 to 7.0.
    • Removed affected products: azl3 openvmm 0.2.0-1 on Azure Linux 3.0.
    • The vendor changed its remediation guidance.
    • CVSS changed from 7.0 to 8.1.
    • Added affected products: azl3 openvmm 0.2.0-1 on Azure Linux 3.0.
    • The vendor changed its remediation guidance.
    • The vendor changed the advisory's last-updated date.
    • Added affected products: cbl2 edk2 20230301gitf80f052277c8-47 on CBL-Mariner 2.0, cbl2 hvloader 1.0.1-18 on CBL-Mariner 2.0, cbl2 openssl 1.1.1k-39 on CBL-Mariner 2.0.
    • Added fixed versions: 3.3.7-2.
    • The vendor changed its remediation guidance.

Updates

  1. Published by Microsoft Security Response Center

    The publication date reported by the vendor.

  2. Added to SecurityAlert

    We collected the advisory from the official source.

  3. Updated by Microsoft Security Response Center

    The vendor changed the advisory after it was first published.

  4. Confirmed at the source

    Our collector saw this advisory during a later source check.