# Exploit (Security)

> Code or steps that use a security hole to do harm. Fix the hole and it stops working.

**Field:** Software Development  
**Category:** Security  
**Also known as:** Exploit Code, Security Exploit, Proof of Concept Exploit

## Think of it like

Think of it like a key made to fit one broken lock. It only works because the lock is broken.

## Definition

An exploit is code or a set of steps that uses a hole to do harm. The hole is the weak spot, and the exploit is how someone uses it. It might steal data, crash a server or let an attacker run their own code. Some exploits are shared in public to prove a hole is real. Fixing the hole makes the exploit stop working.

## Example

A researcher shows that one odd login request skips the password check. That request is the exploit, and the missing check is the hole.

## Why it matters

A hole with a public exploit is far more urgent. Anyone can now use it, not just experts.

## Common mistake

Thinking a hole is safe because nobody has shown an exploit. Attackers can study the fix and write one.

## Three principles

- **Uses a hole.** No hole, no exploit.
- **Many aims.** It can steal, crash or take control.
- **The patch stops it.** The fix closes the hole it needs.

## Related terms

- [Security Vulnerability](https://learn.benibix.com/term/development/vulnerability)
- [Zero-Day Vulnerability](https://learn.benibix.com/term/development/zero-day)
- [Common Vulnerabilities and Exposures (CVE)](https://learn.benibix.com/term/development/cve)
- [Remote Code Execution (RCE)](https://learn.benibix.com/term/development/remote-code-execution)
- [Penetration Testing](https://learn.benibix.com/term/development/penetration-testing)

## Told apart from

- [Vulnerability vs Exploit](https://learn.benibix.com/compare/vulnerability-vs-exploit): People think a vulnerability and an exploit are the same thing, and they are not. The vulnerability is the weak spot in the code. The exploit is the code or the steps that use that weak spot to do harm. A hole can sit there for years with no exploit. Once an exploit is public, fixing the hole becomes urgent.

![A timeline of five points: a flaw goes into the code, attackers find it and write an exploit, the maker hears of it, a CVE and a patch go out, and people who update are safe. A dashed, lit-up box over the second and third points is marked zero-day, no fix exists yet. Notes say the vulnerability is the flaw and the exploit is the code that uses it.](https://learn.benibix.com/diagrams/dev2-vuln-timeline.svg)

---

Source: https://learn.benibix.com/term/development/exploit
Author: Behnia Zarei (a developer in Vienna, Austria, who builds and teaches data, AI and business intelligence at BENIBIX)
Publisher: BENIBIX Learn (https://learn.benibix.com/)
Last updated: 2026-11-19
Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Quote freely with attribution.
