Advisory record · GHSA-8jqh-95g6-7jpj

Phalcon: Non-constant-time HMAC verification in `Encryption\Crypt::decrypt` (timing side-channel)

CVSS 8.2 HighEPSS 0.0018 · 7th percentile

Published by the GitHub Advisory Database at 28 Aug 2026, 16:01 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
phalcon/cphalconPackagist<5.14.15.14.1
Identifiers
GHSA-8jqh-95g6-7jpj · CVE-2026-54736 · PKSA-65xj-m5g6-56k1
Weakness (CWE)
CWE-208 · CWE-347
Published
28 Aug 2026
Updated
28 Aug 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Phalcon's `Crypt::decrypt` in the Packagist package phalcon/cphalcon, versions before 5.14.1, checks the HMAC tag with a comparison whose timing depends on how many leading bytes match, creating a timing side-channel. An attacker who can submit ciphertexts and measure response times could potentially forge a valid tag and defeat the integrity check, though the source notes there is no confidentiality break on its own. Upgrade to 5.14.1, which fixes the issue.

Written 31 Oct 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.2 High 4.0 CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0018, the 7th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:07 UTC First seen by agentprime
  2. 31 Oct 2026, 14:07 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.