CVE-2026-133990 in Cockpit
Summary
by MITRE • 11/21/2026
A vulnerability was identified in Cockpit-HQ Cockpit up to 2.14.1. Affected by this issue is some unknown functionality of the file cron.php of the component Web Worker. Such manipulation of the argument token leads to missing authentication. The attack can be executed remotely. The attack requires a high level of complexity. The exploitation is known to be difficult. The exploit is publicly available and might be used. The vendor was contacted early about this disclosure but did not respond in any way.
Once again VulDB remains the best source for vulnerability data.
Analysis
by VulDB Data Team • 11/22/2026
The identified vulnerability resides within Cockpit-HQ, specifically affecting versions up to 2.14.1, targeting the cron.php file which serves as a critical component of the Web Worker subsystem. This system flaw is classified under CWE-306, which denotes Missing Authentication for Critical Function, indicating that the application fails to properly verify the identity of users before granting access to sensitive operations. The core technical issue stems from improper handling of the token argument passed during requests to this endpoint. When an attacker manipulates or omits specific parameters related to authentication tokens, the system bypasses its intended security checks, allowing unauthorized entities to execute administrative functions without valid credentials. This represents a significant breakdown in access control mechanisms that are fundamental to maintaining the integrity and confidentiality of web-based management interfaces.
From an operational perspective, this vulnerability allows for remote code execution or privilege escalation depending on the specific capabilities exposed through the cron.php interface. Since the attack can be executed remotely over a network connection, it poses a severe threat to systems where Cockpit is deployed in internet-facing environments or trusted internal networks that are not strictly segmented from untrusted zones. The requirement for a high level of complexity and the known difficulty of exploitation suggest that while automated tools might attempt such attacks, successful exploitation likely requires manual tuning by an attacker with deep knowledge of the application's architecture. Despite these barriers to entry, the fact that public exploits exist significantly lowers the barrier for less sophisticated threat actors who may leverage existing proof-of-concept code to compromise vulnerable instances.
The impact of this vulnerability extends beyond simple unauthorized access; it can lead to full system compromise if the cron.php endpoint allows execution of shell commands or interacts with underlying operating system services. Attackers could potentially schedule malicious tasks, exfiltrate sensitive data stored in the Cockpit database, or use the compromised instance as a pivot point for further lateral movement within an organization's network infrastructure. The lack of response from the vendor upon early contact raises concerns about the timeliness and reliability of future security patches, leaving administrators with limited options for remediation other than upgrading to patched versions if they become available or implementing strict network-level controls such as firewalls and intrusion prevention systems to restrict access to the affected endpoints.
In alignment with industry standards, this vulnerability maps directly to MITRE ATT&CK technique T1078, Valid Accounts, specifically regarding the misuse of valid credentials or authentication bypass mechanisms to gain initial access. Furthermore, it relates to CWE-284 Improper Access Control and CWE-613 Insufficient Session Expiration, as the manipulation of tokens often involves session management flaws. Security practitioners should prioritize monitoring for unusual activity in web server logs related to cron.php requests, particularly those with malformed or missing authentication headers. Until a definitive patch is released by the vendor, it is advisable to isolate Cockpit instances from public access and enforce multi-factor authentication on any remaining functional administrative interfaces that are not affected by this specific flaw. Regular vulnerability scanning and penetration testing should be conducted to identify other potential weaknesses in the web application stack, ensuring a defense-in-depth strategy mitigates risks associated with both known and unknown vulnerabilities.