Process-memory disclosure via incomplete close-frame initialization
Published May 15, 2026 · Updated Aug 28, 2026
Uninitialized memory disclosure in ws 8.0.0 through 8.20.0 allows remote authenticated users to read process memory via close frames. Sender.close allocates the frame payload with Buffer.allocUnsafe() but does not overwrite it when the reason is a non-Uint8 TypedArray. Exploitation requires application code to misuse close() with that reason type; the peer receives residual bytes, with no integrity or availability impact.
Summary
What happened
Uninitialized memory disclosure in ws 8.0.0 through 8.20.0 allows remote authenticated users to read process memory via close frames. Sender.close allocates the frame payload with Buffer.allocUnsafe() but does not overwrite it when the reason is a non-Uint8 TypedArray. Exploitation requires application code to misuse close() with that reason type; the peer receives residual bytes, with no integrity or availability impact.
The record
- CVE
- CVE-2026-45736
- Published
- May 15, 2026
- Updated
- Aug 28, 2026
- Vendor
- 389 Directory Server
- Product
- Red Hat Quay
- Classifications
- CWE-908
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 15, 2026CVE publishedPublication date reported by the CVE source.
- Aug 28, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Upstream TypedArray close-frame proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo