What Is a Vulnerability in Cybersecurity?

A clear guide to security vulnerabilities — what they are, the common types, how they are discovered and tracked with CVE and CVSS, and how they are managed.

Share
Editorial science-poster illustration of security-weakness symbols — an ajar door, a cracked wall, an open window, a magnifying glass, and a cracked padlock.

Every system an organization runs — every application, server, and device — contains weaknesses. Some are harmless quirks. Others are security flaws an attacker can exploit to break in, steal data, or take control. Those exploitable weaknesses are called vulnerabilities, and they are one of the most fundamental concepts in all of cybersecurity.

Vulnerabilities are the openings that attacks rely on. A phishing email still needs somewhere to lead; a piece of malware still needs a way in. Very often, that way in is a vulnerability — a flaw that should have been closed and was not.

This guide explains what a vulnerability is, how it differs from a threat and a risk, the common types, how vulnerabilities are discovered and tracked, and how organizations manage them. It is the foundation for our complete guide to vulnerability management.

What Is a Vulnerability?

A vulnerability is a weakness or flaw in a system, application, or process that an attacker can exploit to compromise security. It might be a coding error in a software product, a missing security update, a misconfigured server, a default password left unchanged, or an overly permissive access setting.

The defining point is that a vulnerability is a weakness that could be exploited — it is not an attack in itself. Think of it as an unlocked door or an open window: it does not guarantee a break-in, but it makes one possible. Cybersecurity is, in large part, the ongoing work of finding and closing those openings before someone uses them.

Vulnerability vs Threat vs Risk

These three words are often used loosely, but they describe different things, and understanding the difference is essential.

  • Vulnerability — a weakness that could be exploited, such as an unpatched application.
  • Threat — a potential danger that could exploit a vulnerability, such as an attacker or a piece of malware.
  • Risk — the likelihood that a threat exploits a vulnerability, combined with the impact if it does.

A vulnerability with no realistic threat against it carries little risk. A vulnerability that attackers are actively exploiting carries a great deal. This relationship is why organizations do not simply fix flaws at random — they prioritize by risk, concentrating on the weaknesses most likely to be used and most damaging if they are.

Editorial illustration of the relationship between a vulnerability, a threat, and risk — an open window, an approaching threat, and valuables inside.
The relationship between Vulnerability (the open window), Threat (the figure), and Risk (the valuables).

Common Types of Vulnerabilities

Vulnerabilities come from many sources. The most common categories include:

  • Software flaws — coding errors such as improper input handling that attackers can exploit. SQL injection and similar web flaws fall here.
  • Missing patches — known vulnerabilities left unfixed because an available update has not been applied.
  • Misconfigurations — insecure settings, such as exposed databases, open ports, or overly broad permissions.
  • Weak or default credentials — accounts protected by guessable, reused, or factory-default passwords.
  • Outdated and end-of-life software — products that no longer receive security updates from their vendor.

Unpatched software deserves special mention, because it is both extremely common and entirely preventable — the fix already exists. Our guide to why unpatched software is one of the biggest security risks explains why this category causes so many breaches.

How Vulnerabilities Are Discovered

Vulnerabilities are found by many different people, for very different reasons. Security researchers and ethical hackers hunt for them deliberately, often through bug bounty programs that reward responsible reporting. Vendors find flaws in their own products through internal testing. Attackers, of course, search for them too — and a vulnerability an attacker finds first is the most dangerous kind.

How a newly found vulnerability is handled matters enormously. Responsible, coordinated disclosure means the finder privately alerts the vendor and gives them time to release a fix before details are made public. That window is what allows defenders to patch before the flaw is widely exploited.

How Vulnerabilities Are Tracked: CVE and CVSS

With thousands of vulnerabilities disclosed every year, the security community needs a shared way to refer to them. Two systems make that possible.

The CVE system — Common Vulnerabilities and Exposures — assigns every publicly known vulnerability a unique identifier, so everyone is discussing the same flaw. Our explainer on what a CVE is covers this in detail. The CVSS system — the Common Vulnerability Scoring System — then rates each vulnerability's severity from 0.0 to 10.0, helping defenders judge how urgent a fix is.

[ BODY IMAGE 2 — see CyberSignal_Image_Prompts.md ]

The Life of a Vulnerability

A vulnerability has a lifecycle. It is introduced — usually when software is written or a system is configured. At some point it is discovered. It is ideally disclosed to the vendor, who develops and releases a patch. Finally, defenders apply that patch, closing the flaw.

The dangerous gaps are the spans in between. A zero-day vulnerability is one being exploited before a patch exists at all. And even after a patch is released, every day it goes uninstalled is a day attackers can still use the flaw. Sophisticated attackers may even combine several vulnerabilities — see our guide to how exploit chains work — which is why closing these gaps quickly matters so much.

How Organizations Manage Vulnerabilities

Because new vulnerabilities appear constantly, organizations cannot treat them as one-off problems. They run a continuous process — vulnerability management — that involves keeping an inventory of all systems, scanning them regularly for known weaknesses, prioritizing findings by risk, remediating the most important ones, and verifying the fixes held.

No organization ever reaches zero vulnerabilities, and that is not the goal. The goal is to find and close the most dangerous weaknesses faster than attackers can exploit them. Our complete guide to vulnerability management walks through how that program works in practice.

Conclusion

A vulnerability is simply a weakness an attacker could use — but that simple idea sits at the center of cybersecurity. Attacks succeed by finding and exploiting these openings, so defense, at its core, is the disciplined work of finding and closing them first.

Understanding what vulnerabilities are, where they come from, and how they are tracked and managed is the starting point for everything else in security. An organization that knows its weaknesses — and closes the ones that matter most, quickly — has already removed the easiest paths an attacker would otherwise take.


Frequently Asked Questions (FAQ)

What is a vulnerability in cybersecurity?

A vulnerability is a weakness or flaw in a system, application, or process that an attacker can exploit to compromise security — for example, a software bug, a missing patch, a misconfiguration, or a weak password.

What is the difference between a vulnerability, a threat, and a risk?

A vulnerability is a weakness that could be exploited. A threat is a potential danger that could exploit it. Risk is the likelihood of a threat exploiting a vulnerability combined with the impact if it does.

What are the most common types of vulnerabilities?

Common types include software coding flaws, missing security patches, misconfigurations, weak or default credentials, and outdated end-of-life software that no longer receives updates.

What is the difference between a vulnerability and an exploit?

A vulnerability is the weakness itself. An exploit is the technique or code an attacker uses to take advantage of that weakness. The vulnerability is the open door; the exploit is going through it.

What are CVE and CVSS?

CVE (Common Vulnerabilities and Exposures) gives every publicly known vulnerability a unique identifier. CVSS (Common Vulnerability Scoring System) rates each one's severity from 0.0 to 10.0 so defenders can prioritize fixes.

Can all vulnerabilities be eliminated?

No. New vulnerabilities are discovered constantly, and no system is ever completely free of them. The goal of vulnerability management is not zero vulnerabilities but finding and fixing the most dangerous ones faster than attackers can exploit them.