Skip to content
statance
MenuClose
Log inStart for free ↗
medium · CVSS 5.9

CVE-2026-91147

Cockpit: cockpit: denial of service in `cockpit-ws` due to url-root handling without a trailing slash

Published 18 Sept 2026 · Source updated 6 Nov 2026 · Retrieved 2026-11-06 01:53 UTC

Monitor this CVE ↗Full CVE monitoring on Pro and Business

What happened?

A flaw was found in `cockpit-ws`. This vulnerability allows a remote, unauthenticated attacker to cause a Denial of Service (DoS) by sending a specially crafted request. When the `WebService.UrlRoot` is configured and a request is made to the exact URL-root prefix without a trailing slash, `cockpit-ws` can terminate unexpectedly. This issue leads to the unavailability of the Cockpit web service.

Description supplied by CVE Program. Formatting is simplified; follow the original advisory for full details.

Affected software and versions

Source-provided software and version information
SoftwareVersion informationFixed version
cockpitRed Hatunaffected: 0:310.10-1.el8_10 to < *See vendor advisory
cockpitRed Hatunaffected: 0:356.4-1.el9_8 to < *See vendor advisory
cockpitRed Hatunaffected: 0:356.4-1.el9_8 to < *See vendor advisory
cockpitRed HatDefault status: affectedSee vendor advisory
cockpitRed HatDefault status: affectedSee vendor advisory
devspaces/udi-base-rhel10Red HatDefault status: affectedSee vendor advisory
devspaces/udi-base-rhel9Red HatDefault status: affectedSee vendor advisory
devspaces/udi-rhel9Red HatDefault status: affectedSee vendor advisory

Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.

Is it being exploited?

This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.

CISA data retrieved 2026-11-06 16:38 UTC. Check CISA ↗

How to respond

  1. Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
  2. Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
  3. Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.

Sources and remediation references

This public advisory does not determine whether a particular server is affected. Records are refreshed as sources change; verify urgent decisions against the original advisory.

← Browse the public CVE feed