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

Upgrade to Pro
CVE-2026-55500 Splunk · SPL

Detect 9router (npm) Unprotected Database Import/Export Leading to Credential Theft and Database Takeover (CVE-2026-55500) in Splunk

CVE-2026-55500 affects the 9router npm package (<= 0.4.71), which exposes an unauthenticated/improperly-protected database import/export interface. Attackers can invoke this exposed functionality to exfiltrate the entire application database — including credentials, session tokens, and configuration secrets — or import a malicious database to achieve full application takeover. CVSS 9.9, CWE-200 (Exposure of Sensitive Information). A public PoC/advisory exists (GHSA-qvfm-67h2-2qfx). Detections focus on anomalous HTTP requests to database export/import endpoints, bulk data egress, unauthenticated administrative API access, and post-exploitation credential misuse.

MITRE ATT&CK

Tactic
Initial Access Credential Access Collection Exfiltration

SPL Detection Query

Splunk (SPL)
spl
index=web sourcetype=access_combined OR sourcetype=nginx OR sourcetype=apache
| regex uri="(?i)(/api/export|/api/db/export|/api/database/export|/api/import|/api/db/import|/api/backup)"
| eval has_auth=if(match(cookie, "session|auth|token"), 1, 0)
| where has_auth=0 OR match(useragent, "(?i)(curl|python-requests|go-http-client|httpie|axios)")
| stats count as request_count, min(_time) as first_seen, max(_time) as last_seen, values(uri) as paths, values(useragent) as agents by clientip
| where request_count >= 1
| convert ctime(first_seen) ctime(last_seen)
critical severity medium confidence

Identifies unauthenticated or scripted access attempts against 9router's database export/import endpoints, consistent with exploitation of CVE-2026-55500.

Data Sources

Web Server Access LogsReverse Proxy LogsWAF Logs

Required Sourcetypes

access_combinednginxapache

False Positives & Tuning

  • Internal cron/backup automation using curl or Python without full auth cookie logging
  • Authorized DevOps scripts exporting data for migration
  • Third-party integration polling similarly-named paths

Other platforms for CVE-2026-55500


Testing Methodology

Validate this detection against 3 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 1Simulate Unauthenticated Database Export Request

    Expected signal: Web server access log entry showing GET/POST to /api/db/export with no Authorization or session cookie header, response status 200 and non-trivial body size.

  2. Test 2Simulate Unauthorized Database Import

    Expected signal: Web server log entry for POST to /api/db/import with multipart file upload and no auth header; application log showing database write/replace event.

  3. Test 3Scripted Reconnaissance of Export/Import/Backup Endpoints

    Expected signal: Multiple sequential unauthenticated HTTP requests from a single source IP to distinct export/import/backup paths within a short time window, with a scripted (non-browser) User-Agent.

Unlock playbooks & atomic tests with Pro

Get the full detection package for CVE-2026-55500 — 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