Cyber Resilience

CVE-2026-41588

Inducer Relate ≤ 2026-04-17

Published
08 May 2026
Modified
17 June 2026
Patch / advisory
CVSS Score v3.1 9.0
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
EPSS Score 0.0036 30th percentile
Risk Priority 63 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-41588 is a critical-severity Observable Timing Discrepancy (CWE-208) vulnerability in Inducer Relate. Its CVSS base score is 9.0 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Account Discovery (T1087); ranked at the 30th 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 IA-6 (Authentication Feedback) and SA-11 (Developer Testing and Evaluation) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

RELATE is a web-based courseware package. Prior to commit 2f68e16, there is a timing attack vulnerability in course/auth.py — check_sign_in_key(). This issue has been patched via commit 2f68e16.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1087 Account Discovery Discovery
Adversaries may attempt to get a listing of valid accounts, usernames, or email addresses on a system or within a compromised environment.
T1087.001 Local Account Discovery
Adversaries may attempt to get a listing of local system accounts.
T1087.002 Domain Account Discovery
Adversaries may attempt to get a listing of domain accounts.
T1087.003 Email Account Discovery
Adversaries may attempt to get a listing of email addresses and accounts.
T1087.004 Cloud Account Discovery
Adversaries may attempt to get a listing of cloud accounts.
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.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-32404Same product: Inducer Relate
CVE-2024-32405Same product: Inducer Relate
CVE-2024-32407Same product: Inducer Relate
CVE-2024-32406Same product: Inducer Relate
CVE-2024-0202Shared CWE-203, CWE-208
CVE-2023-25529Shared CWE-203, CWE-208
CVE-2023-32694Shared CWE-203, CWE-208
CVE-2023-25000Shared CWE-203, CWE-208
CVE-2025-8774Shared CWE-203, CWE-208
CVE-2024-1543Shared CWE-203, CWE-208

Affected Assets

inducer
relate
≤ 2026-04-17

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)
  • 1 hardening rule · 1 OS baseline
Validate
Prove the fix (OWASP ASVS)
  • V11.2.4

Mitigating Controls (NIST 800-53 r5) AI

Obscures authentication feedback so that success/failure differences are not observable to attackers.

Developer testing can include timing analysis or side-channel test cases that reveal observable timing discrepancies.

Requires error messages to avoid revealing exploitable details, directly stopping observable response discrepancies.

Engineering principles can mandate constant-time algorithms and side-channel resistance so timing discrepancies are never introduced.

Requiring approved cryptographic modules and algorithms implicitly demands implementations free of observable timing leaks.

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 partial match
prevents

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

References