{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-5025 exists.","fix":"Apply the vendor's patch.","what":"CVE-2025-5025 is a medium-severity vulnerability in Haxx Curl, published on 28 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-5025 and fix it if it is affected.\n\nWhat it is: CVE-2025-5025 is a medium-severity vulnerability in Haxx Curl, published on 28 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-5025 exists.\n\nAffected product: Haxx Curl. 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-5025/ (Markdown: https://insights.sbomify.com/CVE-2025-5025/index.md)","id":"CVE-2025-5025","markdown":"https://insights.sbomify.com/CVE-2025-5025/index.md","name":"CVE-2025-5025","record":{"aliases":["ALPINE-CVE-2025-5025","AZL-62038","CLEANSTART-2026-YC05676","CURL-CVE-2025-5025","DEBIAN-CVE-2025-5025","ECHO-fa7f-8ecf-75e7","GHSA-x8ch-h5vv-q6cm","JLSEC-2026-433","MINI-v932-4r2f-cqgq"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"curl library","requires_auth":"none","summary":"Attackers can bypass certificate pinning in curl when using QUIC with wolfSSL, allowing connections to impostor servers without detection.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"curl","cpe":[{"product":"curl","vendor":"haxx"}],"cvss":{"score":4.8,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"libcurl supports *pinning* of the server certificate public key for HTTPS transfers. Due to an omission, this check is not performed when connecting with QUIC for HTTP/3, when the TLS backend is wolfSSL. Documentation says the option works with wolfSSL, failing to specify that it does not for QUIC and HTTP/3. Since pinning makes the transfer succeed if the pin is fine, users could unwittingly connect to an impostor server without noticing.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2025-07-22","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2025-07-22T02:52:06Z","kind":"github_poc","ref":"https://github.com/KiPhuong/cve-2025-5025","stars":0,"title":null}],"tier":"weaponised"},"has_fix":true,"headline":"No QUIC certificate pinning with wolfSSL","id":"CVE-2025-5025","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"haxx:curl","products":["haxx:curl"],"type":"security_feature_bypass","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.","id":"CVE-2025-5026"},"packages":[],"prev":{"headline":"Gnome-remote-desktop: uncontrolled resource consumption due to malformed rdp pdus","id":"CVE-2025-5024"},"products":["curl"],"published":"2025-05-28","related":[{"cvss_score":9.8,"headline":"Negotiate ambient user conn reuse","id":"CVE-2026-19931","kev_date_added":null,"published":"2026-09-06"},{"cvss_score":9.8,"headline":"HTTP/2 stream-dependency tree UAF","id":"CVE-2026-10536","kev_date_added":null,"published":"2026-07-03"},{"cvss_score":9.8,"headline":"cross-origin Digest auth state leak","id":"CVE-2026-11856","kev_date_added":null,"published":"2026-07-03"},{"cvss_score":9.8,"headline":"SASL double-free","id":"CVE-2026-8925","kev_date_added":null,"published":"2026-07-03"},{"cvss_score":9.8,"headline":"stale proxy password leak","id":"CVE-2026-9079","kev_date_added":null,"published":"2026-07-03"},{"cvss_score":9.8,"headline":"Code injection in curl","id":"CVE-2016-4606","kev_date_added":null,"published":"2020-02-21"},{"cvss_score":9.8,"headline":"Information disclosure in n/a","id":"CVE-2016-9953","kev_date_added":null,"published":"2018-03-12"}],"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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-05-30","vendors":["curl"]},"summary":"Attackers can bypass certificate pinning in curl when using QUIC with wolfSSL, allowing connections to impostor servers without detection.","url":"https://insights.sbomify.com/CVE-2025-5025/"}