Add vpatch-CVE-2026-0768 rule and test - #71
Open
crowdsec-automation wants to merge 4 commits into
Open
crowdsec-automation wants to merge 4 commits into
crowdsec-automation wants to merge 4 commits into
Conversation
|
Hello @crowdsec-automation and thank you for your contribution! ❗ It seems that the following scenarios are not part of the 'crowdsecurity/appsec-virtual-patching' collection: 🔴 crowdsecurity/vpatch-CVE-2026-0768 🔴 |
|
Hello @crowdsec-automation, ✅ The new VPATCH Rule is compliant, thank you for your contribution! |
|
Hello @crowdsec-automation, Scenarios/AppSec Rule are compliant with the taxonomy, thank you for your contribution! |
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
2 participants
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.
The rule restricts detection to Langflow’s
/api/v1/validate/codeendpoint and the JSONcodeargument, avoiding matches against unrelated requests. It lowercases and URL-decodes both request components, then identifies the Pythonexec(primitive used by the exploit. Thejson.prefix is required because the vulnerable parameter is supplied in anapplication/jsonbody.The test template preserves the exploit request but changes the response matcher to status
403, as required for WAF blocking validation. Classification references CVE-2026-0768, command or scripting execution through ATT&CK technique T1059, and CWE-94 for code injection.Exploit URL: https://github.com/projectdiscovery/nuclei-templates/blob/main/http/cves/2026/CVE-2026-0768.yaml