The Drupal-specific identifier for the issue is SA-CORE-2018-002. Patches for Drupal 7.x and 8.3.x, 8.4.x, 8.5.x and 8.6.x will be provided. Your site's update report page will recommend the 8.5.x release even if you are on 8.3.x or 8.4.x, but temporarily updating to the provided backport for your site's current version will ensure you can update quickly without the possible side effects of a minor version update.

The security advisory will list the appropriate version numbers for all three Drupal 8 branches. Sites on 7.x or 8.5.x can immediately update when the advisory is released using the normal procedure.Sites on 8.4.x should immediately update to the 8.4.x release that will be provided in the advisory, and then plan to update to the latest 8.5.x security release in the next month.Sites on 8.3.x should immediately update to the 8.3.x release that will be provided in the advisory, and then plan to update to the latest 8.5.x security release in the next month.The Drupal security team strongly recommends the following: While Drupal 8.3.x and 8.4.x are no longer supported and we don't normally provide security releases for unsupported minor releases, given the potential severity of this issue, we are providing 8.3.x and 8.4.x releases that include the fix for sites which have not yet had a chance to update to 8.5.0. Security release announcements will appear on the security advisory page.

The Drupal Security Team urges you to reserve time for core updates at that time because exploits might be developed within hours or days.

There will be a security release of Drupal 7.x, 8.3.x, 8.4.x, and 8.5.x on March 28th 2018 between 18:00 - 19:30 UTC, one week from the publication of this document, that will fix a highly critical security vulnerability.

Pes 7 actualizar 2018