Adobe Commerce | Time-of-check Time-of-use (TOCTOU) Race Condition (CWE-367)

published 2025-02-11 20 mo ago modified 2026-06-17 4 mo ago also GHSA-6w27-c66f-gvhq , EUVD-2025-3711

cvss: 3.7; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.4%; EPSS 0.4% chance of exploitation in 30 days, percentile 34%
public exploits: 0; none known

Adobe Commerce versions 2.4.8-beta1, 2.4.7-p3, 2.4.6-p8, 2.4.5-p10, 2.4.4-p11 and earlier are affected by a Time-of-check Time-of-use (TOCTOU) Race Condition vulnerability that could result in a security feature bypass. An attacker could exploit this race condition to alter a condition after it has been checked but before it is used, potentially bypassing rate limiting mechanisms. Exploitation of this issue does not require user interaction.

Patch / fix

fixed in 4

packagist magento/community-edition 2.4.4-p12, 2.4.5-p11, 2.4.6-p9, 2.4.7-p4
adobe commerce 2.4.4
adobe commerce_b2b 1.3.3
adobe magento 2.4.4

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: partial
Assessed: 20 mo ago (2025-02-11)

Exploit prediction

0.40% chance of exploitation in the next 30 days, higher than 34% of all scored CVEs (FIRST EPSS, 2026-11-08).

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:L/A:N
NVD	3.1	3.7	CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
GitHub	3.1	3.7	CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N

Affected packages

ecosystem	package	affected	fixed in
packagist	magento/community-edition	>=2.4.7-beta1, <2.4.7-p4 >=2.4.6-p1, <2.4.6-p9 >=2.4.5-p1, <2.4.5-p11 <2.4.4-p12 1 listed version	2.4.7-p4 2.4.6-p9 2.4.5-p11 2.4.4-p12
packagist	magento/project-community-edition	<=2.0.2	no fix listed

Affected products

Adobe Adobe Commerce

Classification

Weakness

CWE-367 Time-of-check Time-of-use (TOCTOU) Race Condition

References

helpx.adobe.com /security/products/magento/apsb25-08.html
vendor-advisory, web
nvd.nist.gov /vuln/detail/CVE-2025-24430
advisory
github.com /magento/magento2
package

Sources

Fencer Vulns 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.

Summary