Is CVE-2025-70058 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2025-70058 being exploited in the wild.

How severe is CVE-2025-70058?

Low severity, with a CVSS score of 3.1, published 23 February 2026.

Which products and versions are affected?

yapi-vendor (npm) SEMVER:introduced=0,last_affected=1.12.0; Ymfe Yapi 1.12.0 and earlier.

Is there a fix for CVE-2025-70058?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2025-70058 attacked?

It is attacked over the network.

Am I affected by CVE-2025-70058?

Check whether you run yapi-vendor (npm) or Ymfe Yapi at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2025-70058: YMFE yapi TLS/SSL certificate validation bypass

CVE-2025-70058 · Severity: low · CVSS 3.1 · Published 2026-02-23

yapi is a popular API documentation and testing tool used by developers to manage and collaborate on API specifications. The application disables certificate validation in HTTPS connections, allowing attackers on the network to impersonate servers and intercept sensitive data including API credentials, test data, and configuration information. This creates a man-in-the-middle attack risk, particularly dangerous in environments where yapi is used to document and test production APIs.

Technologies: yapi-vendor (npm), Ymfe Yapi. Vendors: npm, Ymfe.

Quick answers

Is CVE-2025-70058 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2025-70058 being exploited in the wild.
How severe is CVE-2025-70058?: Low severity, with a CVSS score of 3.1, published 23 February 2026.
Which products and versions are affected?: yapi-vendor (npm) SEMVER:introduced=0,last_affected=1.12.0; Ymfe Yapi 1.12.0 and earlier.
Is there a fix for CVE-2025-70058?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2025-70058 attacked?: It is attacked over the network.
Am I affected by CVE-2025-70058?: Check whether you run yapi-vendor (npm) or Ymfe Yapi at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The vulnerability is an improper certificate validation flaw (CWE-295) where yapi explicitly sets 'rejectUnauthorized': false in the Axios HTTPS agent configuration, disabling TLS/SSL certificate validation. This allows network-level attackers to intercept and modify HTTPS traffic by presenting an untrusted certificate without triggering validation errors. The vulnerability affects yapi v1.12.0 and earlier versions; it is present in the postmanLib.js component where Axios is configured for making external API requests. An attacker positioned to perform man-in-the-middle attacks (e.g., on the same network, through DNS hijacking, or via compromised network infrastructure) can exploit this without authentication to intercept API documentation requests, steal authentication tokens, and modify API specifications. A fix requires enabling certificate validation in the Axios configuration.

Affected products

YMFE yapi 1.12.0 and earlier

Identifiers

CVE-2025-70058
GHSA-663h-2vr3-ghrj

Timeline

2026-02-23: disclosed
2026-02-11: other: Vulnerability publicly documented

References

https://gist.github.com/zcxlighthouse/11c53803faf23f607c2787c166e811d4

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.