{"answers":{"affected":"2 open source packages ship an affected version, including phalcon/cphalcon.","exploited":"There is no known exploitation of CVE-2026-54736 in the wild and no public exploit code.","fix":"Upgrade phalcon/cphalcon to 5.14.1 or later.","what":"CVE-2026-54736 is a high-severity vulnerability in cphalcon, published on 10 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-54736 and fix it if it is affected.\n\nWhat it is: CVE-2026-54736 is a high-severity vulnerability in cphalcon, published on 10 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-54736 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- phalcon/cphalcon (Packagist): affected all versions; fixed in 5.14.1\n- phalcon/cphalcon (Packagist): affected all versions; fixed in 5.14.1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-54736/ (Markdown: https://insights.sbomify.com/CVE-2026-54736/index.md)","id":"CVE-2026-54736","markdown":"https://insights.sbomify.com/CVE-2026-54736/index.md","name":"CVE-2026-54736","record":{"aliases":["GHSA-8jqh-95g6-7jpj"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Phalcon PHP framework","requires_auth":"none","summary":"Attackers can exploit a timing side-channel in Phalcon's decryption to forge valid HMAC tags, allowing tampered encrypted data to be accepted as authentic.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.2,"severity":"high","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"},{"id":"CWE-208","name":"Observable Timing Discrepancy"}],"description":"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.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Phalcon: Non-constant-time HMAC verification in `Encryption\\Crypt::decrypt` (timing side-channel)","id":"CVE-2026-54736","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"other","year":"2026"},"n_packages":2,"n_references":5,"next":{"headline":"@phun-ky/defaults-deep Has a Prototype Pollution issue via Unsafe Recursive Property Merging","id":"CVE-2026-54737"},"packages":[{"ecosystem":"Packagist","fixed":["5.14.1"],"introduced":["0"],"last_affected":[],"package":"phalcon/cphalcon","purl":null,"source":"GHSA-8jqh-95g6-7jpj"},{"ecosystem":"Packagist","fixed":["5.14.1"],"introduced":["0"],"last_affected":[],"package":"phalcon/cphalcon","purl":"pkg:composer/phalcon/cphalcon","source":"GHSA-8jqh-95g6-7jpj"}],"prev":{"headline":"prebid-server's request forgery vulnerability allows for possible host environment data extraction","id":"CVE-2026-54735"},"products":["cphalcon"],"published":"2026-07-10","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-13","vendors":["phalcon"]},"summary":"Attackers can exploit a timing side-channel in Phalcon's decryption to forge valid HMAC tags, allowing tampered encrypted data to be accepted as authentic.","url":"https://insights.sbomify.com/CVE-2026-54736/"}