up:: What’s At Risk
Is my pacemaker safe?
The honest answer has two halves, and the first one should be the reassuring part.
Nobody is going to attack your pacemaker. There’s no evidence of anybody doing this, the attack would require being physically near you or on the right network, and there are vastly easier ways to hurt someone. The realistic concern is systemic rather than personal.
And implanted devices are genuinely the hardest problem in this entire subject. A device sealed inside a body for a decade carries encryption fixed at manufacture, where updating it can mean a medical procedure. That’s a real gap and it deserves attention, from regulators far more than from patients.
The short version:
- The personal risk to you is very low. No evidence of this being done, and far easier ways exist to harm someone.
- The systemic problem is real: devices outlive the deadlines and often can’t be updated.
- The threat here is forgery, meaning a forged instruction or a forged software update, rather than someone reading your heart data.
- The FDA’s 2023 guidance covers new devices coming to market, and does nothing for devices already implanted.
- Don’t stop using your device, and don’t let this page worry you into a decision. The risk of an untreated heart condition is not close.
What’s actually at risk in a device like this?
Three things, and understanding which one matters helps keep the fear proportionate.
Software updates. Before a device installs new firmware, it checks a signature confirming the code genuinely came from the manufacturer. That check runs on the mathematics a quantum computer breaks. Forging it would mean pushing altered software to a device, which is the serious version of this problem.
Data in motion. Readings and telemetry traveling from device to monitor to clinic are protected by everyday encryption. Someone could collect that today and read it later, which is a privacy concern rather than a safety one.
Device identity. How a device proves it’s genuinely itself when it connects to a hospital network, a programmer, or a manufacturer’s cloud. Same mathematics again.
The first one is where the actual weight sits, because it’s the path from a cryptographic weakness to something that affects how a device behaves.
Why can’t they just update it?
Because a device inside a body isn’t a phone.
The lifetime is the core problem. Implanted devices are designed to stay in place for a decade or more, which means devices being implanted now will still be running past the dates by which today’s encryption is meant to be retired.
Updating is a clinical event. Some devices can receive updates through a clinic visit, and many can’t be meaningfully changed at all. Replacing one is surgery, with real risk that has nothing to do with cryptography.
Safety certification cuts both ways. These devices are rigorously certified, and that rigor makes changing them slow and expensive. The same process that keeps them safe makes them hard to update.
The new encryption is bigger. Post-quantum algorithms need more memory, more processing, and more power than what they replace. A device engineered around a battery meant to last years has very little margin for that.
Full technical treatment at PQC in Medical Devices.
What are regulators doing?
The FDA’s premarket cybersecurity guidance, finalized in September 2023, sets expectations for devices coming to market, including how manufacturers handle software updates and vulnerabilities over a device’s life.
Source: FDA, “Cybersecurity in Medical Devices: Quality System Considerations and Content of Premarket Submissions,” final guidance, 27 September 2023, fda.gov.
The limit is obvious and it’s the whole issue. Guidance for new devices does nothing about the ones already in people, and those will be in service for years. The population of implanted devices only gets safer at the pace people receive replacements for everyday clinical reasons.
What should a patient actually do?
Very little, and the first item matters most.
- Don’t change anything about your care because of this. The risk from an untreated cardiac condition is enormous and immediate. The risk described here is speculative and remote. Those are not comparable.
- Go to your follow-up appointments. Device checks are when updates get applied, where updates are possible at all.
- Ask your cardiologist or device clinic whether your device receives security updates, and what the manufacturer’s plan is. It’s a fair question and increasingly one they’ve heard.
- Keep the home monitor updated if you have one, since that’s often the more updatable half of the system.
- Leave the systemic problem to regulators, because this is genuinely one where individual action isn’t the lever. See What critical infrastructure is exposed?
What else falls in this category?
The same shape applies to anything with a long life and no easy update path.
| Category | Why it’s the same problem |
|---|---|
| Insulin pumps and monitors | Long service life, safety certified, limited update path |
| Cars | 15-year-plus service lives, cryptography often fixed at manufacture |
| Industrial and grid equipment | Field lifetimes measured in decades |
| Satellites | Physically unreachable after launch |
| Smart meters and building systems | Installed once, rarely touched again |
Questions people ask
Should I be scared? No. If this page has made you anxious about a device keeping you alive, that’s a misreading of it. The systemic gap is real and your personal risk is very low.
Has anybody ever attacked a pacemaker? Security researchers have demonstrated vulnerabilities in medical devices over the years, and there’s no evidence of the quantum version of this being done to anybody, because the machine required doesn’t exist.
Would I know if my device was affected? Your clinic monitors device function, and that’s the channel that would surface a problem.
Should I ask for a newer device? Talk to your cardiologist, and understand that replacement is surgery with its own risks. Nobody should have a device replaced over this.
Why does this get so much attention then? Because it illustrates the hardest version of the problem clearly. It’s a good teaching example and a poor reason for personal alarm.
Where to go next
- Are my medical records safe? covers your health information.
- What critical infrastructure is exposed? covers the same problem at national scale.
- What should my doctor and my bank be doing? covers the institutional standard.
Go deeper into the technical detail
The technical version is PQC in Medical Devices.
These open the Post-Quantum Field Guide, a separate site written for security professionals.
Last verified 2026-07-30 · Maintained by Addie LaMarr, LaMarr Labs.