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

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is an Exploit Chain?

An exploit chain links several vulnerabilities, each insufficient alone, into a single working attack — which is why severity scores on individual issues routinely understate real risk.

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

What Is an Exploit Chain?

What Is an Exploit Chain?

An exploit chain is a sequence of vulnerabilities used together, where each one provides the precondition for the next. The first might be an information disclosure, the second a way to run code in a restricted context, the third an escape from that context, and the fourth a privilege escalation. None of them is sufficient alone. Together they produce full compromise.

This is how serious attacks are actually built. The single catastrophic vulnerability that takes a system from anonymous to administrator in one request still exists, but defenders encounter it far less often than they encounter three medium-severity findings that somebody joined up.

A Worked Example

Consider a typical internal path:

  1. A public GitHub repository belonging to the organisation contains a test configuration file with an old VPN account. Severity: nothing, it is an information disclosure with no CVE.
  2. That account has no multi-factor authentication because it predates the policy. Severity: a policy exception on a risk register.
  3. Inside the network, a file share permits authenticated read access to everyone and contains a script with a service account password. Severity: a medium finding.
  4. That service account has replication rights, granted by a backup product installer in 2016, allowing DCSync. Severity: critical, but only once the preceding three steps exist.

Each item on its own would be triaged low or medium and scheduled accordingly. The chain is a full domain compromise reachable from the internet, achievable in an afternoon.

Public Examples

Why Scoring Systems Miss This

CVSS scores a vulnerability in isolation, which is a reasonable design decision for a universal metric and a poor basis for a remediation queue. A flaw scored 4.3 because it requires local access and yields only information disclosure may be the keystone of a chain that ends in domain admin.

CVSS version 4.0 improved matters with threat and environmental metrics, and the Exploit Prediction Scoring System estimates the likelihood of exploitation in the wild. Both help. Neither models the specific paths through your environment, which is where the risk actually lives.

Defending Against Chains

Demonstrating realistic chains rather than listing isolated issues is the core of our penetration test services.

FAQ – Frequently Asked Questions

Why Do Attackers Use Chains Instead of a Single Exploit?

Because single-step total compromise is rare against maintained systems. Modern platforms use sandboxing, privilege separation, and exploit mitigations specifically so that one flaw is not enough. Attackers therefore combine several smaller weaknesses, each of which defeats one layer. Chains are also more durable, since a patch for one link can sometimes be replaced with an alternative.

Does CVSS Account for Chained Vulnerabilities?

Not directly. CVSS scores each vulnerability in isolation, which keeps the metric comparable across products but means a low score can belong to the keystone of a serious chain. Version 4.0 added threat and environmental metrics that help, and EPSS estimates exploitation likelihood, but neither models the specific paths available in your own environment.

How Do I Find Chains in My Own Environment?

Use attack path analysis tooling for identity systems, review how low-severity findings relate to one another rather than triaging them independently, and commission testing that is scoped to demonstrate paths rather than produce a scanner report. Asking a tester how they would get from the internet to a named critical system is the most direct version of the question.

Should We Fix Low-Severity Findings?

Fix the ones that enable something else. A verbose error message that leaks internal host names is trivial by itself and valuable to an attacker mapping the network. Rather than treating low severity as a reason to defer indefinitely, assess each finding by what it unlocks, and give priority to those sitting on a path to a high-value asset.

Related Terms

You May Be Interested In These

What Is a URL Address? How Does It Work?

Cybersecurity Terms

30 March 2021

What Is a URL Address? How Does It Work?

Read More
What Is Privileged Access Management (PAM)?

Cybersecurity Terms

17 November 2026

What Is Privileged Access Management (PAM)?

Read More
What Is Business Continuity in Healthcare?

Cybersecurity Terms

17 November 2026

What Is Business Continuity in Healthcare?

Read More