Latest release latest-release
This page lists new capabilities, improvements and fixes coming with the latest Campaign Classic v7 Release. Every new build comes with a status which is materialized by a color. Learn more about Campaign Classic v7 build statuses in this page.
Release 7.4.4 release-7-4-4
Build 9401 build-9401
[General Availability]{class="badge positive" title="General Availability"}
August 25, 2026
Security improvements security-7-4-4-9401
Adobe has released security updates for Adobe Campaign Classic that address critical vulnerabilities. We encourage customers on on-premise and hybrid deployments to install the updates as soon as possible. Adobe-hosted instances have already been remediated and require no customer action. You can find more information in the security bulletin.
A restart of the Adobe Campaign server (nlserver) is required to load the build and complete deployment. The fix is active by default once restarted.
External URL allow list update security-enhancement-url-validation-9401
This release includes an update to the external URL allow list used for delivery content and attachments. Make sure all domains you currently reference are added to your instance’s approved allow list.
As a Campaign Administrator, use the Control Panel to add external URLs currently used in your deliveries to the allow list, and follow the same process for any new external URL going forward. Complete this activity by 5 September 2026 to avoid impact to affected deliveries. See Add URL permissions for steps.
Build 9400 build-9400
[Deprecated]{class="badge negative" title="Deprecated"}
August 11, 2026
This build includes several product improvements, security fixes, and the upgrade to the Adobe Analytics 2.0 API for the Adobe Analytics connector.
Security improvements security-7-4-4-9400
Adobe has released security updates for Adobe Campaign Classic that address critical vulnerabilities. We encourage customers on on-premise and hybrid deployments to install the updates as soon as possible. Adobe-hosted instances have already been remediated and require no customer action. You can find more information in the security bulletin.
A restart of the Adobe Campaign server (nlserver) is required to load the build and complete deployment. The fix is active by default once restarted.
Adobe Analytics 2.0 upgrade analytics-2-0-7-4-4
Adobe Analytics 1.4 APIs are reaching end-of-life. If you use the Adobe Analytics connector, you must upgrade to this build and complete a few migration steps depending on your deployment and use case. Learn how to migrate to the Adobe Analytics 2.0 API.
Release 7.4.3 release-7-4-3
Build 9399 build-9399
[Deprecated]{class="badge negative" title="Deprecated"}
August 3, 2026
Security improvements security-7-4-3-9399
Adobe has released security updates for Adobe Campaign Classic that address critical vulnerabilities. We encourage customers on on-premise and hybrid deployments to install the updates as soon as possible. Adobe-hosted instances have already been remediated and require no customer action. You can find more information in the security bulletin.
A restart of the Adobe Campaign server (nlserver) is required to load the build and complete deployment. The fix is active by default once restarted.
Build 9398 build-9398
[Deprecated]{class="badge negative" title="Deprecated"}
July 29, 2026
Security improvements security-7-4-3-9398
Adobe has released security updates for Adobe Campaign Classic that address critical vulnerabilities. We encourage customers on on-premise and hybrid deployments to install the updates as soon as possible. Adobe-hosted instances have already been remediated and require no customer action. You can find more information in the security bulletin.
A restart of the Adobe Campaign server (nlserver) is required to load the build and complete deployment. The fix is active by default once restarted.
Build 9397 build-9397
[Deprecated]{class="badge negative" title="Deprecated"}
June 30, 2026
Security improvements security-7-4-3-9397
This build includes security fixes and supersedes the previous Campaign Classic v7 builds. This build is now deprecated for on-premise and hybrid deployments; we encourage customers in these deployment modes to install the updates as soon as possible by upgrading to Build 9398 or later.
Other changes changes-7-4-3-9397
By default, webForm.jsp now ignores client-supplied ctx parameters. This is controlled by the disableCtxInWebForm parameter which is set to “true” by default.
If your webForm requests currently pass a ctx parameter in, you can temporarily re-enable this behavior by adding the following to the element of your config- .xml file. Plan to phase out this usage.
<web>
...
<jsp disableCtxInWebForm="false" />
...
</web>
Build 9396 build-9396
[Deprecated]{class="badge negative" title="Deprecated"}
June 9, 2026
This build includes security fixes.
Build 9394 build-9394
[Deprecated]{class="badge negative" title="Deprecated"}
Mar 31, 2026
Security improvements security-7-4-3
- To maintain optimal security, stability, and compliance, Debian has been upgraded to version 13 and PostgreSQL to version 17. Refer to the compatibility matrix.
Fixes fixes-7-4-3
- Fixed an issue where the barcode component allowed an unbounded height parameter, which could lead to a security vulnerability. (NEO-89984)
- Fixed an issue where enumeration fields in lists created via workflows were missing temporary name attributes, causing incorrect or blank enum labels to be displayed in the interface. (NEO-91158)
- Fixed an issue where delivery preparation failed with personalization errors when using targetData fields in workflows with deduplication activities. (NEO-87693)
- Fixed an issue where concatenating single-character string fields with other strings failed in PostgreSQL 15 due to type casting requirements. (NEO-88028)
- Fixed an issue where tracking logs for collaborative campaigns in Distributed Marketing were not being written to the database due to a mismatch between parent and child delivery IDs. (NEO-86836)
- Fixed an issue where delivery logs showed messages as canceled even though they were successfully sent, particularly affecting deliveries with wave scheduling. (NEO-78933)
- Fixed an issue where the database cleanup workflow was not efficiently purging data, which could impact performance. (NEO-76439)
- Fixed an issue where delivery statistics were not fully recomputed for some deliveries, particularly affecting the success indicators. (NEO-88106)
- Fixed an issue where the Client Console could crash when opening certain workflows referencing a missing upstream targeting schema. (NEO-28727)
- Fixed an issue where the Client Console version could not be identified after a failed startup, because the version file was missing from the install package. (NEO-94798)