CVE-2026-5419
A flaw was found in gnutls. The PKCS#7 padding check, performed during decryption, was not constant-time. This timing side-channel could all
CVSS
3.7
Low
EPSS
0.4%
p32
KEV
—
Exploit Today
10
0-100
Published: Jun 1, 2026 · Last modified: Sep 1, 2026 · CWE-208
0.4%EPSS · 30 days0.4%
2026-08-232026-09-20
A flaw was found in gnutls. The PKCS#7 padding check, performed during decryption, was not constant-time. This timing side-channel could allow a remote attacker to potentially leak sensitive information about the padding bytes through observable timing differences. This vulnerability is a form of information disclosure.
- access.redhat.comhttps://access.redhat.com/errata/RHSA-2026:13274
- access.redhat.comhttps://access.redhat.com/errata/RHSA-2026:20612
- access.redhat.comhttps://access.redhat.com/errata/RHSA-2026:20613
- access.redhat.comhttps://access.redhat.com/errata/RHSA-2026:26319
- access.redhat.comhttps://access.redhat.com/errata/RHSA-2026:26409
- access.redhat.comhttps://access.redhat.com/errata/RHSA-2026:29197
- access.redhat.comhttps://access.redhat.com/errata/RHSA-2026:30004
- access.redhat.comhttps://access.redhat.com/errata/RHSA-2026:32962
- access.redhat.comhttps://access.redhat.com/errata/RHSA-2026:58981
- access.redhat.comhttps://access.redhat.com/security/cve/CVE-2026-5419
- bugzilla.redhat.comhttps://bugzilla.redhat.com/show_bug.cgi?id=2467686
- www.gnutls.orghttps://www.gnutls.org/security-new.html#GNUTLS-SA-2026-04-29-13
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2026-706587.4 HIG41.9%
——13Pay is a payments engine for Ruby on Rails 6.0 and higher. Prior to 11.6.2, Pay::Webhooks::PaddleBillingController#valid_signature? in app/controllers/pay/webhooks/paddle_billing_controller.rb compares the computed 64-character SHA-256 HMAC with the attacker-controlled h1 token from the Paddle-Signature header using Ruby String#==. An unauthenticated remote attacker who can repeatedly submit requests to /pay/webhooks/paddle_billing and obtain sufficiently precise timing measurements can infer matching digest prefixes and recover a valid signature. A forged accepted webhook is enqueued through Pay::Webhooks::ProcessJob and can cause a host application to update billing state, provision paid features, record refunds, or trigger customer notifications. This issue is fixed in version 11.6.2.7dCVE-2023-240353.5 LOW54.0%
——16An issue was discovered in Nagios XI before 5.9.3. The is_insecure_login_authenticated function uses a insecure timing comparison that leads to an attacker being able to bruteforce the admin password, by measuring timing differences in the comparison.5dCVE-2026-877375.9 MED11.8%
——4An issue was discovered in the mirage-crypto-ec package before 2.4.0 for OCaml. There is a timing side channel for NIST elliptic-curve scalar multiplication: the time required for a lookup can depend on a secret.12dCVE-2026-160377.5 HIG23.2%
——7Observable timing discrepancy vulnerability in PayTR Payment and Electronic Money Institution Inc. PayTR Virtual Pos iFrame API (v9x) WHMCS Module allows Black Box Reverse Engineering.
This issue affects PayTR Virtual Pos iFrame API (v9x) WHMCS Module: from v9.0.0 before v9.0.3.13dCVE-2026-811593.7 LOW17.5%
——5Observable Timing Discrepancy vulnerability in Drupal Commerce CyberSource allows Brute Force. This issue affects Commerce CyberSource versions: from 0.0.0 to 1.10.0.5dCVE-2026-843086.3 MED11.8%
——4phpseclib is a PHP secure communications library. Prior to 3.0.57 and 4.0.1, pure-PHP X25519 scalar multiplication in phpseclib/Math/PrimeField/Integer.php performs data-dependent conditional modular reductions in add() and subtract(). During the Montgomery ladder in phpseclib/Crypt/EC/BaseCurves/Montgomery.php, the reduction behavior of each step depends on the secret scalar prefix, creating per-step timing and libgmp call-count observations that can reveal a reused 251-bit clamped private scalar. The phpseclib/Crypt/EC/Formats/Keys/MontgomeryPrivate.php derivation path invokes the pure-PHP multiplication without a native-engine check, while phpseclib/Crypt/EC/Formats/Keys/PKCS8.php reaches it when ext-sodium is unavailable. Exploitation requires a reused or long-lived X25519 private key, knowledge of the corresponding public key, execution of the pure-PHP path, and a local observer capable of resolving individual ladder steps or libgmp entry-point calls. Ephemeral X25519 keys, including phpseclib's normal SSH exchange path, are not affected. Recovery of the scalar permanently compromises operations that reuse that key. This issue is fixed in versions 3.0.57 and 4.0.1.18d