ABB Automation Builder 2.9.1 Fixes Project File Code Execution

P1 — VALIDATE AND UPDATEHigh · 7.8 (CVSS v3.1)EXPLOITATION: NOT STATED

Quick Answer

The authority published 3ADR011566 for ABB Automation Builder releases before 2.9.1. ABB is aware of vulnerabilities in the products versions listed as affected in the advisory. Automation Builder could execute arbitrary code by crafting the project file or project archive file. A vulnerability has been discovered in the print engine of Automation Builder. If an Automation Builder project file or archive file was crafted in a specific way, the Automation Builder could execute arbitrary code when a user opens these files and configures the print/printer options or prints the project or parts of it. This arbitrary code would be executed in the context of the user who was tricked into opening the project. Affected deployments should be matched to the authority's exact scope and moved to the supported fixed release.

Confirm Scope And Apply The Supported Fix

What to do now: Inventory ABB Automation Builder releases before 2.9.1, match the exact affected release or feature, apply the authority-supported fixed build or service remediation, validate the dependent workflow, and preserve evidence.

Open the authoritative advisory

Last verified: 2026-09-28 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.

Scope And Authority

Product scopeABB Automation Builder releases before 2.9.1
Advisory3ADR011566
CVECVE-2025-41700
Authoritative release date2026-09-28 00:30:00 UTC (ABB CSAF initial release); added to the ABB CSAF feed at 2026-09-28 12:15:00 UTC
Authority revision date2026-09-28 00:30:00.000 UTC
Affected versionsABB Automation Builder before 2.9.1 when a user opens a crafted project or project archive and invokes print or printer configuration.
Fixed versionABB Automation Builder 2.9.1
CVSS base score7.8 (CVSS v3.1)
CVSS severityHigh
Exploitation statusNot stated by the authority; no exploitation claim is inferred.

What Changed

ABB is aware of vulnerabilities in the products versions listed as affected in the advisory. Automation Builder could execute arbitrary code by crafting the project file or project archive file. A vulnerability has been discovered in the print engine of Automation Builder. If an Automation Builder project file or archive file was crafted in a specific way, the Automation Builder could execute arbitrary code when a user opens these files and configures the print/printer options or prints the project or parts of it. This arbitrary code would be executed in the context of the user who was tricked into opening the project.

What To Validate Now

  1. Inventory. Locate ABB Automation Builder releases before 2.9.1 deployments, versions, enabled features, exposure paths, owners, and dependent services.
  2. Establish applicability. Compare each deployment with the authority's affected-version statement: ABB Automation Builder before 2.9.1 when a user opens a crafted project or project archive and invokes print or printer configuration. Do not infer applicability from product family or severity alone.
  3. Remediate. Apply ABB Automation Builder 2.9.1 through the supported vendor or project channel, following the current advisory and change-control requirements.
  4. Validate. Confirm the resulting version or managed-service state, exercise representative functionality and recovery paths, monitor for regressions, and document exceptions.
  5. Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.

Operational Cautions

Use the exact supported release stream and repository. Test dependencies, clusters, integrations, and rollback before broad deployment; a CVSS rating or reachable feature is not evidence of exploitation.

Evidence To Retain

  • Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
  • UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
  • Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.

Related TechGeeks Resources

Authoritative References

Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.