Cyber Resilience

CVE-2026-27882

Published
30 June 2026
Modified
30 June 2026
CVSS Score v3.1 4.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
EPSS Score 0.0015 4th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2026-27882 is a medium-severity Observable Timing Discrepancy (CWE-208) vulnerability. Its CVSS base score is 4.8 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 4th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and IA-5 (Authenticator Management) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

Coolify is an open-source and self-hostable tool for managing servers, applications, and databases. Prior to 4.0.0-beta.461, the GitLab webhook endpoint uses a non-constant-time string comparison operator (!==) to validate the webhook secret token. This implementation is vulnerable to timing attacks,…

more

which could allow an attacker to gradually discover the secret token by measuring response time differences. This vulnerability is fixed in 4.0.0-beta.461.

CWE(s)
CWE-208

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1110 Brute Force Credential Access
Adversaries may use brute force techniques to gain access to accounts when passwords are unknown or when password hashes are obtained.
attack.mitre.org →
Why these techniques?

Timing attack on exposed webhook secret directly enables brute-force discovery of the token (T1110) against a public-facing management application (T1190).

Confidence: HIGH · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2026-47783Shared CWE-208
CVE-2024-13939Shared CWE-208
CVE-2026-40972Shared CWE-208
CVE-2026-44061Shared CWE-208
CVE-2025-68621Shared CWE-208
CVE-2026-33006Shared CWE-208
CVE-2026-13183Shared CWE-208
CVE-2024-42512Shared CWE-208
CVE-2026-23996Shared CWE-208
CVE-2026-26717Shared CWE-208

Affected Assets

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • AC-3 Access Enforcement
  • SA-8 Security and Privacy Engineering Principles
  • IA-5 Authenticator Management
Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V11.2.4

Mitigating Controls (NIST 800-53 r5) AI

AC-3 Access Enforcement good match
prevent

Directly requires correct enforcement of access decisions based on the webhook secret token; the non-constant-time comparison bypasses that enforcement.

SA-8 Security and Privacy Engineering Principles partial match
prevent

Mandates use of secure engineering principles (constant-time comparison, side-channel resistance) when implementing secret-based authentication such as webhook token validation.

IA-5 Authenticator Management partial match
prevent

Requires proper management and verification of authenticators/secrets, including resistance to disclosure via timing side-channels during comparison.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require constant-time implementations that eliminate observable timing discrepancies.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.17 Clock synchronization none match
none

Consistent reference clocks limit the attacker's ability to measure or manipulate timing differences that could reveal internal state or processing paths.

References