{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-44518 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-44518 is a medium-severity vulnerability in open-quantum-safe liboqs, published on 29 May 2026."},"fix_prompt":"Check this codebase for CVE-2026-44518 and fix it if it is affected.\n\nWhat it is: CVE-2026-44518 is a medium-severity vulnerability in open-quantum-safe liboqs, published on 29 May 2026. \nExploitation: There is no known exploitation of CVE-2026-44518 in the wild and no public exploit code.\n\nAffected product: open-quantum-safe liboqs. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-44518/ (Markdown: https://insights.sbomify.com/CVE-2026-44518/index.md)","id":"CVE-2026-44518","markdown":"https://insights.sbomify.com/CVE-2026-44518/index.md","name":"CVE-2026-44518","record":{"aliases":["GHSA-wf7v-fhxj-73m2"],"analysis":null,"analysis_generated_by":null,"assigner":"GitHub_M","cpe":[{"product":"liboqs","vendor":"openquantumsafe"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"},{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"liboqs is a C-language cryptographic library that provides implementations of post-quantum cryptography algorithms. Prior to 0.16.0, an out-of-bounds read has been identified in the XMSS and XMSS^MT stateful signature verification code. When the verification function is called with a signature buffer shorter than the expected signature size for the given parameter set, the implementation does not validate the caller-supplied length and proceeds to read past the end of the buffer. The out-of-bounds bytes are consumed only as input to an internal hash computation and are not returned to the caller, so no oracle exists to leak their contents to an attacker. The primary observable effect is a possible crash (denial of service) of the verifying process if the read crosses into an unmapped memory page. This vulnerability is fixed in 0.16.0.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"liboqs: XMSS Buffer Overread Bug","id":"CVE-2026-44518","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Docling-Graph: SSRF via Missing Internal IP Validation in URLInputHandler","id":"CVE-2026-44520"},"packages":[],"prev":{"headline":"Buildah: Build breakout using malicious Containerfile and Git Smart HTTP server or GitHub release tar archive","id":"CVE-2026-44517"},"products":["liboqs"],"published":"2026-05-29","related":[{"cvss_score":9.8,"headline":"Other in n/a","id":"CVE-2024-31510","kev_date_added":null,"published":"2024-05-24"},{"cvss_score":7.4,"headline":"liboqs has a correctness error in HQC decapsulation","id":"CVE-2024-54137","kev_date_added":null,"published":"2024-12-06"},{"cvss_score":5.9,"headline":"liboqs secret-dependent branching in HQC reference implementation when compiled with Clang 17-20","id":"CVE-2025-52473","kev_date_added":null,"published":"2025-07-10"},{"cvss_score":5.9,"headline":"Information disclosure in liboqs","id":"CVE-2024-36405","kev_date_added":null,"published":"2024-06-10"},{"cvss_score":5.3,"headline":"liboqs: Heap-buffer-overflow in XMSS verification path via OID-controlled parameter mismatch (xmss_commons.c:194)","id":"CVE-2026-46344","kev_date_added":null,"published":"2026-05-29"},{"cvss_score":3.7,"headline":"liboqs affected by theoretical design flaw in HQC","id":"CVE-2025-48946","kev_date_added":null,"published":"2025-05-30"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-29","vendors":["open-quantum-safe"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-44518/"}