Home » Why OpenSSL Secures Most Web Traffic and Poses Global Infrastructure Risks

Why OpenSSL Secures Most Web Traffic and Poses Global Infrastructure Risks

By

–

Why OpenSSL Secures Most Web Traffic and Poses Global Infrastructure Risks

The Plumbing of the Web

An urgent security fix has been issued for code that underpins an estimated 70% of all websites, a development that highlights the critical role of foundational software in global internet infrastructure. The code in question is OpenSSL, a software library that provides secure communications over computer networks by preventing eavesdropping and identifying the party at the other end of the connection. It is widely used by internet servers, including the majority of HTTPS websites, making it a central pillar of how data moves securely across the globe.

To understand why a fix for this specific codebase is considered a critical risk to internet infrastructure, it helps to look at what OpenSSL actually does and how it got there. In plain terms, OpenSSL is the digital handshake that happens before you see a website. It ensures that the data you send to a bank, a retailer, or a news site is encrypted and that you are talking to the real server, not an imposter. Because it handles this foundational layer of security, any flaw in its core code has the potential to ripple across the entire internet.

A History of Open-Source Encryption

The OpenSSL project was founded in 1998 with the goal of providing a free set of encryption tools for the code used on the Internet. It is based on a fork of SSLeay, a project by Eric Andrew Young and Tim Hudson, which unofficially ended development on December 17, 1998, when both developers went to work for RSA Security. The initial founding members included Mark Cox, Ralf Engelschall, Stephen Henson, Ben Laurie, and Paul Sutton. Since those early days, the project has grown into a massive undertaking supported by the OpenSSL Software Foundation (OSF), which represents the project in most legal capacities, including managing contributor license agreements and donations.

Optical fiber cable-07ASD.jpg
Photo: Asurnipal (CC BY-SA 4.0)

The library is available for most Unix-like operating systems, such as Linux, macOS, and BSD, as well as Microsoft Windows and OpenVMS. In 2018, the project made a notable change to its version numbering, skipping from 1.1.1 to 3.0.0 to avoid a conflict with one of its modules. This version 3.0.0 was also significant for being the first to use the Apache License. By 2024, the project had fourteen employees and reported a total income of US$5.5 million, with development of the TLS 1.3 protocol sponsored by Akamai. This structure, a mix of volunteer effort and corporate sponsorship, is typical of critical open-source infrastructure, but it also means that the code is maintained by a community that must constantly balance security, performance, and compatibility.

How the Code Protects Your Data

OpenSSL contains an open-source implementation of the SSL and TLS protocols, which are the standards for securing web traffic. The core library is written in the C programming language, a choice that allows for high performance but also requires meticulous attention to memory management. It implements basic cryptographic functions and provides various utility functions, with wrappers available that allow the library to be used in a variety of other computer languages. Think of it like a universal translator for secure data: it takes the complex mathematical operations required for encryption and makes them accessible to applications written in Python, Java, or C++.

The library supports a wide array of cryptographic algorithms, including ciphers like AES, ChaCha20, and SM4, as well as hash functions such as SHA-2 and SHA-3. It also handles public-key cryptography, supporting RSA, Diffie-Hellman key exchange, and elliptic curve methods. Perfect forward secrecy, a feature that ensures past communications remain secure even if a key is compromised, has been supported using elliptic-curve Diffie-Hellman since version 1.0. This breadth of support is why OpenSSL is so prevalent; it can handle almost any security requirement a server might face, from a small personal blog to a global financial institution.

The Scale of Adoption and Systemic Risk

The reason a vulnerability in OpenSSL is treated with such urgency is its sheer ubiquity. Because it is used by the majority of HTTPS websites, a single bug in the core library can potentially affect billions of connections. This creates what is known as a systemic risk: if the foundation cracks, everything built on top of it is threatened. The library is not just a component of the web; it is the web’s security layer. When researchers find a flaw, the pressure is on to fix it quickly, not just for the users, but to prevent the kind of large-scale compromise that could undermine trust in online transactions and communications.

The maintenance of such a critical tool is a constant challenge. As of May 2019, the OpenSSL management committee consisted of seven people, with seventeen developers holding commit access. At that time, there were only two full-time employees, with the remainder being volunteers. By 2024, the number of employees had grown to fourteen, reflecting the increasing complexity and importance of the project. This transition from a purely volunteer effort to one with more dedicated staff is a sign of the project’s maturity, but it also highlights the resource constraints that can slow down the identification and patching of vulnerabilities. The more people who depend on the code, the higher the stakes for every update.

New Tools for Finding Bugs in Shipped Code

One of the ongoing challenges in maintaining OpenSSL is finding bugs in code that has already been deployed. Traditional testing often focuses on new code, but vulnerabilities can lurk in older, stable versions for years. This is where new technologies are starting to make a difference. In November 2026, AI company Cohere announced the acquisition of two startups: cubic, a London-based code-review startup, and AISLE, a Prague-based vulnerability-discovery startup that now operates as Cohere Cyber. AISLE specializes in hunting for vulnerabilities in code that has already shipped, including flaws in OpenSSL and curl.

Code on computer monitor (Unsplash).jpg
Photo: Markus Spiske markusspiske (CC0)

The impact of these tools is already visible. Tomáš Mráz, the chief technology officer of the OpenSSL Foundation, stated that the January 2026 release fixed 12 security issues, all of which were disclosed to the project by AISLE. This is a significant development because it shows that automated and AI-assisted tools can find flaws that human reviewers might miss. The practical upshot is that the library is becoming more secure, not just because of human effort, but because of new methods for scrutinizing existing code. For ordinary users, this means that the security of their web connections is being reinforced by a new layer of automated vigilance.

Improving Certificate Verification

Another area where OpenSSL is evolving is in how it handles certificate revocation. A certificate authority revokes a certificate when it should stop being trusted before it expires, but OpenSSL has historically checked the certificate chain by default without checking if any certificate in that chain was revoked. This left tools like curl, which rely on OpenSSL, trusting certificates that browsers had already blocked. In 2026, Ubuntu 26.10 shipped with curl including certificate revocation checking built in, using a project called upki from the rustls developers.

This check compares the server’s certificate against a list of revoked certificates stored locally on the machine, using a method called CRLite that compresses revocation data. Because the data is local, the check adds no network requests, meaning your connection doesn’t wait on a lookup, and no outside server sees which sites you visit. For Ubuntu 27.04, the Foundations team plans to build this capability into Ubuntu’s OpenSSL directly, so that normal certificate verification would also check the revocation data. This change would benefit the more than 1,000 packages that use OpenSSL directly, giving them browser-grade certificate verification without requiring code changes. This is a concrete example of how the ecosystem around OpenSSL is tightening its security, addressing gaps that have existed for years.

Performance and the Future of Secure Computing

As the internet grows, so does the demand for faster encryption. Recent benchmarks show that OpenSSL 4.1 performs well on modern hardware, particularly with the AMD Zen 6 processors. When tested on the EPYC 9996 flagship, simultaneous multithreading (SMT) on Zen 6 provided around 32% better performance for the QuantLib quantitative finance software, and around 20% more performance on the EPYC 9686F. For OpenSSL 4.1 specifically, SMT was found to be very beneficial for maximizing throughput and performance-per-watt, even on the 256-core per socket configurations.

This performance data is important because it shows that the tools securing our data are keeping pace with hardware advancements. As more data is processed and more connections are made, the efficiency of encryption libraries like OpenSSL becomes a key factor in the overall speed and reliability of the internet. The fact that modern CPUs can handle these cryptographic tasks more efficiently means that the security layer is becoming less of a bottleneck and more of a seamless part of the digital experience.

The story of OpenSSL is one of how a small group of developers in the late 1990s created a tool that now underpins the global economy. It is a reminder that the most critical parts of our digital infrastructure are often invisible, maintained by a mix of volunteers, corporations, and new AI-driven tools. The recent security fixes and improvements in certificate verification show that the project is actively evolving to meet new threats. For the ordinary user, the key takeaway is that the web remains secure because of continuous, behind-the-scenes work to keep this foundational code robust and up to date.

Sources

Photo: Winston Chen / Unsplash (Unsplash License)

Get breaking stories first on our Telegram channel.

More stories by

Most read

Crypto

Internet & Data Centers

Cybersecurity

Business