What is the CVSS score of EUVD-2026-41980?

EUVD-2026-41980 has a CVSS 3.1 base score of 3.1 (Low). CVSS vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N. EPSS exploitation probability: 0.2%.

Is there a patch available for EUVD-2026-41980?

Yes, a patch is available for EUVD-2026-41980. Update the affected software to the latest version immediately.

Coolify EUVD-2026-41980

| CVE-2026-42172 LOW

Insufficient Session Expiration (CWE-613)

2026-07-07 GitHub_M

Information Disclosure Coolify

3.1

CVSS 3.1 · Vendor: GitHub_M

Severity by source

Vendor (GitHub_M) PRIMARY

3.1 LOW

AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N

vuln.today AI

3.1 LOW

Token leak is a required precondition (AC:H, PR:L); read-only API access limits impact to C:L with no integrity or availability consequence.

3.1 AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N

4.0 AV:N/AC:H/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (GitHub_M).

CVSS VectorVendor: GitHub_M

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N

Attack Vector

Network

Attack Complexity

High

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

None

Availability

None

Lifecycle Timeline

Patch available

Jul 07, 2026 - 05:01 EUVD

Analysis Generated

Jul 07, 2026 - 04:11 vuln.today

DescriptionCVE.org

Coolify is an open-source and self-hostable tool for managing servers, applications, and databases. Prior to 4.0.0-beta.474, Sanctum API tokens did not expire, allowing a leaked token to retain access indefinitely until manually revoked. This issue is fixed in version 4.0.0-beta.474.

AnalysisAI

Sanctum API tokens in Coolify never expire prior to v4.0.0-beta.474, meaning any token that is leaked or stolen remains permanently valid until an administrator manually revokes it. This affects the self-hosted server, application, and database management platform across all versions below 4.0.0-beta.474. …

Unlock full vulnerability intelligence

Risk assessment & exploitation conditions
Attack chain visualization
Remediation with exact patch versions
Threat intelligence from 22 sources
Personal watchlist & email alerts

Continue with Google Continue with GitHub

Free forever · No credit card required

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata

Access

Obtain leaked Coolify API token

Exploit

Authenticate to Coolify API endpoint

Execution

Query API for server and application configuration

Impact

Exfiltrate sensitive deployment data

Access

Obtain leaked Coolify API token

Exploit

Authenticate to Coolify API endpoint

Execution

Query API for server and application configuration

Impact

Exfiltrate sensitive deployment data

Vulnerability AssessmentAI

Exploitation	Exploitation requires the attacker to first obtain a valid Coolify Sanctum API token through a separate vector - the CVSS PR:L metric confirms a low-privilege authenticated credential is necessary; unauthenticated exploitation is not possible. … Additional conditions and limiting factors are described in the full assessment.
Risk Assessment	The CVSS 3.1 score of 3.1 (AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N) accurately reflects the constrained nature of this vulnerability. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in.
Exploit Scenario	An attacker who intercepts a Coolify API token - for example, from an exposed environment variable in a public repository, an unprotected log file, or a compromised CI/CD pipeline - can use that token indefinitely to query the Coolify API and retrieve sensitive configuration data about managed servers, applications, and databases. Because the token never expires, the attacker retains access silently even after the original credential leak is forgotten or the legitimate user rotates their password. …
Remediation	The primary fix is to upgrade Coolify to v4.0.0-beta.474 or later, available at https://github.com/coollabsio/coolify/releases/tag/v4.0.0-beta.474. … Detailed patch versions, workarounds, and compensating controls in full report.