{"answers":{"affected":"2 open source packages ship an affected version, including cakephp/queue.","exploited":"There is no known exploitation of CVE-2026-54713 in the wild and no public exploit code.","fix":"Upgrade cakephp/queue to 2.3.1 or later.","what":"CVE-2026-54713 is a low-severity vulnerability in cakephp queue, published on 27 Aug 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-54713 and fix it if it is affected.\n\nWhat it is: CVE-2026-54713 is a low-severity vulnerability in cakephp queue, published on 27 Aug 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-54713 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- cakephp/queue (Packagist): affected from 0.1.10; fixed in 2.3.1\n- cakephp/queue (Packagist): affected from 0.1.10; fixed in 2.3.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-54713/ (Markdown: https://insights.sbomify.com/CVE-2026-54713/index.md)","id":"CVE-2026-54713","markdown":"https://insights.sbomify.com/CVE-2026-54713/index.md","name":"CVE-2026-54713","record":{"aliases":["GHSA-r5pm-vrc5-3m73"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"CakePHP queue library","requires_auth":"none","summary":"An attacker can cause legitimate jobs to be dropped as duplicates by exploiting identifier collisions in the CakePHP Queue library when unique job enforcement is enabled.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":3.7,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-1023","name":"Incomplete Comparison with Missing Factors"}],"description":"CakePHP Queue is a queue-interop compatible queueing library. From 0.1.11 until 2.3.1, QueueManager::getUniqueId() generates identifiers for jobs with shouldBeUnique enabled from the job class, method, and parameters, but sorting parameter values drops associative-array keys. An unauthenticated attacker who can influence job parameters can submit semantically different data that produces the same identifier, resulting in legitimate jobs dropped as duplicate collisions. This issue is fixed in version 2.3.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":"CakePHP Queue: Incomplete Comparison in getUniqueId vulnerable to collisions","id":"CVE-2026-54713","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"business_logic","year":"2026"},"n_packages":2,"n_references":4,"next":{"headline":"Logto: XSS via unescaped RelayState in SAML auto-submit form","id":"CVE-2026-54714"},"packages":[{"ecosystem":"Packagist","fixed":["2.3.1"],"introduced":["0.1.10"],"last_affected":[],"package":"cakephp/queue","purl":null,"source":"GHSA-r5pm-vrc5-3m73"},{"ecosystem":"Packagist","fixed":["2.3.1"],"introduced":["0.1.10"],"last_affected":[],"package":"cakephp/queue","purl":"pkg:composer/cakephp/queue","source":"GHSA-r5pm-vrc5-3m73"}],"prev":{"headline":"OpenTelemetry Javaagent RMI context propagation allows resource exhaustion","id":"CVE-2026-54712"},"products":["queue"],"published":"2026-08-27","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-08-28","vendors":["cakephp"]},"summary":"An attacker can cause legitimate jobs to be dropped as duplicates by exploiting identifier collisions in the CakePHP Queue library when unique job enforcement is enabled.","url":"https://insights.sbomify.com/CVE-2026-54713/"}