Skip to main content

Medtronic CareLink CVE-2025-12995

| EUVDEUVD-2025-201285 CRITICAL
Improper Restriction of Excessive Authentication Attempts (CWE-307)
2025-12-04 security@medtronic.com
9.8
CVSS 3.1 · NVD
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Identify CareLink Network API endpoint
  2. Delivery
    Enumerate/target valid account
  3. Exploit
    Send high-volume brute-force auth requests
  4. Execution
    Observe response oracle to confirm valid password
  5. Impact
    Reuse credential to access patient account data

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Brute-force prevention, rate limiting
Exploitation Conditions

Exploitation targets an unauthenticated, internet-facing CareLink Network API authentication endpoint that lacks adequate anti-brute-force controls (rate limiting / account lockout), the core of CWE-307. The advisory explicitly limits success to 'certain circumstances,' meaning the password-determination outcome is conditional rather than guaranteed - this is the key limiting factor and is why the practical difficulty is higher than AC:L suggests. Affected instances are those running CareLink Network code from before the December 4, 2025 fix; deployments patched on or after that date are not affected. No user interaction or prior authentication is required, but the attacker must be able to reach the endpoint and sustain enough requests to exercise the brute-force path.

Impact

The vendor-assigned CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/C:H/I:H/A:H = 9.8 Critical) is inconsistent with the described weakness and appears substantially overstated. The actual flaw is CWE-307 (improper restriction of excessive authentication attempts): an unauthenticated remote attacker can brute-force an API endpoint to determine a valid password 'under certain circumstances.' That phrase signals a conditional, non-guaranteed outcome, which is difficult to reconcile with AC:L, and a credential-discovery weakness does not by itself deliver full C:H/I:H/A:H - those impacts assume the discovered password then grants complete account compromise, which is a downstream consequence rather than the vulnerability itself. Corroborating signals point to lower real-world urgency: EPSS is only 0.13% (32nd percentile), there is no CISA KEV listing, and no public exploit code is identified. The source of the record is the vendor PSIRT (security@medtronic.com) rather than independent exploitation reporting, and the 'Information Disclosure' tag aligns with credential-oracle behavior more than with a full-compromise RCE. Net: this reads as a genuine authentication-hardening defect on an internet-facing medical monitoring service (worth remediating, especially given healthcare/PHI context), but not the drop-everything 9.8 the headline score implies. Conflict to verify with vendor: CVSS claims C:H/I:H/A:H, yet the description supports only credential determination under conditional circumstances.

Exploit ScenarioDerived

A remote unauthenticated attacker scripts repeated requests against the CareLink Network authentication API, exploiting the absence of effective rate-limiting or lockout to test candidate passwords for a targeted account. Under the specific conditions the advisory references, the endpoint's responses let the attacker infer a valid password, which could then be reused to access the account. No public proof-of-concept is available at time of analysis.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
No patch listed yet 0.1% exploitation probability (EPSS)

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

Alert me

AnalysisAIv2 – Sep 26, 2026

Unauthenticated brute-force attacks against the Medtronic CareLink Network API authentication endpoint can allow remote attackers to determine a valid account password under certain circumstances, because the endpoint lacks adequate anti-automation controls such as rate limiting or account lockout (CWE-307). The vendor assigned CVSS 3.1 AV:N/AC:L/PR:N/UI:N/C:H/I:H/A:H (9.8 Critical), while independent analysis assesses the practical risk as materially lower - AV:N/AC:H/PR:N/UI:N/C:H/I:N/A:N (approximately 5.9, Medium) - because the advisory itself limits success to 'certain circumstances' and no integrity or availability impact has been demonstrated. Risk signals are currently muted: EPSS is 0.13% (32nd percentile), there is no public exploit identified at time of analysis, and the issue is not listed in CISA KEV; all CareLink Network instances running code from before December 4, 2025 are affected, with no user interaction or prior authentication required (PR:N in both vectors).

Earlier versions of this analysis (1)
v1 Mar 15, 2026 - 16:35 CVSS 8.1

RemediationAI

Vendor-released remediation is available: Medtronic fixed the issue in CareLink Network code dated December 4, 2025, so the primary action is to ensure every CareLink Network deployment - hosted or customer-operated - runs code from that date or later, confirming the exact applied build with Medtronic since no explicit patched version string is published (reference: https://www.medtronic.com/en-us/e/product-security/security-bulletins/carelink-network-vulnerabilities.html and https://nvd.nist.gov/vuln/detail/CVE-2025-12995). Where the update cannot be applied immediately, compensating controls must target the missing anti-automation logic at the API authentication endpoint: enforce server-side rate limiting, exponential backoff, and account lockout at the API gateway, WAF, or reverse proxy in front of the authentication service - accepting the trade-off that aggressive thresholds can lock out legitimate clinicians and require tuning plus a safe unlock path for patients; require multi-factor authentication on CareLink Network accounts to reduce the value of any recovered password, with the trade-off of added login friction for clinical staff; and restrict network access to the API authentication endpoint to trusted address ranges or a VPN/zero-trust broker, understanding that this can disrupt patient-side and clinician access paths. In parallel, enable alerting on spikes in failed authentication attempts and credential-stuffing patterns per source IP or account so that active brute-force attempts against unpatched instances are detected and blocked quickly.

Affected VersionsENISA

CareLink Network 0 <December 4, 2025

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

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

Technical ContextAI · show details

The weakness class is CWE-307, Improper Restriction of Excessive Authentication Attempts, mapped to the CareLink Network API authentication endpoint exposed to the internet. CareLink Network is Medtronic's remote-monitoring platform that collects and relays cardiac device (pacemaker, ICD) data between patients and clinicians; the vulnerable surface is the network's authentication API rather than the implanted devices themselves. Because the endpoint permits repeated authentication attempts without effective throttling, lockout, or progressive delays, an attacker who can reach it can enumerate candidate credentials at high volume, with the password-determination outcome qualified by the vendor as achievable only under 'certain circumstances' - a conditional success rate that is the primary reason the assessed vector uses AC:H rather than AC:L. Both the vendor and independent vectors specify PR:N and UI:N, confirming that no credentials or user interaction are needed to reach the brute-force path; the attacker's requirement is network reachability and the ability to sustain enough requests to exercise it. The affected CPE cpe:2.3:a:medtronic:carelink_network:*:*:*:*:*:*:*:* uses a wildcard version, so exposure must be determined by deployment code date rather than by a version string, and the only reliable discriminator is whether the instance runs code from before December 4, 2025.

Know when Carelink Network 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

No credit card · 7-day full trial

Severity by source

NVD PRIMARY 9.8 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 5.9 MEDIUM

Remote unauthenticated (AV:N/PR:N/UI:N); AC:H because success is conditional ('certain circumstances') and requires brute-force effort; impact is credential/account confidentiality (C:H), with no direct integrity or availability effect.

3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
4.0 AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from NVD.

CVSS VectorNVD

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

4
Severity Changed
Sep 25, 2026 - 23:22 NVD
HIGH CRITICAL
CVSS changed
Sep 25, 2026 - 23:22 NVD
8.1 (HIGH) 9.8 (CRITICAL)
CVE Published
Dec 04, 2025 - 20:16 nvd
HIGH 8.1
CVE Published
Dec 04, 2025 - 20:16 nvd
CRITICAL 9.8

DescriptionNVD

Medtronic CareLink Network allows an unauthenticated remote attacker to perform a brute force attack on an API endpoint that could be used to determine a valid password under certain circumstances. This issue affects CareLink Network: before December 4, 2025.

Executive ViewAI

Why It Matters

Medtronic CareLink Network contains an authentication vulnerability allowing unauthenticated attackers to brute force user passwords through an API endpoint, potentially compromising patient data and medical device access. Organizations using CareLink Network face immediate risk of unauthorized account access and must implement interim protections while awaiting the December 4, 2025 patch.

Business Impact: High
Compensating Controls

Implement API rate limiting and request throttling to inhibit brute force attempts; restrict API endpoint access via network segmentation or WAF to authorized IP ranges only; enable multi-factor authentication if supported by CareLink; increase monitoring and alerting on failed authentication attempts; consider temporarily disabling remote API access if operationally feasible; implement account lockout policies after failed login attempts.

Threat Intelligence Overview

EPSS Score
0.1%
Top 68% exploitable
Prevalence
Medium
Single vendor-operated cardiac remote-monitoring service with a large but specialized patient base
Data Quality
4 sources
Confidence: Medium

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 CRITICAL
CISA KEV No
Public POC No
EPSS 0.1%
Patch available No
Active threat No
Deciding rule
CRITICAL severity
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.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
Yes
Human Impact
High

Priority Score

49
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +49
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy