Security readout for executives and security teams
This issue affects Medtronic MyCareLink 24950 and 24952 patient monitors. If an attacker obtains product-specific credentials from a monitor plus paired cardiac device information, they may upload invalid data to the Medtronic CareLink network. The business risk is data integrity, not direct device control based on the supplied sources. Exposure is most likely in healthcare environments using Medtronic 24950 or 24952 MyCareLink monitors connected to CareLink workflows. The source bundle lists all versions, but exploitation also requires obtained per-product credentials and paired implantable cardiac device information. Treat as a moderate medical-device data-integrity risk. Prioritize inventory, vendor guidance review, and operational controls for affected monitors. Escalate if these monitors support high-volume or safety-sensitive remote cardiac monitoring workflows. Mitigation focus: Identify any Medtronic 24950 or 24952 MyCareLink monitors in use.; Review Medtronic’s bulletin and CISA ICSMA-18-219-01 for official guidance.; Protect monitors and related credentials from unauthorized physical or local access..
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-345: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2018-10626 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 4.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:A/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:A/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:N1.32.7icscertVulnerability scoring details
Base CVSS 3.1 score
4.4MediumVector: CVSS:3.1/AV:A/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- 105042CVE reference, icscert
- https://www.cisa.gov/news-events/ics-medical-advisories/icsma-18-219-01CVE reference, icscert
- https://github.com/cisagov/CSAF/blob/develop/csaf_files/OT/white/2018/icsma-18-219-01.jsonCVE reference, icscert
- https://ics-cert.us-cert.gov/advisories/ICSMA-18-219-01CVE reference, CVE · x_refsource_MISC, x_transferred
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Insufficient Verification of Data Authenticity
Insufficient Verification of Data Authenticity represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.