{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-48946 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-48946 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-48946 is a low-severity vulnerability in open-quantum-safe liboqs, published on 30 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-48946 and fix it if it is affected.\n\nWhat it is: CVE-2025-48946 is a low-severity vulnerability in open-quantum-safe liboqs, published on 30 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-48946 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-2025-48946/ (Markdown: https://insights.sbomify.com/CVE-2025-48946/index.md)","id":"CVE-2025-48946","markdown":"https://insights.sbomify.com/CVE-2025-48946/index.md","name":"CVE-2025-48946","record":{"aliases":["GHSA-3rxw-4v8q-9gq5"],"analysis":{"component_type":"library","fix_type":"configuration_change","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Post-quantum crypto library","requires_auth":"none","summary":"The HQC algorithm in liboqs has a theoretical design flaw affecting key derivation security, mitigated by disabling it by default in newer versions.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"liboqs","vendor":"openquantumsafe"}],"cvss":{"score":3.7,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-327","name":"Use of a Broken or Risky Cryptographic Algorithm"}],"description":"liboqs is a C-language cryptographic library that provides implementations of post-quantum cryptography algorithms. liboqs prior to version 0.13.0 supports the HQC algorithm, an algorithm with a theoretical design flaw which leads to large numbers of malformed ciphertexts sharing the same implicit rejection value. Currently, no concrete attack on the algorithm is known. However, prospective users of HQC must take extra care when using the algorithm in protocols involving key derivation. In particular, HQC does not provide the same security guarantees as Kyber or ML-KEM. There is currently no patch for the HQC flaw available in liboqs, so HQC is disabled by default in liboqs starting from version 0.13.0. OQS will update its implementation after the HQC team releases an updated algorithm specification.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"liboqs affected by theoretical design flaw in HQC","id":"CVE-2025-48946","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"NextJS-Auth0 SDK Vulnerable to CDN Caching of Session Cookies","id":"CVE-2025-48947"},"packages":[],"prev":{"headline":"pycares has a Use-After-Free Vulnerability","id":"CVE-2025-48945"},"products":["liboqs"],"published":"2025-05-30","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: XMSS Buffer Overread Bug","id":"CVE-2026-44518","kev_date_added":null,"published":"2026-05-29"},{"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"}],"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-05-30","vendors":["open-quantum-safe"]},"summary":"The HQC algorithm in liboqs has a theoretical design flaw affecting key derivation security, mitigated by disabling it by default in newer versions.","url":"https://insights.sbomify.com/CVE-2025-48946/"}