A timing attack against mod_auth_digest in Apache HTTP Server 2.4.66 allows a bypass of Digest authentication by a remote attacker.
Users are recommended to upgrade to version 2.4.67, which fixes this issue.
A timing side-channel vulnerability in Traefik's BasicAuth middleware prior to versions 2.11.43, 3.6.14, and 3.7.0-rc.2 allows attackers to enumerate valid usernames by measuring authentication response times. The issue arises because a variable intended for a constant-time fallback secret is empty, causing the comparison to short-circuit quickly and reveal timing differences. This vulnerability has been patched in the specified versions.
OpenClaw versions before 2026.4.2 have a timing side channel vulnerability due to early length-mismatch checks in shared-secret comparisons. This allows attackers to measure timing differences and infer secret-length information, weakening the intended constant-time security for shared secrets. The vulnerability is identified as CWE-208 and has a medium severity with a CVSS score of 6.3.
An attacker on the same network as the remote application may be able to utilize a timing attack to discover information about the remote secret. In extreme circumstances this could result in the attacker determining the secret and uploading changed classes, thereby achieving remote code execution in the remote application.
Affected: Spring Boot 4.0.0–4.0.5 (fix 4.0.6), 3.5.0–3.5.13 (fix 3.5.14), 3.4.0–3.4.15 (fix 3.4.16), 3.3.0–3.3.18 (fix 3.3.19), 2.7.0–2.7.32 (fix 2.7.33); DevTools remote secret comparison. Versions that are no longer supported are also affected per vendor advisory.
Mojic versions prior to 2.1.4 contain a timing side-channel vulnerability in the CipherEngine's HMAC-SHA256 integrity verification. The use of a standard equality operator (! ==) during decryption causes an observable timing discrepancy (CWE-208), which could allow an attacker to bypass the file integrity check via timing analysis. This vulnerability has a medium severity rating and a CVSS score of 4.7. The issue is fixed in version 2.1.4.
CVE-2026-41418 is a timing side-channel vulnerability in 4ga Boards versions prior to 3.3.5 that allows user enumeration via the login endpoint. The server responds significantly faster when an invalid username/email is provided compared to a valid username/email with an incorrect password, due to the bcrypt.compareSync() operation. This timing difference is easily detectable over a network with a single request. The vulnerability has a medium severity with a CVSS score of 5.3 and is fixed in version 3.3.5.
CVE-2026-40263 is a timing discrepancy vulnerability in the open-source note-taking application Note Mark, versions 0.19.1 and earlier. The login endpoint only performs bcrypt password verification when the username exists, returning immediately for nonexistent usernames. This behavior allows unauthenticated attackers to enumerate valid usernames by measuring response times. The issue has been fixed in version 0.19.2. The vulnerability has a low CVSS score of 3.7 and does not impact integrity or availability.
ApostropheCMS is an open-source Node.js content management system. Versions 4.28.0 and prior contain a timing side-channel vulnerability in the password reset endpoint (/api/v1/@apostrophecms/login/reset-request) that allows unauthenticated username and email enumeration. When a user is not found, the handler returns after a fixed 2-second artificial delay, but when a valid user is found, it performs a MongoDB update and SMTP email send with no equivalent delay normalization, producing measurably different response times. The endpoint also accepts both username and email via an $or query, and has no rate limiting as the existing checkLoginAttempts throttle only applies to the login flow. This enables automated enumeration of valid accounts for use in credential stuffing or targeted phishing. Only instances that have explicitly enabled the passwordReset option are affected, as it defaults to false. This issue has been fixed in version 4.29.0.
Crypt::SecretBuffer versions before 0.019 for Perl is suseceptible to timing attacks.
For example, if Crypt::SecretBuffer was used to store and compare plaintext passwords, then discrepencies in timing could be used to guess the secret password.
CVE-2026-40194 is a timing discrepancy vulnerability in the phpseclib PHP secure communications library. The issue arises from the use of PHP's != operator to compare SSH packet HMACs, which performs a variable-time memcmp() comparison. This can potentially leak information through timing side channels. The vulnerability affects versions starting from 0.1.1 up to but not including 1.0.28, 2.0.0 up to but not including 2.0.53, and 3.0.0 up to but not including 3.0.51. It has a low CVSS score of 3.7 and is fixed in versions 1.0.28, 2.0.53, and 3.0.51.
Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to 9.8.0-alpha.6 and 8.6.74, he login endpoint response time differs measurably depending on whether the submitted username or email exists in the database. When a user is not found, the server responds immediately. When a user exists but the password is wrong, a bcrypt comparison runs first, adding significant latency. This timing difference allows an unauthenticated attacker to enumerate valid usernames. This vulnerability is fixed in 9.8.0-alpha.6 and 8.6.74.
CVE-2026-33129 is a timing side-channel vulnerability in the h3js framework versions 2.0.1-beta.0 through 2.0.0-rc.8. The flaw exists in the requireBasicAuth function due to unsafe string comparison using ! ==, allowing attackers to measure response times and deduce valid password characters sequentially. This bypasses password complexity protections without requiring authentication or user interaction.
phpseclib versions 0.1.1 through 1.0.26, 2.0.0 through 2.0.51, and 3.0.0 through 3.0.49 are vulnerable to a padding oracle timing attack when using AES in CBC mode. This vulnerability allows an attacker to exploit observable timing discrepancies to potentially decrypt sensitive data. The issue has been fixed in versions 1.0.27, 2.0.52, and 3.0.50.
Observable timing discrepancy in AES-CCM decryption in AWS-LC allows an unauthenticated user to potentially determine authentication tag validity via timing analysis.
The impacted implementations are through the EVP CIPHER API: EVP_aes_128_ccm, EVP_aes_192_ccm, and EVP_aes_256_ccm.
Customers of AWS services do not need to take action. Applications using AWS-LC should upgrade to AWS-LC version 1.69.0.
Observable Timing Discrepancy vulnerability in Apache Shiro.
This issue affects Apache Shiro: from 1.*, 2.* before 2.0.7.
Users are recommended to upgrade to version 2.0.7 or later, which fixes the issue.
Prior to Shiro 2.0.7, code paths for non-existent vs.existing users are different enough,
that a brute-force attack may be able to tell, by timing the requests only, determine if
the request failed because of a non-existent user vs.wrong password.
The most likely attack vector is a local attack only.
Shiro security model https://shiro.apache.org/security-model.html#username_enumeration discusses this as well.
Typically, brute force attack can be mitigated at the infrastructure level.
Trilium Notes is an open-source, cross-platform hierarchical note taking application with focus on building large personal knowledge bases. Prior to 0.101.0, a critical timing attack vulnerability in Trilium's sync authentication endpoint allows unauthenticated remote attackers to recover HMAC authentication hashes byte-by-byte through statistical timing analysis. This enables complete authentication bypass without password knowledge, granting full read/write access to victim's knowledge base. This vulnerability is fixed in 0.101.0.
An issue was discovered in 6.0 before 6.0.2, 5.2 before 5.2.11, and 4.2 before 4.2.28.
The `django.contrib.auth.handlers.modwsgi.check_password()` function for authentication via `mod_wsgi` allows remote attackers to enumerate users via a timing attack.
Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected.
Django would like to thank Stackered for reporting this issue.
Tomahawk auth timing attack due to usage of `strcmp` has been identified in Hiawatha webserver version 11.7 which allows a local attacker to access the management client.
The fix applied in CVE-2025-22228 inadvertently broke the timing attack mitigation implemented in DaoAuthenticationProvider. This can allow attackers to infer valid usernames or other authentication behavior via response-time differences under certain configurations.
CVE-2026-23996 is a timing side-channel vulnerability in the fastapi-api-key library version prior to 1.1.0. The verify_key() function applies a random delay only on verification failures, enabling attackers to statistically distinguish valid API keys by measuring response times. This can facilitate brute-force or enumeration attacks against API keys. The vulnerability impacts confidentiality by revealing valid key existence but does not affect integrity or availability. The issue is fixed in version 1.1.0 by applying uniform random delays to all responses. Mitigations include upgrading to 1.