{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-52473 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2025-52473 is a medium-severity vulnerability in open-quantum-safe liboqs, published on 10 Jul 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-52473 and fix it if it is affected.\n\nWhat it is: CVE-2025-52473 is a medium-severity vulnerability in open-quantum-safe liboqs, published on 10 Jul 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-52473 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-52473/ (Markdown: https://insights.sbomify.com/CVE-2025-52473/index.md)","id":"CVE-2025-52473","markdown":"https://insights.sbomify.com/CVE-2025-52473/index.md","name":"CVE-2025-52473","record":{"aliases":["GHSA-qq3m-rq9v-jfgm","openSUSE-SU-2025:15339-1"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Post-quantum crypto library","requires_auth":"none","summary":"A local attacker can recover secret keys from the HQC implementation in liboqs when compiled with specific Clang optimization levels, exposing cryptographic secrets.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"liboqs","vendor":"openquantumsafe"}],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"liboqs is a C-language cryptographic library that provides implementations of post-quantum cryptography algorithms. Multiple secret-dependent branches have been identified in the reference implementation of the HQC key encapsulation mechanism when it is compiled with Clang for optimization levels above -O0 (-O1, -O2, etc). A proof-of-concept local attack exploits this secret-dependent information to recover the entire secret key. This vulnerability is fixed in 0.14.0.","ecosystems":["openSUSE:Tumbleweed"],"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 secret-dependent branching in HQC reference implementation when compiled with Clang 17-20","id":"CVE-2025-52473","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":1,"n_references":2,"next":{"headline":"WeGIA SQL Injection Vulnerability in id Parameter on control.php Endpoint","id":"CVE-2025-52474"},"packages":[{"ecosystem":"openSUSE:Tumbleweed","fixed":["0.14.0-1.1"],"introduced":["0"],"last_affected":[],"package":"liboqs","purl":"pkg:rpm/opensuse/liboqs\u0026distro=openSUSE%20Tumbleweed","source":"openSUSE-SU-2025:15339-1"}],"prev":{"headline":"XWiki Platform vulnerable to HQL injection via wiki and space search REST API","id":"CVE-2025-52472"},"products":["liboqs"],"published":"2025-07-10","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":"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"},{"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":"CC BY 4.0","name":"SUSE","prefix":"openSUSE"},{"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-07-10","vendors":["open-quantum-safe"]},"summary":"A local attacker can recover secret keys from the HQC implementation in liboqs when compiled with specific Clang optimization levels, exposing cryptographic secrets.","url":"https://insights.sbomify.com/CVE-2025-52473/"}