Monthly
Drupal's Commerce CyberSource payment integration module (all versions prior to 1.10.0) contains a timing side-channel vulnerability (CWE-208) that enables brute-force attacks against authentication or token-validation operations. Remote unauthenticated attackers can exploit measurable differences in response timing to iteratively confirm the validity of credentials or secrets, achieving limited integrity impact. Vendor-released patch version 1.10.0 is available via the Drupal security advisory sa-contrib-2026-106; no public exploit code or CISA KEV listing has been identified at time of analysis.
Timing side-channel exposure in phpseclib's pure-PHP X25519 scalar multiplication allows a local observer to recover a reused 251-bit clamped private key. Data-dependent conditional modular reductions in PrimeField/Integer.php cause per-step timing and libgmp call-count variation during the Montgomery ladder, leaking scalar bits when the same private key is used across multiple operations. Only applications using a long-lived or reused X25519 private key on the pure-PHP code path are at risk; phpseclib's standard SSH ephemeral key exchange is explicitly unaffected. Vendor-released patches exist in versions 3.0.57 and 4.0.1; no public exploit has been identified at time of analysis.
Account enumeration in Cockpit CMS before 2.14.1 exposes valid usernames through measurable response-time differences in the authentication check endpoint. When a submitted username matches an existing account, the application performs a full bcrypt hash comparison - an intentionally slow operation - whereas non-existent accounts return immediately without any hash computation, creating a statistically detectable timing delta. Unauthenticated remote attackers can exploit this by issuing repeated authentication probes and measuring latency, building a list of valid accounts to target with credential stuffing or brute-force attacks. No public exploit code or CISA KEV listing has been identified at time of analysis, though a researcher advisory (MFC-2026-001) exists.
Non-constant-time authentication comparisons and plaintext logging of XRES* in free5GC's AUSF component (v1.4.4 and earlier) expose two distinct vulnerability classes under CWE-208. The 5G-AKA confirmation path writes the expected XRES* value to INFO-level application logs immediately before comparison, making authentication material directly readable by any principal with AUSF log access - operators, SIEM agents, log-collection sidecars, or compromised containers. Both 5G-AKA and EAP-AKA' confirmation paths use non-constant-time Go primitives (strings.EqualFold, bytes.Equal, ==) instead of crypto/subtle.ConstantTimeCompare, though the researcher's own PoC confirmed the timing signal is too small to distinguish from HTTP/SBI noise under standard network conditions. No public exploit or CISA KEV listing; patched in v1.4.5.
Blind server-side request forgery in WatchGuard Dimension's Database Server Test configuration feature allows an authenticated privileged attacker to enumerate network services on adjacent systems by exploiting observable timing or response discrepancies (CWE-208). The scope of impact extends beyond the Dimension host itself to adjacent network segments, enabling internal network reconnaissance without direct access to those systems. No public exploit is identified at time of analysis, and the high privilege requirement substantially limits the realistic attacker pool.
Timing side-channel exposure in Spring Security allows remote unauthenticated attackers to progressively infer security-sensitive string values - such as CSRF tokens, bearer tokens, or other secrets compared at the application layer - by statistically measuring the time differential between rejection responses. Multiple active Spring Security release trains are affected, spanning versions 5.7.x through 7.1.x, representing a broad swath of production Spring-based Java applications. No public exploit code has been identified at time of analysis, and CISA KEV status is absent; however, the confidentiality impact is rated High in the CVSS vector, reflecting that successful exploitation could fully compromise protected secrets under favorable network conditions.
Timing oracle in Kimai's TokenAuthenticator (all 2.x versions before 2.54.0) allows unauthenticated network attackers to enumerate valid usernames by measuring a consistent ~25ms response time differential - argon2id password hashing executes only when a matched user record exists, leaking username validity despite identical HTTP 403 response bodies. No authentication, API token, or session cookie is required to exploit this flaw against default Kimai deployments. A fully functional proof-of-concept Python script is publicly available in the GitHub Security Advisory (GHSA-jrc6-fmhw-fpq2), making this a low-barrier reconnaissance primitive for follow-on credential attacks; no confirmed active exploitation (CISA KEV) has been recorded at time of analysis.
Observable timing discrepancy in the Drupal Token Content Access module exposes token-protected content to brute-force enumeration via side-channel analysis. All module versions from 0.0.0 through 3.1.2 are affected; unauthenticated remote attackers (PR:N, AV:N per CVSS) can measure differential response times during token validation to reconstruct valid access tokens character-by-character, ultimately bypassing content access restrictions. No active exploitation has been confirmed (SSVC exploitation: none, EPSS 0.14%, no KEV listing), and a vendor patch is available per Drupal SA-CONTRIB-2026-090.
Timing side-channel in Grav CMS before 2.0.16 allows remote attackers to weaken CSRF protection by recovering valid nonce values through statistical analysis of server response latency. The `Utils::verifyNonce()` function uses PHP's non-constant-time `===` operator instead of `hash_equals()`, enabling byte-by-byte nonce reconstruction via repeated probing requests. No public exploit is identified at time of analysis, but the CWE-208 vulnerability class is well-documented in security literature and the technique is reproducible with standard tooling.
Password reset and account activation token comparison in Grav Login Plugin before 3.9.1 uses PHP's non-constant-time === operator instead of hash_equals(), exposing a CWE-208 timing oracle in both taskReset() (classes/Controller.php) and the activation handler (login.php). Combined with the absence of rate limiting on the token-submission endpoint, an unauthenticated network attacker can submit high-volume repeated token guesses against a known username and statistically recover a valid reset token via timing discrepancy. No public exploit code has been identified and the vulnerability is not listed in CISA KEV; the vendor itself characterizes practical exploitability as low, and no end-to-end network exploitation has been demonstrated.
Drupal's Commerce CyberSource payment integration module (all versions prior to 1.10.0) contains a timing side-channel vulnerability (CWE-208) that enables brute-force attacks against authentication or token-validation operations. Remote unauthenticated attackers can exploit measurable differences in response timing to iteratively confirm the validity of credentials or secrets, achieving limited integrity impact. Vendor-released patch version 1.10.0 is available via the Drupal security advisory sa-contrib-2026-106; no public exploit code or CISA KEV listing has been identified at time of analysis.
Timing side-channel exposure in phpseclib's pure-PHP X25519 scalar multiplication allows a local observer to recover a reused 251-bit clamped private key. Data-dependent conditional modular reductions in PrimeField/Integer.php cause per-step timing and libgmp call-count variation during the Montgomery ladder, leaking scalar bits when the same private key is used across multiple operations. Only applications using a long-lived or reused X25519 private key on the pure-PHP code path are at risk; phpseclib's standard SSH ephemeral key exchange is explicitly unaffected. Vendor-released patches exist in versions 3.0.57 and 4.0.1; no public exploit has been identified at time of analysis.
Account enumeration in Cockpit CMS before 2.14.1 exposes valid usernames through measurable response-time differences in the authentication check endpoint. When a submitted username matches an existing account, the application performs a full bcrypt hash comparison - an intentionally slow operation - whereas non-existent accounts return immediately without any hash computation, creating a statistically detectable timing delta. Unauthenticated remote attackers can exploit this by issuing repeated authentication probes and measuring latency, building a list of valid accounts to target with credential stuffing or brute-force attacks. No public exploit code or CISA KEV listing has been identified at time of analysis, though a researcher advisory (MFC-2026-001) exists.
Non-constant-time authentication comparisons and plaintext logging of XRES* in free5GC's AUSF component (v1.4.4 and earlier) expose two distinct vulnerability classes under CWE-208. The 5G-AKA confirmation path writes the expected XRES* value to INFO-level application logs immediately before comparison, making authentication material directly readable by any principal with AUSF log access - operators, SIEM agents, log-collection sidecars, or compromised containers. Both 5G-AKA and EAP-AKA' confirmation paths use non-constant-time Go primitives (strings.EqualFold, bytes.Equal, ==) instead of crypto/subtle.ConstantTimeCompare, though the researcher's own PoC confirmed the timing signal is too small to distinguish from HTTP/SBI noise under standard network conditions. No public exploit or CISA KEV listing; patched in v1.4.5.
Blind server-side request forgery in WatchGuard Dimension's Database Server Test configuration feature allows an authenticated privileged attacker to enumerate network services on adjacent systems by exploiting observable timing or response discrepancies (CWE-208). The scope of impact extends beyond the Dimension host itself to adjacent network segments, enabling internal network reconnaissance without direct access to those systems. No public exploit is identified at time of analysis, and the high privilege requirement substantially limits the realistic attacker pool.
Timing side-channel exposure in Spring Security allows remote unauthenticated attackers to progressively infer security-sensitive string values - such as CSRF tokens, bearer tokens, or other secrets compared at the application layer - by statistically measuring the time differential between rejection responses. Multiple active Spring Security release trains are affected, spanning versions 5.7.x through 7.1.x, representing a broad swath of production Spring-based Java applications. No public exploit code has been identified at time of analysis, and CISA KEV status is absent; however, the confidentiality impact is rated High in the CVSS vector, reflecting that successful exploitation could fully compromise protected secrets under favorable network conditions.
Timing oracle in Kimai's TokenAuthenticator (all 2.x versions before 2.54.0) allows unauthenticated network attackers to enumerate valid usernames by measuring a consistent ~25ms response time differential - argon2id password hashing executes only when a matched user record exists, leaking username validity despite identical HTTP 403 response bodies. No authentication, API token, or session cookie is required to exploit this flaw against default Kimai deployments. A fully functional proof-of-concept Python script is publicly available in the GitHub Security Advisory (GHSA-jrc6-fmhw-fpq2), making this a low-barrier reconnaissance primitive for follow-on credential attacks; no confirmed active exploitation (CISA KEV) has been recorded at time of analysis.
Observable timing discrepancy in the Drupal Token Content Access module exposes token-protected content to brute-force enumeration via side-channel analysis. All module versions from 0.0.0 through 3.1.2 are affected; unauthenticated remote attackers (PR:N, AV:N per CVSS) can measure differential response times during token validation to reconstruct valid access tokens character-by-character, ultimately bypassing content access restrictions. No active exploitation has been confirmed (SSVC exploitation: none, EPSS 0.14%, no KEV listing), and a vendor patch is available per Drupal SA-CONTRIB-2026-090.
Timing side-channel in Grav CMS before 2.0.16 allows remote attackers to weaken CSRF protection by recovering valid nonce values through statistical analysis of server response latency. The `Utils::verifyNonce()` function uses PHP's non-constant-time `===` operator instead of `hash_equals()`, enabling byte-by-byte nonce reconstruction via repeated probing requests. No public exploit is identified at time of analysis, but the CWE-208 vulnerability class is well-documented in security literature and the technique is reproducible with standard tooling.
Password reset and account activation token comparison in Grav Login Plugin before 3.9.1 uses PHP's non-constant-time === operator instead of hash_equals(), exposing a CWE-208 timing oracle in both taskReset() (classes/Controller.php) and the activation handler (login.php). Combined with the absence of rate limiting on the token-submission endpoint, an unauthenticated network attacker can submit high-volume repeated token guesses against a known username and statistically recover a valid reset token via timing discrepancy. No public exploit code has been identified and the vulnerability is not listed in CISA KEV; the vendor itself characterizes practical exploitability as low, and no end-to-end network exploitation has been demonstrated.