Skip to content
Fencer Vulns
medium 5.9

CVE-2025-49558 json

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

published 2025-08-12 14 mo ago modified 2026-06-17 4 mo ago also GHSA-wcmw-8xpp-rwfj , EUVD-2025-24449

cvss
5.9
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 39%
public exploits
0
none known

Summary

Adobe Commerce versions 2.4.9-alpha1, 2.4.8-p1, 2.4.7-p6, 2.4.6-p11, 2.4.5-p13, 2.4.4-p14 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 vulnerability by manipulating the timing between the check of a resource's state and its use, allowing unauthorized write access. Exploitation of this issue does not require user interaction.

Patch / fix

  • packagist magento/community-edition 2.4.5-p14, 2.4.6-p12, 2.4.7-p7, 2.4.8-p2, 2.4.9-alpha2
  • adobe commerce 2.4.4
  • adobe commerce_b2b 1.3.3
  • adobe magento 2.4.5

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
14 mo ago

Exploit prediction

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

CVSS scores

assigned by version score vector
CNA 3.1 5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
GitHub 3.1 5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N

Affected packages

ecosystem package affected fixed in
packagist magento/project-community-edition
<=2.0.2
no fix listed
packagist magento/community-edition
>=2.4.9-alpha1, <2.4.9-alpha2
>=2.4.8-beta1, <2.4.8-p2
>=2.4.7-beta1, <2.4.7-p7
>=2.4.6-p1, <2.4.6-p12
<2.4.5-p14
1 listed version
2.4.9-alpha2
2.4.8-p2
2.4.7-p7
2.4.6-p12
2.4.5-p14

Affected products

  • Adobe Adobe Commerce

Classification

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

References

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.