Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦 npm

GHSA-663h-2vr3-ghrj

HIGH

GHSA-663h-2vr3-ghrj is a high-severity (CVSS 7.4) CWE-295 vulnerability in yapi-vendor. O3 Security confirms whether GHSA-663h-2vr3-ghrj is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

yapi disables TLS/SSL certificate validation via rejectUnauthorized: false in Axios HTTPS agent

Also known asCVE-2025-70058
Published
Feb 23, 2026
Updated
Feb 25, 2026
Affected
1 pkg
Patched
None yet
Exploits
None indexed

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

0other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
yapi-vendornpm
827downloads / week

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

Affected Packages

1 total
EcosystemPackageVulnerable rangeFix
📦npmyapi-vendorall versionsNo fix

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for yapi-vendor. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Remediation status

    No patched version of yapi-vendor has shipped for GHSA-663h-2vr3-ghrj yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

  3. Mitigate without a patch

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-663h-2vr3-ghrj is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-663h-2vr3-ghrj. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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
O3 Security · Impact-Aware SCA

Is GHSA-663h-2vr3-ghrj in your dependencies?

O3 detects GHSA-663h-2vr3-ghrj across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.