CVE-2026-5300
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedUnauthenticated functionality in CoolerControl/coolercontrold <4.0.0 allows unauthenticated attackers to view and modify potentially sensitive data via HTTP requests
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe coolercontrold application contains an unauthenticated HTTP endpoint that exposes sensitive functionality, allowing remote attackers to read and modify data without any credentials. This affects all versions prior to 4.0.0.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 4.0.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed CoolerControl versionRun 'coolercontrold --version' or check package version with 'dpkg -l | grep coolercontrol' (Debian) or 'rpm -qa | grep coolercontrol' (RHEL). Alternatively, check the running daemon process version if displayed in logs or control interface.Affected if Version is lower than 4.0.0 (e.g., 3.x.x, 2.x.x, or any version number less than 4.0.0)
-
Confirm CoolerControl daemon is runningRun 'systemctl status coolercontrold' or 'ps aux | grep coolercontrold' to verify the daemon process is active.Affected if Daemon is running and version is below 4.0.0
-
Check network binding configurationRun 'ss -tlnp | grep coolercontrold' or 'netstat -tlnp | grep coolercontrold' to determine which network interfaces the HTTP service is listening on.Affected if Service binds to 0.0.0.0 or all interfaces (0.0.0.0:port) rather than localhost only (127.0.0.1:port)
-
Verify service is accessible without authenticationSend an HTTP request to the daemon endpoint (e.g., curl http://<daemon_host>:<port>/api/status or similar endpoint) without providing any authentication headers or credentials.Affected if HTTP requests to the daemon succeed without authentication and return valid data or allow configuration changes
You are affected if CoolerControl version is below 4.0.0 and the daemon HTTP service is exposed on a network interface accessible to untrusted parties, allowing unauthenticated access to sensitive data or configuration functions.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data4.0.0
Upgrade to coolercontrold version 4.0.0 or later to obtain the patched code. If immediate upgrading is not feasible, implement network-level access controls to restrict HTTP access to trusted IP addresses only.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-5300 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-5300 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data