Is CVE-2026-5300 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-5300 being exploited in the wild.

How severe is CVE-2026-5300?

Medium severity, with a CVSS score of 5.9, published 8 April 2026.

Which products and versions are affected?

CoolerControl >= 0.14.0, < 4.0.0.

Is there a fix for CVE-2026-5300?

A patch was published on 2026-04-08: Fixed in version 4.0.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-5300 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-5300?

Check whether you run CoolerControl or Coolercontrold at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-5300: CoolerControl coolercontrold missing authentication in API router

Q: Is there a fix for CVE-2026-5300?

A patch was published on 2026-04-08: Fixed in version 4.0.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-5300 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-5300?

Check whether you run CoolerControl or Coolercontrold at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-5300 · Severity: medium · CVSS 5.9 · Published 2026-04-08

CoolerControl is a system daemon used to monitor and control cooling hardware like fans and liquid coolers. A security flaw in versions prior to 4.0.0 allows unauthorized individuals to access the software's management interface without a password. This could allow an attacker to view sensitive system information or maliciously change cooling settings, potentially leading to hardware overheating or system instability.

Technologies: Coolercontrold. Vendors: Coolercontrol.

Quick answers

Is CVE-2026-5300 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-5300 being exploited in the wild.
How severe is CVE-2026-5300?: Medium severity, with a CVSS score of 5.9, published 8 April 2026.
Which products and versions are affected?: CoolerControl >= 0.14.0, < 4.0.0.
Is there a fix for CVE-2026-5300?: A patch was published on 2026-04-08: Fixed in version 4.0.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-5300 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-5300?: Check whether you run CoolerControl or Coolercontrold at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A missing authentication vulnerability (CWE-306) exists in the coolercontrold daemon of CoolerControl versions prior to 4.0.0. The issue resides in the API router component, which fails to enforce authentication for critical functions accessible via HTTP requests. A remote, unauthenticated attacker can exploit this to interact with the daemon's API, allowing them to read sensitive system data or modify hardware control configurations. While some assessments categorize this as local, the NVD-provided vector suggests network reachability (AV:N) with high impact on confidentiality and integrity. The vulnerability is addressed in version 4.0.0.

Affected products

CoolerControl coolercontrold >= 0.14.0, < 4.0.0

Timeline

2026-04-08: disclosed
2026-04-08: advisory
2026-04-08: patched: Fixed in version 4.0.0

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.