Response playbooks, investigation guides, and Atomic Red Team tests are Pro-only. Upgrade to unlock the full detection package for CVE-2026-49352.

Upgrade to Pro
CVE-2026-49352 Google Chronicle · YARA-L

Detect 9router Hardcoded Default JWT Secret Authentication Bypass (CVE-2026-49352) in Google Chronicle

Detects exploitation attempts against 9router (npm package) versions 0.2.21 through 0.4.41, which ship a hardcoded default fallback JWT signing secret (CWE-798). When an operator fails to override the default secret, an attacker can forge arbitrary JWTs (including admin/privileged claims) and bypass authentication entirely. Detection focuses on identifying JWTs signed with the known-public default secret, anomalous authentication success patterns following token forgery, and process/network indicators consistent with public PoC exploitation against 9router deployments.

MITRE ATT&CK

Tactic
Initial Access Privilege Escalation Defense Evasion Credential Access

YARA-L Detection Query

Google Chronicle (YARA-L)
yaral
rule ninerouter_jwt_forgery_cve_2026_49352 {
  meta:
    author = "df00tech"
    description = "Detects successful 9router auth via forged JWT using hardcoded default secret (CVE-2026-49352)"
    severity = "CRITICAL"
  events:
    $auth.metadata.event_type = "USER_LOGIN"
    $auth.target.application = "9router"
    $auth.security_result.action = "ALLOW"
    $auth.additional.fields["jwt_header_alg"] = /HS256|HS384|HS512/
    ($auth.additional.fields["prior_session_id"] = "" or
     $auth.network.http.user_agent = /python-requests|curl|jwt_tool|PyJWT/)
  condition:
    $auth
}
critical severity medium confidence

Chronicle YARA-L rule matching successful 9router login events signed with HMAC JWTs absent prior session linkage or issued via known JWT-forgery tooling.

Data Sources

Application LogsAuthentication Logs

Required Tables

USER_LOGIN

False Positives & Tuning

  • Stateless service-to-service authentication by design
  • Security research/scanning traffic using common HTTP libraries
  • First-time legitimate API consumers

Other platforms for CVE-2026-49352


Testing Methodology

Validate this detection against 4 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are available with Pro.

  1. Test 1Forge JWT using published default secret

    Expected signal: Application auth log entry showing a successful authentication event with HS256 JWT and admin role claim, with no prior session record for the subject.

  2. Test 2Simulate JWT forgery tooling user agent

    Expected signal: HTTP access log and application auth log capturing the jwt_tool user agent string alongside an authentication attempt.

  3. Test 3Validate unrotated default secret configuration

    Expected signal: File access/read event on the 9router config file captured by EDR or file integrity monitoring.

  4. Test 4Windows PowerShell JWT forgery and replay

    Expected signal: Windows PowerShell script block logging (Event ID 4104) capturing the token generation, plus 9router application auth log for the replayed request.

Unlock playbooks & atomic tests with Pro

Get the full detection package for CVE-2026-49352 — response playbook and atomic red team tests, plus investigation guidance and hunting queries.

df00tech Pro — £29/user/month

Response PlaybookInvestigation GuideHunting QueriesAtomic Red Team TestsTuning Guidance

Related Detections