In Mbed TLS 3.2.0 though 3.6.6 and 4.0.0 through 4.1.0, an attacker who can cause an entropy source to fail can remove or inject bytes into the start of the TLS stream.
Published October 3, 2026Updated October 3, 2026
Source data
Overview
Full source title
In Mbed TLS 3.2.0 though 3.6.6 and 4.0.0 through 4.1.0, an attacker who can cause an entropy source to fail can remove or inject bytes into the start of the TLS stream. This only affects TLS 1.3 servers.
The source does not supply a plain-text overview. Review the authoritative advisory for the full description.
Impact & technical details
A separate impact classification is not supplied in this record. See the source advisory.
- CVSS base score
- 2.9 / 10
- CVSS vector
- CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
Highest base score supplied by MSRC for this record; the vector belongs to that score. Ratings can vary by product. Microsoft Important is displayed as High; Moderate is displayed as Medium.
Affected products
- azl3 qemu 10.1.0-1 on Azure Linux 3.0
Source guidance
Remediation
- Release Notes
Patch availability is not confirmed by this dataset. Consult the vendor before selecting a remediation.
GTP recommendation · Rule-based guidance
Recommended next step
Review affected Microsoft products and apply the applicable security updates through your organization's normal patch-management process. Confirm availability and prerequisites in the Microsoft advisory.
Authoritative sources & updates
Findings and update information come from the linked publishers. GTP compiles the public record and provides the recommendation above. CVSS ratings shown here come from Microsoft. NVD references provide additional public context.
Managed by GTP?
Griffin Technology Partners managed customers may receive additional environment-specific security guidance and remediation assistance through their managed services relationship.
Security bulletins are provided for informational purposes and compiled from authoritative public sources. Vulnerability applicability varies by environment. Validate affected products, configuration, compatibility requirements, and vendor guidance before making production changes.