Persistent API access via null token expiration
Published Jul 7, 2026 · Updated Jul 7, 2026
Insufficient token expiration in Coolify before 4.0.0-beta.474 allows remote authenticated users to retain API access through leaked tokens. The Sanctum configuration sets expiration to null, so issued personal access tokens remain valid indefinitely and survive password changes. Possession of an existing token is required; reachable data and actions remain bounded by that token's abilities.
Summary
What happened
Insufficient token expiration in Coolify before 4.0.0-beta.474 allows remote authenticated users to retain API access through leaked tokens. The Sanctum configuration sets expiration to null, so issued personal access tokens remain valid indefinitely and survive password changes. Possession of an existing token is required; reachable data and actions remain bounded by that token's abilities.
The record
- CVE
- CVE-2026-42172
- Published
- Jul 7, 2026
- Updated
- Jul 7, 2026
- Vendor
- coolLabs
- Product
- Coolify
- Classifications
- CWE-613, T1550.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 7, 2026CVE publishedPublication date reported by the CVE source.
- Jul 7, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 4.0.0-beta.474
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- API token non-expiration reproductionproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo