IntlDateFormatter::parse() misparses ISO datetime string in PHP 8.4 (returns incorrect date)

[marvincaspar]

Preconditions and environment

• Magento version 2.4.8-p3
• PHP 8.4

Steps to reproduce

• Use PHP 8.4
• Use a locale such as de_DE (or other non-ISO locale)
• Call:

$formatter = new \IntlDateFormatter(
    'de_DE',
    \IntlDateFormatter::SHORT,
    \IntlDateFormatter::SHORT,
    'UTC'
);

$timestamp = $formatter->parse('2026-02-10 10:49:38');
var_dump(date('Y-m-d H:i:s', $timestamp));

• Observe incorrect parsed date.

Expected result

2026-02-10 10:49:38

Actual result

2015-08-19 10:49:00

Additional information

I noticed this bug when using the graphql api to get orders (

magento2/app/code/Magento/SalesGraphQl/Model/Formatter/Order.php

Line 51 in 6f286f4

'order_date' => $this->timezone->date($orderModel->getCreatedAt())

). In Magento 2.4.7 it works fine. This is the commit which causes the issue 85ad2c2

---

When running Magento 2 with PHP 8.4, IntlDateFormatter::parse() produces an incorrect timestamp when parsing a valid ISO datetime string (YYYY-MM-DD HH:MM:SS).

Specifically, parsing the string:

2026-02-10 10:49:38

results in a completely incorrect date (e.g. 2015-08-19 10:49:00) instead of the expected 2026-02-10 10:49:38.

The issue appears to originate from this code in:

lib/internal/Magento/Framework/Stdlib/DateTime/Timezone.php (around line 199)

magento2/lib/internal/Magento/Framework/Stdlib/DateTime/Timezone.php

Line 199 in 7ae03a5

$date = $formatter->parse($date) ?: (new \DateTime($date))->getTimestamp();

Magento creates an IntlDateFormatter using SHORT date/time formats without defining an explicit pattern:

$formatter = new \IntlDateFormatter(
    $locale,
    \IntlDateFormatter::SHORT,
    \IntlDateFormatter::SHORT,
    $timezone
);

$timestamp = $formatter->parse($date);

However, the input string is in ISO format (yyyy-MM-dd HH:mm:ss), which does not match the locale-dependent SHORT format.

With PHP 8.4 (likely due to ICU changes), this now results in incorrect but valid timestamps instead of failing cleanly.

Workaround

To fix is quickly I reverted the commit with this patch

diff --git a/Model/Formatter/Order.php b/Model/Formatter/Order.php
index 06afec2ac..409083b6d 100644
--- a/Model/Formatter/Order.php
+++ b/Model/Formatter/Order.php
@@ -48,8 +48,7 @@ class Order
             'id' => base64_encode((string)$orderModel->getEntityId()),
             'increment_id' => $orderModel->getIncrementId(),
             'number' => $orderModel->getIncrementId(),
-            'order_date' => $this->timezone->date($orderModel->getCreatedAt())
-                ->format(DateTime::DATETIME_PHP_FORMAT),
+            'order_date' => $orderModel->getCreatedAt(),
             'order_number' => $orderModel->getIncrementId(),
             'status' => $orderModel->getStatusLabel(),
             'email' => $orderModel->getCustomerEmail(),

Release note

No response

Triage and priority

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @marvincaspar. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce.

• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this
• To learn more about issue processing workflow, refer to the Code Contributions.

---

Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[hostep]

Note that this isn't depending on the PHP version but most likely on the icu package version indeed.
As I can reproduce the same behavior of that snippet in all PHP versions I have installed locally (7.1 => 8.5), and I have icu version 78.2 installed and used by all those PHP versions.

I didn't check Magento's implementation yet, but I can confirm that the code mentioned, got changed between Magento 2.4.7 and 2.4.8

[m2-assistant]

Hi @engcom-Hotel. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
• 5. Add label Issue: Confirmed once verification is complete.
• 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-Hotel]

Hello @marvincaspar,

Thank you for the report and collaboration!

Thank you @hostep for your inputs on this issue.

We have tried to reproduce this issue in the latest development branch i.e. 2.4-develop with PHP 8.5 and the issue is reproducible to us.

Hence confirming the issue.

Thank you for bringing this issue to our attention. If you have a potential solution, we encourage you to submit a pull request. Your contributions significantly enhance Magento Open Source for everyone. Should you need any assistance, please don't hesitate to ask!