CVE-2026-126792 · Other
NO FIX YET
A fixed-size output buffer in the library's key-management request-building code assumes a key size that is never checked, so oversized data can be written past the end of the heap buffer. The demonstrated result is memory corruption that crashes the client process, and an attacker must first be able to control the embedding application's key-provider configuration.
first public Nov 13, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Applications that embed this library and supply their own cryptographic callback implementation are the ones the description covers. The attacker needs to control the in-process key-management provider configuration, which is a high-privilege position, so applications that do not use custom key providers are less exposed. The sources do not name the affected library, its versions or a fixed release.
Not affected if default-config, no-custom-crypto-callbacks
Who cares custom-crypto-callbacks, embedded-crypto, key-management
Unknown from the sources.
No fix yet, per the sources.
A memory-safety flaw in the key-management request-building component of the library can lead to an out-of-bounds write on the heap. A fixed-size output buffer is used under an assumption about cryptographic key size that is never validated, so when the library is embedded by a caller that supplies its own cryptographic callback implementation, data larger than the buffer can be written past its end. Exploitation requires the ability to control the embedding application's in-process key-management provider configuration, a high-privilege position. The demonstrated impact is memory corruption resulting in abnormal termination of the client process.
This page as .md · .json · CVSS:4.0/AV:L/AC:H/AT:P/PR:H/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.