{"answers":{"affected":"2 open source packages ship an affected version, including yapi-vendor. It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-70058 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-70058 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-70058 is a high-severity vulnerability in n/a, published on 23 Feb 2026. 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-70058 and fix it if it is affected.\n\nWhat it is: CVE-2025-70058 is a high-severity vulnerability in n/a, published on 23 Feb 2026. 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-70058 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- yapi-vendor (npm): affected all versions up to 1.12.0; no fix listed\n- yapi-vendor (npm): affected all versions up to 1.12.0; no fix listed\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-70058/ (Markdown: https://insights.sbomify.com/CVE-2025-70058/index.md)","id":"CVE-2025-70058","markdown":"https://insights.sbomify.com/CVE-2025-70058/index.md","name":"CVE-2025-70058","record":{"aliases":["GHSA-663h-2vr3-ghrj"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"YAPI API management","requires_auth":"none","summary":"YAPI disables TLS certificate validation, allowing attackers to intercept or manipulate HTTPS traffic via man-in-the-middle attacks.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"yapi","vendor":"ymfe"}],"cvss":{"score":7.4,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"An issue pertaining to CWE-295: Improper Certificate Validation was discovered in YMFE yapi v1.12.0. The application disables TLS/SSL certificate validation by setting 'rejectUnauthorized': false in the HTTPS agent configuration for Axios requests","ecosystems":["npm"],"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":"yapi disables TLS/SSL certificate validation via rejectUnauthorized: false in Axios HTTPS agent","id":"CVE-2025-70058","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"weak_cryptography","year":"2025"},"n_packages":2,"n_references":3,"next":{"headline":"Denial of service in n/a","id":"CVE-2025-70059"},"packages":[{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["1.12.0"],"package":"yapi-vendor","purl":null,"source":"GHSA-663h-2vr3-ghrj"},{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["1.12.0"],"package":"yapi-vendor","purl":"pkg:npm/yapi-vendor","source":"GHSA-663h-2vr3-ghrj"}],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2025-70050"},"products":["n/a"],"published":"2026-02-23","related":[{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2025-70059","kev_date_added":null,"published":"2026-03-09"},{"cvss_score":5.4,"headline":"Cross-site scripting in n/a","id":"CVE-2025-70060","kev_date_added":null,"published":"2026-03-09"},{"cvss_score":5.4,"headline":"Cross-site Scripting in yapi-vendor","id":"CVE-2021-36686","kev_date_added":null,"published":"2023-01-26"},{"cvss_score":5.4,"headline":"Cross-site Scripting in yapi-vendor","id":"CVE-2018-17574","kev_date_added":null,"published":"2018-09-28"},{"cvss_score":5.1,"headline":"Weak JSON Web Token in yapi-vendor","id":"CVE-2021-27884","kev_date_added":null,"published":"2021-03-01"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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":"total"},"state":"PUBLISHED","updated":"2026-02-25","vendors":["n/a"]},"summary":"YAPI disables TLS certificate validation, allowing attackers to intercept or manipulate HTTPS traffic via man-in-the-middle attacks.","url":"https://insights.sbomify.com/CVE-2025-70058/"}