Skip to main content
Menu
CVEs

Cockpit authentication bypass in web worker cron.php

CVE-2026-133990Published November 21, 2026, updated

6.3MediumCNA
Exploited
No known exploitation
Fix
No fix listed
Who is exposed
Not reported

Summary

Cockpit-HQ's Cockpit has a missing authentication flaw in the cron.php file of its Web Worker component. A remote attacker, without logging in, can manipulate the token argument to reach functionality that should require authentication.

Written by a model

Original description

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.

What to do

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-133990 (Cockpit-HQ Cockpit Web Worker cron.php missing authentication), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-133990 (entry last updated 2026-11-21):
Affected:
- Cockpit-HQ Cockpit: versions 2.14.0, 2.14.1
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-133990 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133990 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://vuldb.com/vuln/441597
- https://vuldb.com/vuln/441597/cti
- https://vuldb.com/cve/CVE-2026-133990
- https://vuldb.com/submit/1052045
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-133990
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133990"}.

Affected versions

cve.now Index

28Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity6.3/10CVSS 6.3
  • No patch5/5No patch listed yet

What would change the score

  • Would score about 73 if added to CISA KEV
  • Would score about 68 if CISA's SSVC rates exploitation active
  • Would score about 33 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 7

KindSource
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-133990
RecordNVD · CVE-2026-133990
Public exploit code 1Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).
ExploitGitHub · LeoWSY-hashblue/cve-tls-followup · tree/master/cockpit-failopen
Other links 4
AdvisoryVulDB · Advisory #441597
AdvisoryVulDB · Threat intelligence #441597
AdvisoryVulDB · CVE-2026-133990 record
AdvisoryVulDB · Submission #1052045

Questions about CVE-2026-133990

Is CVE-2026-133990 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-133990?

Cockpit: versions 2.14.0, 2.14.1.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.