Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
CVE-2025-29927-Sigma-Rule — Sigma rule for detecting CVE-2025-29927 exploitation via suspicious x-middleware-subrequest HTTP headers in Next.js applications, with detection strategies and mitigation guidance. | Kitploit
Tools/GitHubGitHub/elshaheedy/cve-2025-29927-sigma-rule
Vulnerability AnalysisWeb SecurityThreat IntelligenceIntrusion DetectionLearning & EducationLog Analysis
GitHubelshaheedy/cve-2025-29927-sigma-rule

CVE-2025-29927-Sigma-Rule

Sigma rule for detecting CVE-2025-29927 exploitation via suspicious x-middleware-subrequest HTTP headers in Next.js applications, with detection strategies and mitigation guidance.

View Repository
431 year agoNot yet reviewed
Share

CVE-2025-29927 Report

Overview

CVE-2025-29927 is a security vulnerability in Next.js middleware, allowing attackers to bypass authentication by modifying specific HTTP headers.

Exploitation

Attackers can send a request with the header x-middleware-subrequest: middleware to bypass authentication.

Detection

Detection strategies include:

  • Monitoring HTTP headers for suspicious x-middleware-subrequest values.
  • Implementing Sigma rules to detect unauthorized requests.
  • Enabling logging for middleware actions in Next.js applications.

Mitigation

  • Update to the latest patched version of Next.js.
  • Implement strict request header validation.
  • Enforce authentication at the API layer instead of relying solely on middleware.

References

  • CVE Details

Can We Use a Sigma Rule to Detect CVE-2025-29927? ✅ Yes, but only if the logging environment captures HTTP headers correctly. If the web server (e.g., Apache, Nginx) logs the x-middleware-subrequest header, the Sigma rule will successfully detect the attack.

🚨 No, if the logs do not contain this header. If the web server does not record HTTP headers in the logs, the Sigma rule will not detect the exploitation, even if the rule is correctly written.

📌 Recommendation: Ensure that your logging configuration includes full HTTP headers before relying on Sigma rules for detection.

Download Tool

Most Popular

View all →

Discover the most used tools by our community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 The ultimate OSINT toolkit: investigation graph, confidence scoring, alias families, map, timeline and reports. 49 modules, 400+ sites, no API keys required.

    831
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock One-Tap Execution App (CVE-2026-43499)

    534
  • 3

    ARTEX

    baarai/artex

    LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting.

    429
  • 4

    redforge

    cybersecurity91/redforge

    Browser-side red team toolkit with 102 offline tools for recon, payload generation, credential attacks, crypto, encoding and engagement reporting.

    355
  • 5

    looking-glass

    anonghosty/looking-glass

    CSIRT platform that ingests Shadowserver reports into MongoDB and replays them as interactive maps, analysis, findings, advisories and executive dashboards.

    284
  • 6

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    The system of action for AI-native cybersecurity—where intent becomes governed execution, evidence becomes operational memory, and every operation improves the next.

    275

Explore all tools

Browse our collection of tools

View all tools →