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

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is the Difference Between Threat, Vulnerability and Risk?

A threat is who or what could harm you, a vulnerability is the weakness they would use, and risk is what it would cost you if they did. Mixing them up wrecks prioritisation.

Illustration for the cybersecurity term Threat, Vulnerability and Risk
Home / Blog / Cybersecurity Terms / What Is the Difference Between Threat, Vulnerability and Risk?
17 November 2026

What Is the Difference Between Threat, Vulnerability and Risk?

What Is the Difference Between Threat, Vulnerability and Risk?

These three words are used interchangeably in meetings and mean quite different things in a risk register. A threat is something that could cause harm. A vulnerability is a weakness that would let it. Risk is the combination: how likely that pairing is, and what it would cost you. Get the distinction right and prioritisation becomes straightforward; get it wrong and you end up patching everything with equal urgency, which means patching the wrong things first.

Three Words, Three Jobs

DefinitionExampleWho controls it
ThreatA potential cause of an unwanted incident—an actor, or a natural or accidental eventA ransomware affiliate; a careless supplier; a burst water main above the comms roomNot you. You can only observe and anticipate it
VulnerabilityA weakness in an asset or control that a threat can exploitAn unpatched file transfer appliance; a shared admin password; no out-of-hours monitoringYou. This is where remediation happens
RiskThe effect of uncertainty on objectives, expressed as likelihood multiplied by impact£2m of recovery cost and 30,000 records exposed, judged likely within a yearYou, by changing the vulnerability, the exposure, or the consequence

Two more terms complete the picture. An asset is the thing with value—data, a service, a reputation. Impact is what the loss of that asset costs, usually scored against the CIA triad. ISO/IEC 27005 and NIST SP 800-30 both define risk in these terms, and ISO 31000 adds the general formulation used across non-security disciplines.

A Worked Example

In late May 2023, the Cl0p ransomware group began exploiting CVE-2023-34362, an SQL injection flaw in Progress MOVEit Transfer, to drop a web shell and steal data. More than 2,700 organisations were affected, including UK bodies whose payroll provider used the software.

Notice which of those an organisation could change. They could not deter Cl0p. They could have reduced the vulnerability by patching within hours of the advisory, and reduced the exposure by placing the appliance behind an access gateway. The risk was the number that should have driven how quickly they did either.

Why the Distinction Changes Your Queue

A vulnerability scan returns thousands of findings. Severity scores alone cannot order them, because a critical flaw on an isolated test box matters less than a high-severity flaw on an internet-facing system holding customer data. Risk-based vulnerability management combines three inputs: the technical severity from CVSS, evidence of real-world exploitation from sources such as CISA’s Known Exploited Vulnerabilities list and the EPSS probability score, and the business value and exposure of the affected asset. That third input is the one only you can supply.

The same logic applies upwards. Threat intelligence that is not tied to your vulnerabilities is reading material; a vulnerability list without threat context is an infinite backlog. The useful question is always the intersection: which of our weaknesses are actually being exploited, on systems that matter.

Common Confusions

Once the three are separated, the control strategy follows: reduce vulnerability through patching and hardening, reduce exposure through segmentation and access control, and reduce impact through backups, encryption, and rehearsed incident response. What is left is residual risk for an owner to accept. Our cyber risk analysis services build that chain from your own assets rather than from a generic threat list.

FAQ – Frequently Asked Questions

Can You Have a Vulnerability With No Risk?

Effectively yes. A weakness on a system with no value, no connectivity, and no realistic threat carries negligible risk, which is why risk-based prioritisation exists. Be careful with the judgement, though: isolated systems turn out to be reachable more often than their owners expect, and an asset’s value can change when a new business process starts using it.

How Is Risk Actually Calculated?

Most organisations use a qualitative matrix, scoring likelihood and impact on a five-point scale and reading the result off a grid. Quantitative approaches such as FAIR express risk as a distribution of financial loss, which suits board conversations and insurance decisions but needs better data. Either works if the scoring criteria are written down and applied consistently.

What Is the Difference Between a Threat and a Threat Actor?

A threat is any potential cause of harm, including accidents, hardware failure, and natural events. A threat actor is a person or group that deliberately causes harm, such as a ransomware affiliate, a state-sponsored group, or a disgruntled employee. Every threat actor is a threat; not every threat has an actor behind it.

Where Does Exposure Fit In?

Exposure describes how reachable a vulnerability is to a given threat: internet-facing, reachable from a user workstation, or only from a segregated management network. It sits between vulnerability and risk and is often the fastest thing to change. Removing an appliance from the public internet can cut risk sharply while you wait for a vendor patch.

Related Terms

You May Be Interested In These

What Is HSTS?

Cybersecurity Terms

17 November 2026

What Is HSTS?

Read More
What Is an Indicator of Compromise (IoC)?

Cybersecurity Terms

17 November 2026

What Is an Indicator of Compromise (IoC)?

Read More