CVE-2026-90945

9.8

crawlab-team · crawlab

Crawlab versions 0 through 0.6.3 contain an authentication bypass vulnerability due to a hard-coded JWT secret, allowing unauthenticated attackers to forge administrator tokens and execute code.

Executive summary

This critical vulnerability in Crawlab is actively exploited in the wild and allows unauthenticated attackers to gain administrative control and execute arbitrary code.

Vulnerability

The application utilizes a hard-coded HMAC-SHA256 secret for JWT token signing, which cannot be modified via configuration. This allows unauthenticated attackers to generate valid administrative tokens to access sensitive APIs and perform remote code execution on worker nodes.

Business impact

The ability for an unauthenticated attacker to gain administrative access presents a total compromise of the application and its underlying infrastructure. With a CVSS score of 9.8, this flaw represents the highest level of risk, potentially leading to unauthorized data exfiltration, full system takeover, and lateral movement within the network.

Remediation

Immediate Action: There is currently no vendor-supplied patch; administrators should immediately isolate affected instances from the internet and restrict access to the administrative API.

Proactive Monitoring: Monitor server logs for unauthorized API requests and unusual token usage, specifically looking for tokens that do not originate from legitimate login sessions.

Compensating Controls: Deploy a Web Application Firewall to block suspicious traffic patterns directed at administrative endpoints and monitor worker nodes for unauthorized process execution.

Exploitation status

Public Exploit Available: Unknown

Analyst recommendation

Given the critical nature of this vulnerability and its confirmed status in the CISA KEV catalog, immediate action is required. Organizations should treat this as a high-priority incident, isolate affected systems, and maintain strict network access controls until a security update is provided by the vendor.

More crawlab-team CVEs

History

  1. Disclosed CVE record published
  2. Collected by CVE Brief via github
  3. Analyst report written
  4. Analyst report updated
  5. Published in the daily brief critical section

Sources

Originally found and disclosed by George Chen, per the CVE Program record.