Adobe Experience Manager 6.5 Latest Service Pack Release Notes

Last update: March 26, 2025

CREATED FOR:

  • User
  • Admin
  • Developer

Release information

ProductAdobe Experience Manager 6.5
Version6.5.22.0
TypeService Pack release
DateThursday, November 21, 2024
Download URLSoftware Distribution

What is included in Experience Manager 6.5.22.0

Experience Manager 6.5.22.0 includes new features, key customer-requested enhancements, and bug fixes. It also includes performance, stability, and security improvements released since the initial availability of 6.5 in April 2019. Install this Service Pack on Experience Manager 6.5.

Key features and enhancements

Forms

Key features and enhancements in this release include the following:

New GA features in AEM Forms

  • Added support to enable font embedding in Interactive Communications Batch APIs - Interactive Communications now includes support for embedding Adobe Ming and Adobe Myungjo fonts in PDFs generated through the Batch API. This enhancement ensures accurate text rendering in generated documents, even when using font subsets, providing improved support for multilingual content in PDF outputs.

  • Table of Content API for PDF Accessibility - AEM Forms on OSGi now support the new TOC Tag API to enhance PDF for accessibility standards. It makes PDFs more accessible for users with assistive technology.

  • Fragment XDP resolution - AEM Forms on OSGi now resolves Fragment XDPs referenced in Primary XDPs and stored in the AEM CRX Repository.

  • PDF/A compliance enhancements - Now users can convert PDFs to PDF/A formats (1a, 2a, 3a) for archival purposes while ensuring accessibility and verifying compliance with these standards.

  • Support for Auto Sizing of Font for Static PDF documents - AEM Forms Designer, OutputService, and FormsService now supports auto sizing of fonts for static PDFs. If the user sets the font size 0 for text, numeric, password, or datetime fields, the font size auto-adjusts within these fields without altering the field’s overall size. To use the feature, users pass a flag in the custom XCI: <behaviorOverride>patch-LC-3921991:1</behaviorOverride>.

New Beta features in AEM Forms

The beta feature offers a unique opportunity to you to get exclusive access to cutting-edge innovations, and help shape their development. Interested in enabling a beta feature for your environments? Send an email from your official address to aem-forms-ea@adobe.com with the list of capabilities that you are interested in.

  • hCaptcha and Cloudflare Turnstile CAPTCHA services: AEM Forms support the following Captcha services:

    • hCaptcha protects forms from bots, spam, and automated abuse by challenging users with a checkbox widget. It ensures that only human users proceed, enhancing security for online transactions.
    • Cloudflare Turnstile offers a security measure that aims to protect forms from automated bots, malicious attacks, spams and unwanted automated traffic. It presents a checkbox on form submission to verify that they are human, before allowing them to submit the form.

  • Adaptive Form versioning:

    • Create multiple versions of an Adaptive Form - Now users can easily manage variations of existing forms. This process simplifies version control and facilitates comparison for form optimization, all within a single, streamlined workflow.
    • Compare Adaptive Forms: Now users can easily compare two forms to identify differences. It facilitates smooth collaboration by enabling team members to compare revisions and discuss changes efficiently.

Sites

The Universal Editor is now available on AEM 6.5 for headless use cases with the application of a feature pack.

Assets

The IPTC tab now supports Alt Text and Extended Description text fields. (ASSETS-34918)

Fixed issues in Service Pack 22

Sites

Accessibility

  • Annotation swatch selector button was missing an accessible name. That is, using a screen reader, there is no human-understandable name for the button to select after entering a new hex value. (SITES-11992)

  • The following elements in the left rail menu appear like a list but are not marked up as such in the screen reader:

    • Site
    • Live copy
    • Launch
    • Language Copy
    • Folder
    • CSV Report (SITES-2874)

  • The AEM Core Web Content Management requires an accessibility label for hyperlinks in the Rich Text Editor. When a hyperlink is used in the text component, the anchor tag should include the aria-label attribute to ensure that screen readers can read and convey the link text accurately for accessibility purposes. (SITES-11511)

  • In AEM, interactive elements in the table header in List View do not have the required “button” role. As such, the NVDA screen reader does not announce the expected button roles for the following table headers: Title, Name, Modified, Published, Preview, Template, Operation, Workflow. Each interactive element in the table header should be assigned a “button” role to ensure compatibility with assistive technologies like NVDA. (SITES-10962)

Admin User Interface

  • In some instances of AEM, the version preview and comparison functionalities were not working as expected across several pages. Specifically:

    • Preview Issue: When attempting to preview a page version, an error appears initially. After retrying, the preview results in a blank page.
    • Version Comparison Issue: The “Compare to Current” feature only displayed the current version, without highlighting any differences between versions. (SITES-23988)

  • An unexpected <br> tag appears in the Rich Text Editor (RTE) field when using the defaultPasteMode set to plaintext during a copy and paste action. This issue results in different markup for the same content, resulting in the same text content being translated twice in a customer’s translation memory. (SITES-23606)

  • In AEM 6.5.20.0, a functionality issue was encountered with the Manage Publication feature. When selecting a node and scheduling it for future publication, an error message – “Failed to retrieve child resources for selected items” – could appear when trying to include child nodes. This issue was blocking the use of the Include Children option, preventing complete publication of the intended content hierarchy. (SITES-23000)

  • A template’s “Published” timestamp was not updating in the author environment, even though the template was successfully replicated to the publish instances. The expected behavior was for the timestamp on the author instance to reflect the latest publication, but this update was not occurring as intended. (SITES-21585)

  • There was a discrepancy in the count of Incoming Links in the AEM author environment. The left side rail showed fewer links compared to the Classic UI. Also, some Incoming Links that were legitimate, do not work. (SITES-24837)

  • Extremely long loading times were being reported when viewing page versions in the Timeline view of AEM. It was taking up to 19 minutes to display versions. This issue was ongoing since the upgrade from AEM 6.4.8 to 6.5.18, significantly disrupting workflow efficiency. (SITES-22468 & SITES-22467)

Content Fragments

  • In the upgraded AEM 6.5.17, saving Content Fragments resulted in the following error: ERROR: Could not save Content Fragment. (SITES-22993)
  • An issue was identified with an unclosed resource resolver in ContentFragmentModelOmniSearchHandler on the publisher in AEM. (SITES-24903)

Content Fragments - Admin

Clicking the link in the email notification directs the user to the default asset viewer or editor. It does so instead of the Content Fragment editor, even when the asset in the workflow is determined to be a Content Fragment. (SITES-24338)

Content Fragments - GraphQL API

When using Content Fragments with Multiline Text field items, the markup generated when querying using GraphQL was not retaining the formatting as specified in the HTML. For example, a newline was missing after the list. The impact was that the last paragraph became part of the list. (SITES-23233)

Core Backend

  • Recurring SegmentNotFoundException errors was reported on an AEM author instance. Restarting the author temporarily resolved the issue but a long-term fix was needed to prevent further occurrences. (SITES-22573)
  • An issue was raised regarding the timeline functionality in AEM Sites, specifically around handling missing cq:lastModified properties on annotations. After applying AEM 6.5.20, there was uncertainty about whether existing content needed remediation for the missing property, or if the timeline was updated to function correctly without it. (SITES-21861)

Core Components

  • Following an upgrade from AEM 6.5.18 to 6.5.21, an issue was identified with the functionality that checks the live usage of components. When attempting to scroll for additional items on the Live Usage page, the table failed to load more results even though “Loading more items” was seen in the UI. (SITES-23919)
  • An issue was reported with the validation of required fields in an AEM component dialog box containing two tabs. Tab 1 included a Rich Text Editor (RTE) and text fields, while Tab 2 had path fields and text fields. Although all fields are marked as mandatory (required=true), error notifications persist incorrectly in Tab 1, even after filling in all required fields. In contrast, errors in Tab 2 cleared as expected. (SITES-23243)
  • After migrating to AEM 6.5.21, the HTML Template Language data-sly-include statement no longer functioned as expected, specifically failing to support appendPath and prependPath expressions. As a result, the included resource’s output was not rendered properly, even though it worked correctly prior to the migration. This issue caused rendering failures for resources that rely on these expressions for path manipulation. (GRANITE-52970)

Experience Fragments

  • Experience Fragments do not sort by title as expected when the Title column header is clicked in the List View. A quick flicker of the screen is observed, but it does not sort. (SITES-23706)

  • In AEM 6.5.17, an issue was encountered when converting a page component into an Experience Fragment using the out-of-the-box feature. After conversion, the Experience Fragment appeared empty during editing, despite displaying correctly on the page where it was used. The issue stemmed from incorrect node creation: the component node was placed outside the root/container node, violating the template’s structure. You needed to move the component node manually into the correct root/container node to restore the fragment’s editability. (SITES-22974)

  • After migrating from AEM 6.5.11 to 6.5.20, Cloud configurations on Experience Fragments were not saving correctly. Although the configurations appeared to save in crx/de, they would not display upon reopening the configurations console, indicating an issue with persistence. (SITES-22287)

Launches

When adding Experience Fragment assets using the tagging filter in AEM production, the user could select it, but then encountered an error after selecting Create language copy. The expected behavior was that the Experience Fragment asset selected from the tagging filter was supposed to get added to the translation project. (SITES-24152)

The LinkCheckerTask fails to authenticate because the HTTP client tries NTLM before Basic Authentication, causing the proxy to block users after multiple failed attempts. The system should instead use Basic Authentication to authenticate against the proxy, allowing the LinkCheckerTask services to function correctly. (SITES-25034)

MSM - Live Copies

  • When SEO Robots tags are applied to the primary copy and rolled out to Live Copy pages, the values appeared correctly in crx/de. However, the values were not reflected in the user interface under the Page Properties of the Live Copy pages. (SITES-23475)
  • Errors related to Launches were appearing when an attempt was made to promote a Launch through the user interface. The Promote Launch wizard remained empty, preventing the completion of the promotion process. (SITES-19718)
  • Issues arose with Experience Fragments in AEM following attempts to create Live Copies and perform rollouts. The problem occurred when users encountered a NotFound error when trying to navigate back to the Experience Fragments management screen from the Rollout screen. (SITES-21933)

Page Editor

  • The Undo button changed the position of the component in addition to changing the text to the last version. (SITES-17465)
  • When a copied container component was pasted, it visually appeared twice, resulting in three instances on the page. However, after refreshing the page, the duplicate disappeared, suggesting the issue was likely a temporary visual glitch. (SITES-21890)
  • While navigating the Components left pane using the keyboard’s Tab or Shift+Tab keys, multiple text elements were not clearly visible, both visually and in tab mode. This issue affected accessibility, making it difficult to identify or interact with these components during keyboard navigation. (SITES-2266)

Replication

In AEM 6.5.18 and 6.5.19, on deactivating a parent page, multiple deactivation requests were generated for each child page. This issue also broke the bulk unpublishing of the GraphQL endpoints. (NPR-42075 & NPR42010)

Assets

  • While using the Connected Assets feature, the updates made in AEM Assets do not reflect on AEM Sites environment. (ASSETS-42344)
  • Issues with the asset publish status when you move assets from one location to another within Experience Manager. (ASSETS-41158)
  • Uploading assets using the API results in unclosed resource resolver error message. (ASSETS-41049)
  • Issues with AssetReferenceResolverImpl reference query after upgrading to Adobe Experience Manager, Service Pack 21. (ASSETS-40384)
  • In AEM version 6.5.19, while removing one option from the search panel results, it unchecks all other available checkboxes as well. (ASSETS-37335)
  • Junk values are displayed in the Excel output while performing the bulk metadata export operation. (ASSETS-37260)
  • In AEM version 6.5.19, when you upload an SVG file in UTF-8 format, the output is blurred. (ASSETS-36616)
  • Fetch original rendition for Dynamic Media Connected Assets option is missing within Connected Assets configuration. (ASSETS-41726)
  • Asset properties are saved even if you do not define a value for mandatory fields. (ASSETS-37914)
  • If the processing status of an asset is Failed or Metadata Failed, the captions and audio tracks UI does not work appropriately. (ASSETS-37281)
  • When you save an asset metadata and try to edit it, the language name does not display. (ASSETS-37281)

Dynamic Media

A production issue disrupted the migration process when a video upload to Dynamic Media failed, displaying a process failure error in the user interface. (ASSETS-36038)

Forms

  • The URLs generated for file attachments in saved drafts in AEM Forms do not reflect the configured Apache Sling Resource Resolver Factory mappings. (FORMS-16949)

  • When a user on AEM Forms Service Pack 19 (6.5.19.0) previews a letter, the content does not align properly, as the spaces appear missing and the character x appears at some locations. (FORMS-16670)

  • When a user on AEM Forms Service Pack 18 (6.5.18.0), attempts to print the files using CIFS protocol, it fails with the error: (FORMS-16629)
    ALC-OUT-001-401: Unknown error while printing using CIFS on the Printer: \\\\\\\\NSMVPLUETEST01\\\\TH_Test.

  • When a user upgrades from AEM Forms Service Pack 17 (6.5.17.0) to AEM Forms Service Pack 20 (6.5.20.0), the Rule Editor icon does not appear at the Form Container level. (FORMS-16430)

  • When a user upgrades from AEM Forms Service Pack 17 (6.5.17.0) to AEM Forms Service Pack 21 (6.5.21.0), the modified adaptive form submit URL Path fails to work. (FORMS15894)

  • On AEM Forms Service Pack 19 (6.5.19.0), AEM Forms 6.5 PDF/A validation fails for certain files with the error creation date and modification date mismatch with timezone, while it runs smoothly on Acrobat Pro PDF/A validation for a compliance check. (FORMS-15840)

  • When a user deletes form drafts using “Drafts and Submissions” component on a site page on AEM Forms Service Pack 15 (6.5.15.0) on OSGi, deletion fails. (FORMS-15755)

  • When a user has a SharePoint list with more than 999 entries and the form includes an attachment, the form submission fails. (FORMS-15057)

  • A validation rule is added to ensure that the End Date is not earlier than the Start Date, along with a custom script for the validation message. However, the validation does not trigger when the End Date is earlier than the Start Date. (FORMS-14757)

  • When a user employs the show/hide functionality on a table in an adaptive form, the field size shrinks. The field size corrects itself on adding and removing a row. (FORMS-14756)

  • When a user print forms on AEM Forms Service Pack 19 (6.5.19.0), some forms do not render correctly on the server, causing errors during the printing process. (FORMS14734)

  • When a user updates from AEM Forms Service Pack 15 (6.5.15.0) to Service Pack 19 (6.5.19.0), an issue occurs. A custom display pattern set as num{$zzz,zz9.99} does not render correctly in preview and Agent UI. (FORMS-14694)

  • When a user previews a letter in an Interactive Communication with a saved data xml, the letter becomes stuck in the “Loading” state on AEM UI. Previewing the letter again with the same XML works fine. (FORMS-14521)

  • In AEM Forms Service Pack 20 (6.5.20.0), users sending emails with attachments using the ‘Send Email’ button in adaptive forms notice an issue. The attachment name appears on the next line instead of inline. (FORMS-14426)

  • When a user generates a PDF in AEM Forms with bulleted lists set to the default “Disc” style, the PDF fails the Accessibility Check in Adobe Acrobat’s accessibility tool. List with ‘Bullet’ and ‘Square’ styles pass the Accessibility Check. (FORMS-13802, LC-3922179)

  • When a user upgrades from AEMForms-6.5.0-0065 to AEMForms-6.5.0-0087 on Standalone RHEL8 JBoss® setup, it fails to connect with the LiveCycle service container. (FORMS-15907) *

  • On AEM Forms on JEE, in AEM Workspace, selecting a previously submitted form to start a new form process causes an issue. Forms with prepopulated data overwrite all previously submitted data, removing manually filled fields. (FORMS-15376)

  • On AEM Forms Service Pack 20 (6.5.20.0) when a user converts Tiff file to PDF using PDFG service, it fails with the error: (FORMS-14879) ALC-PDG-011-028-Error occurred while converting the input image file to PDF. com/sun/image/codec/jpeg/JPEGCodec

  • Upgrade in AEM Forms on JEE jar files: The commons-collections:commons-collections:jar library is now included to improve dependency resolution and functionality across various AEM Forms JEE job such as:

    • Assembler Job enhancement to improve job processing and error handling.
    • PDF Generator (PDFG) Job enhancement to ensure smoother operations for document generation and conversion.
    • LC-Upgrade Job enhancement to improve the upgrade process while ensuring a stable transition between versions.
    • Rights Management Job enhancement to secure document handling and improved Rights Management capabilities.
    • Process Management Job enhancement for more reliable job processing and system management.

  • Starting AEM Forms OSGi 6.5.22, the renderPDFForm operation of Forms service will not execute client-only (runAt=client) scripts on the server, only those marked runAt=server or runAt=both will be executed as described in the table below. (FORMS-16564)

    Script marked runAtExecuted on the server
    serveryes
    bothyes
    clientno

XMLFM

  • In AEM Forms Service Pack 21 (6.5.21.0) when a user adds non-standard tags to PDFs using XMLFM, the document fails to comply with PDF specification requirements. (LC-3922484)
  • When a user generates a PDF using the Output Service on AEM Forms Service Pack 20 (6.5.20.0), it fails with CORBA.COMM_FAILURE and displays the error: 15:04:35,973 ERROR [com.adobe.formServer.PA.XMLFormAgentWrapper] (default task-14) ALCOUT-002-013: XMLFormFactory, PAexecute failure: "org.omg.CORBA.COMM_FAILURE". The service passes successfully when the Accessibility role “Reference” is excluded from the XDP template’s subform. however, this role is needed for 508 compliance. (LC-3922402)
  • When a user converts an XFA form to an AcroForm PDF, it fails. (LC-3922363)
  • In AEM Forms Service Pack 19 (6.5.19.0) when a user creates an XDP with the unnamed subforms, FS_DATA_SOM appears empty for unnamed subforms. (LC-3922034)

Forms Designer

  • When a user opens a fragment library by selecting a fragment folder in AEM Forms Designer version 6.5.21.0, it crashes. (LC-3922439)
  • When a user uninstalls the 32-bit AEM Forms Designer version 6.5.20.0 and installs AEM Forms Designer version 6.5.21.0, Forms Designer fails to start. The error logs show insufficient memory allocation for the Java Runtime Environment (JRE). (LC-3922404)
  • After a user installs AEM Forms Designer version 6.5.20.0, the Macros option does not appear in the menu, only the default ‘Accessibility Checker’ macro appears and fails to run. (LC-3922321)
  • When a user adds a new template location for creating XDPs in AEM Forms Designer version 6.5.20.0, Forms Designer crashes. (LC-3922316)
  • When a user generates output using the ExportData method in AEM Forms 6.5 Service Pack 15 (6.5.15.0) OSGI, it produces incomplete and incorrect data. (LC-3922340)

Foundation

In the AEM Assets console, an issue occurred when attempting to reorder DITA documents. The breadcrumb at the top of the path browser dialog box incorrectly displays the node name instead of the node title for the root parent. The correct node title only appears after selecting an item within the breadcrumb, indicating a temporary display error. (NPR-42106)

Communities

After upgrading from AEM 6.5.19 to 6.5.20, an issue emerged where Connection evic threads failed to close properly after calls to UgcSearch. This problem, observed in the production environment, causes these threads to persist and accumulate over time, potentially impacting performance. (NPR-42019)

CRX

  • Sorting was not working as per Groups in the left side menu in CRX Package Manager. (GRANITE-53277)
  • The Package Manager in AEM restricts the installation of lower package versions by default but allows forceful installations of older versions. However, using the force install option can interfere with future installations through the standard pipeline. For instance, if version 1.21 is installed and version 1.24 is added, the installation succeeds, listing both versions. However, trying to install version 1.22 over 1.24 fails through the pipeline but works if forcefully installed, listing all versions. Similarly, installing version 1.23 is blocked if version 1.24 is already present, as the pipeline does not permit downgrades. (GRANITE-53263)

Granite

  • Snapshot packages were being installed in AEM using CURL commands. During installation, the JCR installer scanned the packages by way of the OSGI Installer to ensure that no additional OSGI bundles or configurations are required. If a package version contained “SNAPSHOT,” the OSGI Installer triggered VLT to create a corresponding snapshot package. However, because each AEM author instance runs its own OSGI Installer, both instances may attempt to generate the snapshot simultaneously, leading to session conflicts within the repository. (NPR-42003)
  • A lock contention existed in ScriptDependencyResolver with AEM 6.5.21. (GRANITE-53181)
  • After upgrading AEM to 6.5.21, issues arose when relative paths were used in Sightly (HTL) syntax, such as data-sly-use. (GRANITE-53080)

Integrations

  • Added legal attribution statement for Cloud Services user interface. (FORMS-16373)
  • Addition of read permissions for the fd-cloudservice user to access hCaptcha and Turnstile configurations, letting it retrieve the client ID and client secret necessary for captcha rendering and validation. Additionally, an Access Control List model was implemented to manage access to these configurations. (FORMS-16360)

Localization

In Hammer icon Tools > Security > User icon Users, on the User Management page, the data in Status column of the table was displaying vertically. (GRANITE-48304)

Platform

  • The Enterprise Information Management tracking introduced in AEM 6.5.18 caused anomalies in calculating product adoption scores. The Adobe Metrics library caused this issue by overwriting user data supplied by the Omega tracking library. As a result, adoption scores for many AEM Sites and AEM Assets customers dropped to zero starting February 2024. (CQ-4358438)
  • A critical issue has been identified in the production environment where the Garbage Collector was improperly handling tags. Specifically, when a tag was moved or renamed, the Garbage Collector failed to update the cq:MovedTo property, causing the tag to disappear from pages. (CQ-4358293)
  • A problem with ContextHub in AEM 6.5.19 was causing segments to resolve incorrectly when a context path was added to an AEM instance. The issue specifically affected the URL field within the JavaScript objects generated by the page component, where the required context path prefix was missing. This omission prevented segments from functioning as expected. (SITES-21852)
  • Updated AEM Quickstart to use the library commons-collections-3.2.2-adobe-2. The update ensures that the application can continue to run smoothly. (NPR-42150)
  • The SMTP OAuth2 setup in AEM 6.5 differs significantly from what is used in AEM as a Cloud Service. To streamline configuration and ensure consistency, the setup in AEM 6.5 needed to be aligned with the standards used in AEM as a Cloud Service. (GRANITE-53273)
  • An issue was found when you clicked Compass icon > Project icon Projects, then hovered your mouse pointer over Rail left icon Chevron Down icon , a grave accent appeared before the tooltip text “Content Only.” (CQ-4356633)

Security

  • Issues were encountered with an outdated JSAFE cryptographic library (version 6.0.0) in AEM. A patched bundle with JSAFE version 6.2.5 is included in AEM 6.5.22. (NPR-42006)
  • When validating allowed protocols during XSS checks, handlers compare against “http” and “https.” However, the protocol property of a URL object returned these values with a trailing colon, such as http: and https:. This mismatch caused validation issues. To ensure accurate parsing, the protocol check needed to account for the colon or adjust the comparison logic accordingly. (NPR-42119)
  • After installing AEM 6.5.21 (the previous version was AEM 6.5.19) on IBM® WebSphere® Liberty Profile and Semeru Java 8.0, it was not possible to open any pages. Error logs indicated issues related to servlet versions that different bundles required. To address this issue, the dependency on org.apache.felix.http.servlet-api-1.2.0_fragment_full.jar had to be reverted because it related to the problem. (NPR-42116)
  • Several browsers are phasing out support for SameSite=None cookies, which are used to allow cross-site access to cookies. As an alternative, Partitioned cookies are being introduced. These cookies isolate storage by the context in which they are used, enhancing privacy and security by preventing tracking across sites while still allowing cookies to function within specific partitions, such as embedded third-party content. (GRANITE-51953)

Translation

  • Added support for recent changes in Core Components to default translation rules. (NPR-42029)
  • An issue was identified with the export of XLIFF files in AEM Forms. When using the Export selection as XLIFF (strings only) option, the sequence of components was not consistently maintained. However, the sequence remains correct when exporting XLIFF for a specific language. Two files were provided to demonstrate the issue: DE-CH_Export.xliff (correct sequence) and String_Export.xliff (incorrect sequence). (NPR-42118)

User interface

  • The coralui-component-dialog was altering the placement of cq-dialog-actions, potentially affecting the layout or behavior of action buttons within dialog boxes in AEM. (NPR-42294)
  • The color picker functionality in AEM was malfunctioning. When accessed, it displayed a blank modal, preventing color selection. This issue began after installing AEM 6.5.20 in the Stage environment. The color picker worked correctly prior to the update. (NPR-42163)
  • In Hammer icon Tools > Workflow > Models > select any model > Start Workflow, the Browse icon was missing from the Payload field in the Run Workflow dialog box. (NPR-42162)

Install Experience Manager 6.5.22.0

  • Experience Manager 6.5.22.0 requires Experience Manager 6.5. See upgrade documentation for detailed instructions.
  • The Service Pack download is available on Adobe Software Distribution.
  • On a deployment with MongoDB and multiple instances, install Experience Manager 6.5.22.0 on one of the Author instances using the Package Manager.
IMPORTANT
Adobe does not recommend that you remove or uninstall the Experience Manager 6.5.22.0 package. As such, before you install the pack, you should create a backup of the crx-repository in case you must roll it back.