CVE-2026-54713 json
CakePHP Queue: Incomplete Comparison in getUniqueId vulnerable to collisions
published 2mo ago modified 2mo ago also GHSA-r5pm-vrc5-3m73 , EUVD-2026-67241
- cvss
- 3.7
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 40%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- packagist cakephp/queue 2.3.1
- github.com/cakephp/queue@1389059 commit
- github.com/cakephp/queue#188 pull request
- github.com/cakephp/queue/releases/tag/2.3.1 release
Is CVE-2026-54713 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2mo ago
Exploit prediction
0.46% chance of exploitation in the next 30 days, higher than 40% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 3.7 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L |
| GitHub | 3.1 | 3.7 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | cakephp/queue | >=0.1.10, <2.3.1 |
2.3.1 |
Affected products
- cakephp queue
Classification
- Weakness
-
- CWE-1023 Incomplete Comparison with Missing Factors
References
Sources
- CVE List CVE-2026-54713
- GitHub Advisory GHSA-r5pm-vrc5-3m73
- NVD CVE-2026-54713
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.