Add vpatch-CVE-2026-20253 rule and test#46
Closed
crowdsec-automation wants to merge 4 commits into
Closed
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-20253 🔴 |
|
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.
This rule detects exploitation attempts against Splunk Enterprise and Cloud Platform's PostgreSQL sidecar backup endpoint, which allows unauthenticated file creation or truncation (CVE-2026-20253). The attack is characterized by POST requests to the path
/splunkd/__raw/v1/postgres/recovery/backup, optionally prefixed by a region (e.g.,/en-US/). The rule matches any request URI containing this path, usinglowercaseandurldecodetransforms to ensure case-insensitive and encoded variant matching. No argument or body matching is required, as the vulnerability is triggered solely by accessing this endpoint. The labels section includes the correct CVE, ATT&CK, and CWE references. Allvalue:fields are lowercase, and the rule usescontainsfor robust detection with minimal false positives.