Is CVE-2026-42172 exploited in the wild?

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

How severe is CVE-2026-42172?

Low severity, with a CVSS score of 3.1, published 7 July 2026.

Which products and versions are affected?

Coollabs Coolify < 4.0.0-beta.474.

Is there a fix for CVE-2026-42172?

A patch was published on 2026-04-20: Fix merged into the repository. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-42172 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-42172?

Check whether you run Coollabs Coolify 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-42172: Coollabs Coolify insufficient session expiration for API tokens

Q: Which products and versions are affected?

Coollabs Coolify < 4.0.0-beta.474.

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

A patch was published on 2026-04-20: Fix merged into the repository. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-42172 attacked?

It is attacked over the network, in a network appliance.

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

Check whether you run Coollabs Coolify 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-42172 · Severity: low · CVSS 3.1 · Published 2026-07-07

Coolify is an open-source platform used to manage servers, applications, and databases. A security issue was identified where API access tokens did not have an expiration date, meaning that if a token was ever leaked or stolen, it would remain valid forever. This could allow unauthorized individuals to maintain long-term access to a company's infrastructure management tools unless the token was manually revoked.

Technologies: Coollabs Coolify. Vendors: Coollabs.

Quick answers

Is CVE-2026-42172 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-42172 being exploited in the wild.
How severe is CVE-2026-42172?: Low severity, with a CVSS score of 3.1, published 7 July 2026.
Which products and versions are affected?: Coollabs Coolify < 4.0.0-beta.474.
Is there a fix for CVE-2026-42172?: A patch was published on 2026-04-20: Fix merged into the repository. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-42172 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-42172?: Check whether you run Coollabs Coolify 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

Coolify suffered from insufficient session expiration (CWE-613) in its API authentication layer. Prior to version 4.0.0-beta.474, personal API tokens generated via Laravel Sanctum did not have an 'expires_at' value enforced, resulting in infinite TTL. An attacker who obtains a leaked token can maintain persistent access to the Coolify API. The fix introduces optional expiration durations (1, 7, 30, 60, or 90 days), implements an hourly pruning job for expired tokens, and adds proactive expiration notifications.

Affected products

coollabsio Coolify < 4.0.0-beta.474

Timeline

2026-04-20: patched: Fix merged into the repository.
2026-04-21: advisory: Release v4.0.0-beta.474 published.
2026-07-07: disclosed: CVE-2026-42172 published.

References

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