Feat/owasp llm 2026 - #15
Merged
Merged
Conversation
… feat/owasp-llm-2026
…nscoped Bash grants - Introduced SKL006 to detect load-time command execution via dynamic-context-injection in agent skills. - Added SKL007 to identify unscoped Bash grants in allowed-tools frontmatter. - Updated rule catalog and skill parsing logic to accommodate new rules. - Created test fixtures for vulnerable skills demonstrating these issues.
…ersistence backdoors, and unsafe deserialization - Introduced SKL008: Detects skills that fetch and execute remote instructions from external URLs, highlighting risks associated with dynamic payloads. - Introduced SKL009: Identifies skills that write backdoors into trust-elevated context files, ensuring persistent changes across sessions. - Introduced SKL010: Flags unsafe deserialization tags in YAML/JSON configurations, preventing potential code execution vulnerabilities. - Updated FRAMEWORK_MAP and RULE_CATALOG to include new skill rules. - Enhanced tool-poisoning checks to support new vulnerability detections. - Added test fixtures for both safe and vulnerable skills to validate new rules.
…es for OWASP 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What and why
Detection logic changes (delete this section if not applicable)
npm run regressionwas run and everyproven/likelyfinding it printed was reviewed against its source linetest-fixtures/vulnerable/andtest-fixtures/safe/src/scanner/catalog.tsandsrc/scanner/explainer.tsboth have an entry for any new rule IDtest/corpus.test.js'sEXPECTED_VULNERABLEwas updated for any new ruleCLI changes (delete this section if not applicable)
test/cli.test.jshas a new or updated case exercising the built binary (src/cli.tschanges aren't covered by any other test file)Checklist
npm run build && npm testpasses