<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Wed, 30 Sep 2026 01:49:15 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-54736</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-54736</link>
      <description>&lt;p&gt;Phalcon is a high-performance, full-stack PHP framework. Prior to 5.14.1, Phalcon\Encryption\Crypt::decrypt compares the attacker-supplied HMAC tag against the freshly computed HMAC using PHP/Zephir identity comparison, which lowers to a byte-wise comparison that returns early on the first differing byte. This observable timing discrepancy can allow an attacker to recover a valid tag byte-by-byte and attach it to a chosen IV and ciphertext so that decrypt() accepts tampered encrypted content as authentic. This issue is fixed in version 5.14.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Phalcon is a high-performance, full-stack PHP framework. Prior to 5.14.1, Phalcon\Encryption\Crypt::decrypt compares the attacker-supplied HMAC tag against the freshly computed HMAC using PHP/Zephir identity comparison, which lowers to a byte-wise comparison that returns early on the first differing byte. This observable timing discrepancy can allow an attacker to recover a valid tag byte-by-byte and attach it to a chosen IV and ciphertext so that decrypt() accepts tampered encrypted content as authentic. This issue is fixed in version 5.14.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-54736</guid>
    </item>
    <item>
      <title>GHSA-8jqh-95g6-7jpj — Phalcon: Non-constant-time HMAC verification in `Encryption\Crypt::decrypt` (timing side-channel)</title>
      <link>https://db.gcve.eu/vuln/ghsa-8jqh-95g6-7jpj</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: phalcon/cphalcon&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;`Phalcon\Encryption\Crypt` provides authenticated encryption: when `useSigning` is enabled (the default), `encrypt()` appends an HMAC tag and `decrypt()` verifies it before returning the plaintext. The verification compares the attacker-supplied tag against the freshly computed HMAC using PHP/Zephir identity comparison (`!==`), which the Zephir compiler lowers to `!ZEPHIR_IS_IDENTICAL(...)` — a byte-wise `memcmp` that returns early on the first differing byte. The comparison time therefore depends on how many leading bytes of the supplied tag are correct, a classic MAC-verification timing side-channel. Every other secret/MAC comparison in the framework uses the constant-time `hash_equals()` (`zephir_hash_equals`) — the CSRF token check (`Security::checkToken`) and the JWT signature check (`Signer\Hmac::verify`); `Crypt::decrypt` is the lone deviation.&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;### Vulnerable code&lt;/p&gt;
&lt;p&gt;`phalcon/Encryption/Crypt.zep:246` (Zephir source):&lt;/p&gt;
&lt;p&gt;```zephir
if true === this-&amp;gt;useSigning {
    // Checks on the decrypted message digest using the HMAC method.
    if digest !== hash_hmac(hashAlgorithm, padded, decryptKey, true) {
        throw new Mismatch(&amp;#34;Hash does not match.&amp;#34;);
    }
}
```&lt;/p&gt;
&lt;p&gt;Generated C --&amp;gt; `ext/phalcon/encryption/crypt.zep.c:364-367`:&lt;/p&gt;
&lt;p&gt;```c
ZEPHIR_CALL_FUNCTION(&amp;amp;_8$$7, &amp;#34;hash_hmac&amp;#34;, NULL, 245, &amp;amp;hashAlgorithm, &amp;amp;padded, &amp;amp;decryptKey, &amp;amp;__$true);
...
if (!ZEPHIR_IS_IDENTICAL(&amp;amp;digest, &amp;amp;_8$$7)) {                 // &amp;lt;-- non-constant-time
    ZEPHIR_THROW_EXCEPTION_DEB…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: phalcon/cphalcon&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;`Phalcon\Encryption\Crypt` provides authenticated encryption: when `useSigning` is enabled (the default), `encrypt()` appends an HMAC tag and `decrypt()` verifies it before returning the plaintext. The verification compares the attacker-supplied tag against the freshly computed HMAC using PHP/Zephir identity comparison (`!==`), which the Zephir compiler lowers to `!ZEPHIR_IS_IDENTICAL(...)` — a byte-wise `memcmp` that returns early on the first differing byte. The comparison time therefore depends on how many leading bytes of the supplied tag are correct, a classic MAC-verification timing side-channel. Every other secret/MAC comparison in the framework uses the constant-time `hash_equals()` (`zephir_hash_equals`) — the CSRF token check (`Security::checkToken`) and the JWT signature check (`Signer\Hmac::verify`); `Crypt::decrypt` is the lone deviation.&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;### Vulnerable code&lt;/p&gt;
&lt;p&gt;`phalcon/Encryption/Crypt.zep:246` (Zephir source):&lt;/p&gt;
&lt;p&gt;```zephir
if true === this-&amp;gt;useSigning {
    // Checks on the decrypted message digest using the HMAC method.
    if digest !== hash_hmac(hashAlgorithm, padded, decryptKey, true) {
        throw new Mismatch(&amp;#34;Hash does not match.&amp;#34;);
    }
}
```&lt;/p&gt;
&lt;p&gt;Generated C --&amp;gt; `ext/phalcon/encryption/crypt.zep.c:364-367`:&lt;/p&gt;
&lt;p&gt;```c
ZEPHIR_CALL_FUNCTION(&amp;amp;_8$$7, &amp;#34;hash_hmac&amp;#34;, NULL, 245, &amp;amp;hashAlgorithm, &amp;amp;padded, &amp;amp;decryptKey, &amp;amp;__$true);
...
if (!ZEPHIR_IS_IDENTICAL(&amp;amp;digest, &amp;amp;_8$$7)) {                 // &amp;lt;-- non-constant-time
    ZEPHIR_THROW_EXCEPTION_DEB…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-8jqh-95g6-7jpj</guid>
    </item>
  </channel>
</rss>
