What is the CVSS score of CVE-2025-70058?

CVE-2025-70058 has a CVSS 3.1 base score of 7.4 (High). CVSS vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N. EPSS exploitation probability: 0.0%.

How to fix or mitigate CVE-2025-70058?

Within 24 hours: Inventory all systems running yapi v1.12.0 and isolate them from external networks if possible; document business criticality of each instance. Within 7 days: Implement network-level controls (WAF rules, VPN requirement, IP whitelisting) to restrict access to yapi instances; deploy internal monitoring for suspicious HTTPS traffic. Within 30 days: Migrate to a patched version when available or decommission affected instances; conduct audit of data accessed through vulnerable systems during exposure period.

Yapi CVE-2025-70058

HIGH

Improper Certificate Validation (CWE-295)

2026-02-23 cve@mitre.org

GHSA-663h-2vr3-ghrj

TLS Yapi Ymfe

7.4

CVSS 3.1 · NVD

View

Vulnerability Assessment

Weakness	CWE CWE-295 OWASP Top 10:2025 A07:2025 - Authentication Failures ASVS 5.0 V12 - Secure Communication Certificate validation
Impact	CVSS 7.4 (HIGH). Attack vector: Network. Complexity: High. Privileges required: None. User interaction: None. Exploitation no authentication required.
Exploit ScenarioDerived	An attacker without authentication could exploit this vulnerability to compromise the affected system.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).

No patch listed yet 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 12, 2026

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 [CVSS 7.4 HIGH]

RemediationAI

Monitor vendor advisories for a patch. Restrict network access to the affected service where possible.

Affected Packages

npm yapi-vendor no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in npm

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Classified as CWE-295 (Improper Certificate Validation). Affects Yapi. 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

Know when Yapi gets its next vulnerability

Watch products and get an email when something new is published
Check this CVE against your own stack and servers
Exploit and PoC references, threat intelligence from 22 sources

Continue with Google Continue with GitHub

No credit card · 7-day full trial

Severity by source

NVD PRIMARY 7.4 HIGH

AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector

Network

Attack Complexity

High

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

None

DescriptionCVE.org

Executive ViewAI

Why It Matters

YMFE yapi v1.12.0 contains a critical certificate validation flaw that disables TLS/SSL security checks, exposing the organization to man-in-the-middle attacks and data interception. This vulnerability affects any deployment of yapi v1.12.0 and requires immediate assessment to determine exposure scope and implement protective measures.

Business Impact: High

Compensating Controls

Network segmentation to restrict yapi access to trusted internal networks only; implement WAF rules to monitor and log all HTTPS requests to yapi instances; require VPN or IP-based access controls; disable external API integrations until patch is available; increase monitoring and logging of certificate validation errors and TLS handshake failures; consider disabling yapi's external API call features if not business-critical.

Threat Intelligence Overview

EPSS Score

0.0%

Top 94% exploitable

Data Quality

4 sources

Confidence: Medium

NVD

CVE.org

EPSS

GitHub

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue

Severity HIGH

CISA KEV No

Public POC No

EPSS 0.0%

Patch available No

Active threat No

Deciding rule

HIGH severity (CVSS 7.0-8.9)

What every action level means

Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.

Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.

This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.

This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.

Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.