Add OWASP Top 10 for LLM Applications 2026 as a mapped resource

Aperta
  • Qualcosa non va?
#1,015 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
48/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Tranquilla
Stack tecnologico
python
Ambito
content, security

Direzione di ricerca

Inizia da CONTRIBUTING.md e dal processo esistente per le risorse e i mapping del 2025. Dopo che un maintainer ha selezionato Route A o B, usa CREmappingtemplate.xls per il percorso del foglio di calcolo, oppure esamina application/tests/fixtures/owasp_mappings/, owasp_llm_top10_2025_parser_test.py, il pattern dell’importer in #960 e scripts/import-all.sh per il percorso del codice. È completato quando la risorsa 2026 è distinta da quella del 2025 e i suoi mapping sono stati revisionati oppure sono coperti dai test dell’importer e dal wiring.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

The ask

The 2026 edition of the OWASP Top 10 for LLM Applications is out and OpenCRE doesn't carry it yet. I'd like to add it as a new resource and do the mapping work myself. I co-lead the project, so I can supply the source document and answer questions about what any entry was meant to cover.

I need a yes to proceed, and a pick between the two routes at the bottom.

I'm opening an issue instead of a PR because CONTRIBUTING.md asks contributors to wait for a maintainer to acknowledge a ticket first.

Why it needs its own resource name

OpenCRE serves OWASP Top10 for LLM today and its sections are named for the 2025 edition, like LLM01:2025 Prompt Injection.

The 2026 edition reshuffled the list. Eight of the ten IDs now point somewhere different than they did in 2025:

ID 2025 2026
LLM01 Prompt Injection Prompt Injection
LLM02 Sensitive Information Disclosure Sensitive Information Disclosure
LLM03 Supply Chain Excessive Agency
LLM04 Data and Model Poisoning Supply Chain
LLM05 Improper Output Handling Data and Model Poisoning
LLM06 Excessive Agency Unbounded Consumption
LLM07 System Prompt Leakage Misinformation
LLM08 Vector and Embedding Weaknesses Hidden Context Exposure
LLM09 Misinformation Vector and Embedding Weaknesses
LLM10 Unbounded Consumption Improper Output Handling

LLM08 is worth a closer look, because it's the one entry that isn't just a renumber. System Prompt Leakage became Hidden Context Exposure, and the scope widened past the system prompt to anything the application assembles into the context window, including developer instructions, policy text pulled from RAG, and the schemas of tools the model can call. A mapping inherited from the 2025 entry would miss most of that.

If both editions shared a resource name, /smartlink/standard/OWASP Top10 for LLM/LLM03 resolves to Supply Chain or Excessive Agency depending on which import ran last. You already split OWASP Top 10 2017 and OWASP Top 10 2021 for the same reason.

None of this touches the 2025 resource. It stays as it is.

How I'd build the mapping

I'd go through the CRE catalog entry by entry with the mapping template spreadsheet, putting each 2026 entry's name, ID, and link on the row of the Common Requirement that fits.

A few of the entries are finer grained than anything in the catalog right now. Where that happens I'll propose a new child requirement with the NEW|<name> convention rather than stretch an existing CRE to cover it.

I won't build any of it from CWE or another standard already in OpenCRE. CONTRIBUTING.md warns that detail gets lost that way and I agree, particularly for the entries about agent behavior rather than a code defect.

Pick a route

Route A is the spreadsheet. I fill in CREmappingtemplate.xls, attach it here, and you review it before anything imports. That's the path CONTRIBUTING.md lays out for content.

Route B is code. I add the 2026 fixture under application/tests/fixtures/owasp_mappings/, the parser, a test next to owasp_llm_top10_2025_parser_test.py, and the CLI and scripts/import-all.sh wiring. Route B rides on the importer pattern in #960, so it waits for #960 to land.

Say A or B and I'll start.

Duplicate check

I read through the open and closed issues and the open PRs before filing. #960 is the closest thing, and it covers the 2025 edition and the importer plumbing rather than 2026 content.

Lingua principale
Python
Stelle
210
Fork
167
Merge medio
4g 12h
PR unite (30g)
28

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di OWASP/OpenCRE

Tutte le issue di OWASP/OpenCRE

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.