CVE-2026-104254 · Package
NO FIX YET · SEE WHAT TO DO
liboqs builds with LMS/HSS stateful signatures enabled read up to 40 bytes past a caller-supplied signature or public key buffer when given a truncated signature. The read data is only hashed internally and not exposed, so the realistic impact is a verifier crash (denial of service) rather than data theft or a forged signature.
first public Sep 22, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Only systems that link liboqs 0.11.0 through 0.16.0 built with LMS/HSS stateful signature support enabled and that verify untrusted LMS or HSS-LMS signatures. Builds with the option off, or that verify only trusted signatures, are not reachable by this path.
Not affected if default-config, lms-disabled, trusted-input-only
Who cares c, hss, liboqs, lms, post-quantum
OQS_ENABLE_SIG_STFL_LMS=ON.0.11.0 through 0.16.0.0.17.0 (the source says the fix is scheduled for this version; confirm it is released).liboqs is a C-language cryptographic library that provides implementations of post-quantum cryptography algorithms. From 0.11.0 through 0.16.0, builds configured with OQS_ENABLE_SIG_STFL_LMS=ON can read beyond a caller-supplied signature buffer when an untrusted truncated LMS or HSS-LMS signature reaches OQS_SIG_STFL_verify or OQS_SIG_STFL_alg_lms_verify. In hss_validate_signature_init() in src/sig_stfl/lms/external/hss_verify_inc.c, consumed-length checks do not ensure that the bottom-level q and C fields remain available, allowing up to 32 bytes to be read past the buffer. In version 0.16.0, is_hss_public_key() also reads at offset 8 after only a four-byte length check, allowing an over-read of up to eight bytes. No valid signature is required, but the public key must be syntactically plausible. The read data is consumed only by an internal hash and is not exposed, so the supported impact is a possible verifier crash and denial of service, not memory disclosure or acceptance of an invalid signature. This issue is scheduled to be fixed in version 0.17.0.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
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.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.