Findings

CVE-2026-39824

NewNTUnicodeString does not check for string length overflow.

Published May 22, 2026 · updated Jul 23, 2026

NewNTUnicodeString does not check for string length overflow. When provided with a string that overflows the maximum size of a NTUnicodeString (a 16-bit number of bytes), it returns a truncated string rather than an error.

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. May 22, 2026 · NIST NVD

    Detected

    NewNTUnicodeString does not check for string length overflow. When provided with a string that overflows the maximum size of a NTUnicodeString (a 16-bit number of bytes), it returns a truncated string rather than an error.

  2. Jul 23, 2026 · NIST NVD

    Updated

    NewNTUnicodeString does not check for string length overflow. When provided with a string that overflows the maximum size of a NTUnicodeString (a 16-bit number of bytes), it returns a truncated string rather than an error.

Sources

  • CVE.orgVulnerability recordCVE-2026-39824

    Official CVE identifier

    cve.org
  • NIST NVDVulnerability recordCVE-2026-39824

    NewNTUnicodeString does not check for string length overflow. When provided with a string that overflows the maximum size of a NTUnicodeString (a 16-bit number of bytes), it returns a truncated string rather than an error.

    nvd.nist.gov

References

CVE-2026-39824 · ZeroDay Findings