Which CVEs should I add to my Python security benchmark for AI agents?
CVE-Bench A benchmark for evaluating LLM agents on fixing real-world security vulnerabilities. Agents run inside sandboxed Docker containers and are scored against the maintainer's security test suite. Building Docker images python build.py This builds: A shared base image (cve-bench/base) — Python 3.12, git, poetry, and the harness.
- ▪CVE-Bench A benchmark for evaluating LLM agents on fixing real-world security vulnerabilities.
- ▪Agents run inside sandboxed Docker containers and are scored against the maintainer's security test suite.
- ▪Building Docker images python build.py This builds: A shared base image (cve-bench/base) — Python 3.12, git, poetry, and the harness.
Hacker News (AI / LLM) files mainly under ai. We currently carry 3,301 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | GitHub |
| Canonical URL | https://github.com/GiovanniGatti/cve-bench |
| Publication time | Thu, 23 Jul 2026 14:10:28 +0000 |
| Retrieval time | 2026-07-23T14:14:18.643Z |
| Last seen | 2026-07-23T14:14:18.643Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | 4py4Rll1jyo- |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
CVE-Bench A benchmark for evaluating LLM agents on fixing real-world security vulnerabilities. Agents run inside sandboxed Docker containers and are scored against the maintainer's security test suite. Requirements Python 3.12+ Docker OPENAI_API_KEY, ANTHROPIC_API_KEY, and/or POOLSIDE_API_KEY in your environment (or a .env file) Install dependencies: pip install poetry poetry install Task structure Each task lives under tasks/{CVE-ID}/ and contains: tasks/CVE-2026-33175/ ├── meta.json # GHSA ID, CWE, CVSS, repo URL, vulnerable and fixed SHAs ├── setup.sh # Clones repo, checks out the vulnerable SHA, installs dependencies ├── run_tests.sh # Injects test_security.py into the repo and runs pytest ├── test_security.py # Security tests (xfail on vulnerable code, pass on the fix) ├──…
Excerpt limited to ~120 words for fair-use compliance. The full article is at GitHub.