# Common Vulnerabilities and Exposures (CVE)

> A public list that gives each known flaw its own ID, like CVE-2024-3094.

**Field:** Software Development  
**Category:** Security  
**Also known as:** CVE, CVE ID, CVE Number

## Think of it like

Think of it like a case number. Everyone uses the same number for the same case.

## Definition

CVE is a public list that gives each known flaw its own ID. One example is CVE-2024-3094. The ID has the year and a number. It means everyone, from the maker to the person fixing it, talks about the same flaw by the same name. The list started in 1999 and holds hundreds of thousands of entries. Security tools and patch notes quote CVE IDs to say what they fix.

## Example

Lucy's scanner warns about CVE-2024-3094. She looks up the ID, sees it is the backdoor in the xz tool, and updates the package.

## Why it matters

One shared name lets tools, makers and teams match a warning to its fix. Nobody gets mixed up.

## Common mistake

Assuming a CVE is serious just because it exists. Check its score and whether your setup is affected.

## Three principles

- **One ID per flaw.** CVE, year, number.
- **Shared by everyone.** Makers, tools, teams.
- **Look up the score.** Not every one is urgent.

## Related terms

- [Security Vulnerability](https://learn.benibix.com/term/development/vulnerability)
- [Dependency Scanning](https://learn.benibix.com/term/development/dependency-scanning)
- [Supply Chain Attack](https://learn.benibix.com/term/development/supply-chain-attack)
- [OWASP Top 10](https://learn.benibix.com/term/development/owasp-top-10)

---

Source: https://learn.benibix.com/term/development/cve
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.
