Skip to content

Azure Pipelines Agent v4.269.0 (Node 24) breaks MicrosoftSecurityDevOps@1 v1.18.1: crypto.createCipher is not a function #154

Closed

Description

Since upgrading the Azure Pipelines Agent to v4.269.0 (Node 24), pipelines that are decorated to run Microsoft Security DevOps (MSDO) fail with:

TypeError: crypto.createCipher is not a function
at _exposeTaskLibSecret (azure-pipelines-task-lib/internal.js:923:29)
...

Root cause:

  • Node.js removed crypto.createCipher() in v22 (DEP0106). This is why Node 24 throws "is not a function".
  • The MSDO Azure DevOps task (MicrosoftSecurityDevOps@1, v1.18.1) still calls this removed API via azure-pipelines-task-lib.

Impact:

  • Organization-wide impact if the task is injected via a pipeline decorator (no pipeline-level control to pin a different injected task version).

Environment:

  • Azure Pipelines Agent: v4.269.0
  • Node runtime: v24.x (agent default)
  • MSDO task: MicrosoftSecurityDevOps@1 v1.18.1

Activity

  1. changed the title [-]MicrosoftSecurityDevOps@1 (v1.18.1) fails with "crypto.createCipher is not a function" on Azure Pipelines Agent v4.269.0 (Node 24)[/-] [+]Azure Pipelines Agent v4.269.0 (Node 24) breaks MicrosoftSecurityDevOps@1 v1.18.1: crypto.createCipher is not a function[/+] on Mar 12, 2026
  2. DimaBir commented on Mar 25, 2026

    @DimaBir
    Collaborator

    Thanks for reporting this issue.

    Root cause identified: The azure-pipelines-task-lib dependency at version ^4.13.0 (resolves to 4.17.3) uses the deprecated crypto.createCipher() API in its _exposeTaskLibSecret() function. This API was removed in Node.js v22 (DEP0106), causing the TypeError: crypto.createCipher is not a function error when running under Node 24.

    Fix: The upstream fix was merged in azure-pipelines-task-lib PR #1147, replacing createCipher with createCipheriv. This fix shipped in azure-pipelines-task-lib v5.2.4+. We are bumping our dependency from ^4.13.0 to ^5.2.4 to pick up this fix.

  3. added
    dependenciesPull requests that update a dependency file
    type:securitySecurity vulnerability or hardening
    priority:highImportant, should be addressed soon
    area:pipelineAzure Pipelines integration and configuration
    area:taskAzure DevOps build task definition and configuration
    on Mar 25, 2026
  4. DimaBir commented on Mar 26, 2026

    @DimaBir
    Collaborator

    Aymen Glaied (@AymenGlaied), merged. Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

area:pipelineAzure Pipelines integration and configurationarea:taskAzure DevOps build task definition and configurationdependenciesPull requests that update a dependency filepriority:highImportant, should be addressed soonstatus:approvedAccepted, ready to be worked ontype:securitySecurity vulnerability or hardening

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions