Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is Heartbleed?

Heartbleed (CVE-2014-0160) is an OpenSSL memory disclosure bug that let anyone read 64KB of a server’s memory per request, exposing session cookies, passwords, and private keys.

Illustration for the cybersecurity term Heartbleed
Home / Blog / Cybersecurity Terms / What Is Heartbleed?
17 November 2026

What Is Heartbleed?

What Is Heartbleed?

Heartbleed is a memory disclosure flaw in the OpenSSL cryptographic library, tracked as CVE-2014-0160, that allowed anyone on the internet to read up to 64 kilobytes of a vulnerable server’s memory per request—repeatedly, and without leaving anything in the logs. It was announced on 7 April 2014 and affected OpenSSL 1.0.1 through 1.0.1f, which at the time protected a large share of all HTTPS traffic.

The name comes from the feature it abused: the TLS heartbeat extension described in RFC 6520, a keep-alive mechanism that had been in OpenSSL since December 2011.

One Missing Bounds Check

A heartbeat message is simple. The client sends a short payload together with a number stating how long that payload is, and the server echoes the payload back. The vulnerable code trusted the stated length rather than measuring the data it had actually received. Send a one-byte payload while claiming it is 65,535 bytes long, and the server copies 65,535 bytes out of its own heap and returns all of them.

Whatever happened to sit next to that buffer travelled with it: session cookies, usernames and passwords submitted moments earlier, decrypted request bodies, internal memory addresses, and in many cases fragments of the server’s RSA private key. Cloudflare ran a public challenge in April 2014 and confirmed within hours that private keys could indeed be reconstructed from the leaked bytes.

Two properties made Heartbleed unusually severe. The request is valid TLS, so it works before any authentication and reaches the library even on services that require a login. And because heartbeats are not logged by default, a compromised organisation had no reliable way of telling whether it had been attacked.

Who Was Affected

The bug was found independently by Neel Mehta of Google and by a team at the Finnish firm Codenomicon, who commissioned the logo and the name that turned a library bug into front-page news. In the UK, the parenting site Mumsnet reset the passwords of around 1.5 million accounts after confirming that user sessions had been hijacked. The Canada Revenue Agency reported the theft of roughly 900 social insurance numbers and delayed its tax filing deadline. Community Health Systems in the United States traced a breach of 4.5 million patient records to a Heartbleed-vulnerable Juniper appliance.

The exposure reached far beyond web servers. OpenSSL sits inside VPN concentrators, mail servers, load balancers, Android builds, industrial controllers, and printers. Plenty of embedded devices shipped in 2013 are still running the vulnerable code because no one ever issued firmware for them.

Recovering Properly

Patching alone was never enough, and this is the part many organisations got wrong at the time. A complete recovery from a Heartbleed-class key disclosure has four steps:

  1. Upgrade to a fixed version—OpenSSL 1.0.1g or later—or rebuild with -DOPENSSL_NO_HEARTBEATS.
  2. Generate a new private key and request a new certificate. Reusing the old key defeats the point.
  3. Revoke the old certificate so that a stolen key cannot be used against clients that check revocation.
  4. Invalidate every session token and force a password reset, because credentials in memory may already be in someone else’s hands.

Certificate authorities reissued hundreds of thousands of certificates in the weeks that followed, and the resulting revocation lists grew large enough to cause their own performance problems.

What It Changed

Heartbleed reframed how the industry thinks about dependencies. OpenSSL was maintained by a handful of volunteers on a tiny budget while underpinning a significant fraction of global commerce. The Core Infrastructure Initiative, and later the Open Source Security Foundation, grew directly out of that realisation, as did the LibreSSL and BoringSSL forks.

It also made the case for knowing what you run. A current software bill of materials turns a question such as “are we exposed?” from a fortnight of guesswork into a database query. The same lesson resurfaced with Log4Shell seven years later.

Heartbleed remains a useful teaching case because detection and patch management cannot cover a vulnerability that leaves no trace—only inventory, rapid rebuilds, and rotated secrets can. Our Continuous Vulnerability Scanning Services keep that inventory honest between annual tests.

FAQ – Frequently Asked Questions

Is Heartbleed Still a Risk Today?

Not on maintained systems. Every supported OpenSSL branch has been fixed since April 2014. The remaining risk sits in equipment that was never updated: old VPN appliances, embedded controllers, network printers, and industrial devices whose vendors have stopped issuing firmware. Internet-wide scans still find a few thousand vulnerable hosts, almost all of them forgotten hardware rather than live web servers.

Could an Attacker Choose What Data Heartbleed Returned?

No. Each request returned whatever happened to be adjacent in the heap at that moment, so the output was largely random. That did not make it safe. An attacker could repeat the request thousands of times per minute, collect the fragments, and reassemble useful material such as private key components, session cookies, and form submissions from the accumulated dump.

Why Did Sites Have to Reissue Certificates Rather Than Just Patch?

Because the private key may already have been stolen. Patching stops future leaks but does nothing about a key an attacker copied last week, and that key would let them impersonate the site or decrypt recorded traffic. Recovery therefore required a new key pair, a new certificate, revocation of the old one, and the invalidation of every active session.

How Would We Detect a Heartbleed Attack After the Fact?

Usually you cannot, which was the central problem. Heartbeat messages are not written to application logs, and the exploit produces no error. Only organisations with full packet capture, or an IDS running a signature for oversized heartbeat responses, could go back and check. That gap is why the recommended response assumed compromise rather than waiting for evidence of it.

Related Terms

You May Be Interested In These

What Is Vishing?

Cybersecurity Terms

17 November 2026

What Is Vishing?

Read More
What Is Distributed Energy Resource Security?

Cybersecurity Terms

17 November 2026

What Is Distributed Energy Resource Security?

Read More
What Is Hypothesis-Driven Threat Hunting?

Cybersecurity Terms

17 November 2026

What Is Hypothesis-Driven Threat Hunting?

Read More