Proactive insights, news and tips from Oracle Fusion Middleware Support. Learn Oracle from Oracle.

Oracle Critical Patch Update for July 2018 is Released

   The Critical Patch Update for July 2018 has been released. Oracle strongly recommends applying the patches as soon as possible.
      The Critical Patch Update Advisory is the starting point for finding relevant information. It includes the list of products affected, pointers to obtain the patches, a summary of the security vulnerabilities for each product suite, and links to other important documents. Supported products that are not listed in the "Affected Products and Components" section of the advisory do not require new patches to be applied.

      It is also essential to review the Critical Patch Update supporting documentation referenced in this Advisory before applying patches, as this is where you can find important pertinent information.

      More information about Critical Patch Update Advisories are available at the following location:

Oracle Critical Patch Update Advisory - July 2018- Oracle Technology Network:
Critical Patch Updates, Security Alerts and Bulletins - Oracle Technology Network:
► Oracle Knowledge Management Document - July 2018 Critical Patch Update: Executive Summary and Analysis (Doc ID 2383583.1)
Important information can also be found at: https://blogs.oracle.com/security/

The next four dates for Critical Patch Updates are as follow:

  • 16 October 2018
  • 15 January 2019
  • 16 April 2019
  • 16 July 2019

Related Articles:


Join the discussion

Comments ( 2 )
  • loganathan Friday, August 17, 2018

    I am not able to find patch number. Please provide me the patch number.
  • Alan Monday, August 20, 2018

    The July 2018 Oracle Fusion Middleware Critical Patch Updates can be found here:
    https://support.oracle.com/rs?type=doc&id=2394520.1 under 3.3 Oracle Fusion Middleware.

    Kind Regards,
    Alan Boucher - Oracle
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.