> ## Documentation Index
> Fetch the complete documentation index at: https://docs.zdlake.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Weaknesses

> Understand CWE flaw classes, prevention guidance, and related security issues.

Weaknesses represent normalized Common Weakness Enumeration (CWE) records. A weakness describes a class of software or design flaw that can produce many different vulnerabilities.

Use weaknesses to move from individual CVEs toward root-cause analysis, secure development guidance, taxonomy reporting, and recurring risk patterns.

## When to use weaknesses

* Group vulnerabilities by their underlying flaw instead of affected product.
* Explain recurring engineering risks using a shared taxonomy.
* Connect prevention and detection guidance to concrete vulnerabilities.
* Organize AppSec reporting, education, and control coverage around CWE classes.

A CWE relationship is explanatory, not a complete exploit narrative. Use related vulnerabilities for concrete affected software and related attack patterns for adversary behavior.

## Relationships

| Related concept | What the relationship explains |
| - | - |
| [Vulnerability](https://docs.zdlake.com/concepts/vulnerabilities.md) | Concrete security issues associated with the flaw class. |
| [Attack pattern](https://docs.zdlake.com/concepts/attack-patterns.md) | Ways an attacker may exercise the weakness. |
| [Advisory](https://docs.zdlake.com/concepts/advisories.md) | Publisher notices that identify the weakness. |
| [Software](https://docs.zdlake.com/concepts/software.md) | Affected products connected through supported vulnerability or advisory claims. |

Deprecated or remapped CWEs can remain useful historical identifiers. Check `state`, relationships, and provenance before using them as durable reporting groups. See [Security data model](https://docs.zdlake.com/concepts/security-data-model.md) for relationship cardinalities.

## Schema

Every weakness detail response starts with these fields:

| Field | Meaning |
| - | - |
| `entity` | Always `weakness`. |
| `entity_id` | Durable Zero identifier for the entity. |
| `id` | Preferred CWE identifier, such as `CWE-79`. |
| `aliases` | Alternate identifiers associated with the taxonomy record. |
| `title` | CWE name. |
| `summary` | Normalized weakness description. |
| `state` | Current taxonomy lifecycle state. |
| `published_at` | Taxonomy publication time when available. |
| `source_updated_at` | Most recent relevant taxonomy update time. |
| `updated_at` | Time Zero last updated the entity. |
| `revision_id` | Identifier for the normalized revision returned by the request. |

Request optional projections when you need more detail:

| Projection | Contents |
| - | - |
| `overview` | Abstraction level, extended description, likelihood, platforms, consequences, mitigations, and detection methods. |
| `prevention_examples` | Mitigations, detection methods, examples, and observed examples. |
| `affected_targets` | Software targets connected through supporting source claims, when available. |
| `relationships` | Related entities grouped by type, including direction and supporting sources. |
| `provenance` | Field-level evidence keyed by JSON Pointer path. |

Search responses are intentionally more compact than detail responses. Use the API pages for the complete request and response schemas.

## API pages

| Page | Use it for |
| - | - |
| [Search weaknesses](https://docs.zdlake.com/weaknesses/search.md) | Search and filter weakness records. |
| [Get a weakness](https://docs.zdlake.com/weaknesses/get.md) | Retrieve one weakness and request optional projections. |


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.