Recorded 16 Oct 2026 at 07:41 UTC. This is what ChangeIntel recorded, including the title, summary, facts and links. It is not a statement of the source's current position.
See the latest record.
The historical field “Public exploit code” recorded Nuclei detection-template membership. It did not establish exploit availability. The original recorded fields remain below.
The historical “Publicly disclosed: No” field could represent a missing MSRC assessment. It does not establish that the vulnerability was undisclosed. The original recorded fields remain below.
CVEMicrosoft Security Response Center
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.
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.
16 Oct 2026 · 07:41:54 UTCAffected productsazl3 nodejs 24.21.0-1 on Azure Linux 3.0, azl3 qemu 10.1.0-1 on Azure Linux 3.0 → azl3 nodejs 24.21.0-1 on Azure Linux 3.0