← all corpora

mitre-capec

reference corpus · status live · domain SEC (Security and vulnerabilities) · lane A · refresh pinned · tags GLOBAL · ATTACK-PATTERNS · SECURITY · CLASSIFICATION

What an agent uses it for

an agent reasoning about attack surface queries this for attack-pattern enumerations with prerequisites and mitigations

Use it
curl -fsSLO https://raw.githubusercontent.com/xerj-org/xerj/corpus-hub/tools/xerj-code/hub/mitre-capec.json
xerj corpus add --from ./mitre-capec.json
xerj corpus index mitre-capec then xerj code mitre-capec "your question"

Needs the xerj CLI and a local node running; the copy prompt covers both, checks each step, and shows how to stop only the node you started. No shell: the MCP tool xerj_code_search with corpus: "mitre-capec", once the corpus is indexed on the node.

Sources and pins

sourcepinlicencesizereview note
corpus-mitre-capec c59d35cdb52cMITRE Terms of Use (permissive, notice-preserving) 824.4 KB / 619 files LICENSE-TERMS carries the verbatim grant: non-exclusive royalty-free license for research/development/commercial purposes; any copy authorized provided MITRE's copyright designation and license are reproduced. Condition satisfied in-mirror. Detector records UNKNOWN (not a standard OSS licence). G7 graded 2026-10-04: 3/5 relevant on the pre-registered suite (backlog/g7-mitre-<slug>-2026-10.json; gr

824.4 KB across 619 files. Added 2026-10-04.

People behind this corpus

Upstream authors (1)

Owners of the pinned repositories, credited under each repository's licence. They have not signed up here; their pages are attribution.

xerj-org@xerj-org · upstream

All contributors.

Rights

MITRE Terms of Use (permissive, notice-preserving). Redistribution permitted with attribution per the licence review. The review block records a human opening each licence file at the pin. Detector output is a hint, never the verdict.

Retrieval spot-check (G7)

3.0/5 relevant. Graded .

Q: In a challenge-response login, how do we stop an attacker who opens a second connection and bounces the server's own challenge straight back at it?
expect:
top-5: corpus-mitre-capec/CAPEC-90.md / corpus-mitre-capec/CAPEC-33.md / corpus-mitre-capec/CAPEC-466.md / corpus-mitre-capec/CAPEC-273.md / corpus-mitre-capec/CAPEC-34.md
grade: pass
Q: What kind of access does an intruder need up front before they can tamper with a vendor's patch distribution and push malware out to already-deployed customers?
expect:
top-5: corpus-mitre-capec/CAPEC-672.md / corpus-mitre-capec/CAPEC-522.md / corpus-mitre-capec/CAPEC-669.md / corpus-mitre-capec/CAPEC-671.md / corpus-mitre-capec/CAPEC-34.md
grade: pass
Q: How do I defend a program that writes files with predictable names in a shared directory against someone planting a link to another file at that exact path?
expect:
top-5: corpus-mitre-capec/CAPEC-23.md / corpus-mitre-capec/CAPEC-177.md / corpus-mitre-capec/CAPEC-132.md / corpus-mitre-capec/CAPEC-149.md / corpus-mitre-capec/CAPEC-132.md
grade: pass
Q: What can an attacker accomplish by masquerading as a device the victim already has an established short-range wireless connection with, rather than going through a fresh pairing?
expect:
top-5: corpus-mitre-capec/CAPEC-115.md / corpus-mitre-capec/CAPEC-301.md / corpus-mitre-capec/CAPEC-326.md / corpus-mitre-capec/CAPEC-89.md / corpus-mitre-capec/CAPEC-646.md
grade: miss
Q: Why does one bad answer planted in a shared name-resolution or browser cache keep serving the attacker's content long after the initial corruption happens?
expect:
top-5: corpus-mitre-capec/CAPEC-275.md / corpus-mitre-capec/CAPEC-464.md / corpus-mitre-capec/CAPEC-275.md / corpus-mitre-capec/CAPEC-465.md / corpus-mitre-capec/CAPEC-187.md
grade: miss

Agent score

From structured reviews that AI agents send after they use this corpus: through xerj hub pull, MCP queries, or the xerj_corpus_feedback tool. Each review rates usefulness 1–5, whether the answer was found, and freshness. This is not the human hub star count shown above. The two are never mixed.

Loading agent reviews…

Score = Bayesian mean of usefulness (prior 3.0 with weight 5), so a few reviews cannot swing it. One voice per installation per corpus per week; abnormal-volume reviewers are dropped. Coverage gaps appear only once 3 or more agents report the same one. How it works.

Traffic

Traffic stats load from /api/hub-traffic when this page runs JavaScript.

Views: visits to this page (search-engine crawlers excluded). Unique: distinct visitors per day, by a hash salted with the day, so the 14-day unique figure adds up daily uniques. Pulls: growth of the GitHub release download count of this corpus’s pack (xerj hub pull downloads from there; includes our own pack-verification downloads). Searches: hosted-hub queries for this corpus. Referring sites appear after 3 views. What is collected.

Agent usage

Usage stats load from /api/hub-usage when this page runs JavaScript.

Counted: requests agents send to the hosted hub API (hub.xerj.org/api/v1/code, /def) for this corpus. Queries on your own node (xerj code, xerj ask with a local pack, the MCP tools) never leave your machine and are not counted. Templates replace identifiers, versions, paths, numbers and quoted text with placeholders; one is shown only once it has been seen 3 times in 30 days, and any word asked fewer than 3 times shows as <term>. Raw queries are never published. What is collected.