cakephp/queue's Incomplete Comparison in getUniqueId vulnerable to collisions (CVE-2026-54713) | HOL Guard CVE

Low · CVSS 3.7CVE-2026-54713GHSA-R5PM-VRC5-3M73

cakephp/queue's Incomplete Comparison in getUniqueId vulnerable to collisions

Answer in brief

CVE-2026-54713 records a Low severity (CVSS 3.7) vulnerability in cakephp/queue's Incomplete Comparison in getUniqueId vulnerable to collisions. The current sources do not mark it as known exploited. The current feed maps cakephp/queue (composer). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Aug 27, 2026Updated Aug 27, 2026Source checked Aug 27, 2026First seen by HOL Aug 27, 2026Material review Aug 27, 2026

Upstream Advisory

Key facts

Risk: Low · CVSS 3.7
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

CVSS is 3.7. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps cakephp/queue (composer). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
cakephp/queuecomposer	>=0.1.10,<2.3.1	2.3.1

Recommended response

Check inventory. Check lockfiles and deployed manifests for cakephp/queue.
Review the reported fix. Update cakephp/queue to 2.3.1 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Aug 27, 2026
Evidence: source:ghsa:source_dates:source-dates:record
Source modified
Aug 27, 2026
Evidence: source:ghsa:source_dates:source-dates:record
First seen by HOL
Aug 27, 2026

Sources and claim methodology

Upstream source description

### Impact For jobs with `shouldBeUnique = true` the queue plugin will generate a 'unique identifier' based on the job class, method and parameters. If user data is supplied, a malicious user could create collisions, resulting in legitimate jobs being dropped. ### Patches Upgrade to 2.3.1 ### Workarounds You can disable `shouldBeUnique` and handle idempotency in application code.

Quoted source text, attributed separately from HOL analysis.