CVE-2026-54736
Timing attack in Phalcon Crypt::decrypt lets attackers forge HMAC and bypass integrity.
Is CVE-2026-54736 being exploited?
Not confirmed. CVE-2026-54736 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.18% probability of exploitation in the next 30 days.
How severe is CVE-2026-54736?
CVE-2026-54736 is rated High with a CVSS score of 8.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-54736?
Yes. A fix has been recorded for CVE-2026-54736. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-54736 affect?
CVE-2026-54736 affects Phalcon PHP framework < 5.14.1, Applications using Phalcon\Encryption\Crypt::decrypt. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-54736?
Upgrade Phalcon to 5.14.1; rotate keys if exposed; audit crypt usage.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Timing side-channel allows recovery of HMAC bytes, enabling attackers to forge valid ciphertext and bypass integrity checks on encrypted data.
Patch when possible
- affected< 5.14.1
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.