Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-13380 – Cleartext SFTP Credential Disclosure – VSee Clinic 7.1.26 and API 1.3.0

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-13380 is a critical credential exposure vulnerability in VSee Clinic 7.1.26 and VSee Clinic API 1.3.0, a HIPAA-compliant telemedicine platform used by healthcare organizations. The flaw causes cleartext SFTP credentials to be returned in HTTP responses from three unauthenticated endpoints, requiring no authentication to exploit and enabling direct unauthorized access to the associated SFTP server. It carries a CVSS 4.0 base score of 9.0 (Critical).

Technical details

  • Root cause: VSee Clinic and its API component include SFTP credential data — including usernames and passwords in cleartext — in the HTTP responses of three endpoints that require no authentication. This behavior stems from the insertion of sensitive information into outbound API responses (CWE-201) and cleartext storage of credentials within application data (CWE-312).
  • Trigger condition: The credential data is present in these responses only when SFTP connections have been configured within the application. SFTP integration is not enabled by default; instances where it has been configured are directly exposed.
  • Attack vector: Network-accessible, unauthenticated. An attacker sends HTTP requests to any of the three affected endpoints and receives SFTP credentials in the response body. No prior access, session, or authentication token is required.
  • Impact: An attacker who obtains the exposed credentials can authenticate directly to the configured SFTP server. This grants full access to files stored on that server, which in healthcare environments may include Protected Health Information (PHI), clinical records, or other regulated data. The CVSS 4.0 vector reflects high confidentiality and integrity impact on subsequent systems (SC:H/SI:H).

Affected software

  • VSee Clinic version 7.1.26 (fixed in 7.1.26.1)
  • VSee Clinic API version 1.3.0 (fixed in 1.3.0.1)

Severity

  • CVSS 4.0 Base Score: 9.0 (Critical)
  • CVSS 4.0 Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:H/SA:N

Mitigation and recommended actions

  • Immediate: Upgrade VSee Clinic to version 7.1.26.1 and VSee Clinic API to version 1.3.0.1, which contain the vendor-released fix.
  • Assess SFTP configuration: Organizations should confirm whether SFTP connections are configured on their VSee Clinic instance. If SFTP is configured and the instance has not yet been patched, rotate any exposed SFTP credentials immediately and audit SFTP server access logs for unauthorized activity.
  • Network mitigation: Where patching is not immediately feasible, restrict public network access to the VSee Clinic API endpoints at the perimeter or via WAF rules to reduce exposure while the upgrade is applied.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge