# Snyk test report

December 14th 2025, 12:24:32 am (UTC+00:00)

Scanned the following paths:

- /argo-cd/argoproj/argo-cd/v3/go.mod (gomodules)
- /argo-cd/argoproj/gitops-engine/gitops-engine/go.mod (gomodules)
- /argo-cd/argoproj/argo-cd/get-previous-release/hack/get-previous-release/go.mod (gomodules)
- /argo-cd/ui/yarn.lock (yarn)

8 known vulnerabilities
29 vulnerable dependency paths
2868 dependencies

## MPL-2.0 license

medium severity

- Manifest file: /argo-cd/argoproj/argo-cd/v3 › go.mod
- Package Manager: golang
- Module: github.com/r3labs/diff/v3
- Introduced through: github.com/argoproj/argo-cd/v3@0.0.0 and github.com/r3labs/diff/v3@3.0.2

### Detailed paths

- Introduced through: github.com/argoproj/argo-cd/v3@0.0.0 › github.com/r3labs/diff/v3@3.0.2

MPL-2.0 license

More about this vulnerability

## MPL-2.0 license

medium severity

- Manifest file: /argo-cd/argoproj/argo-cd/v3 › go.mod
- Package Manager: golang
- Module: github.com/hashicorp/go-version
- Introduced through: github.com/argoproj/argo-cd/v3@0.0.0, code.gitea.io/sdk/gitea@0.22.1 and others

### Detailed paths

- Introduced through: github.com/argoproj/argo-cd/v3@0.0.0 › code.gitea.io/sdk/gitea@0.22.1 › github.com/hashicorp/go-version@1.7.0

MPL-2.0 license

More about this vulnerability

## MPL-2.0 license

medium severity

- Manifest file: /argo-cd/argoproj/argo-cd/v3 › go.mod
- Package Manager: golang
- Module: github.com/hashicorp/go-retryablehttp
- Introduced through: github.com/argoproj/argo-cd/v3@0.0.0 and github.com/hashicorp/go-retryablehttp@0.7.8

### Detailed paths

- Introduced through: github.com/argoproj/argo-cd/v3@0.0.0 › github.com/hashicorp/go-retryablehttp@0.7.8
- Introduced through: github.com/argoproj/argo-cd/v3@0.0.0 › github.com/argoproj/notifications-engine/pkg/services@#e2e7fe18381a › github.com/hashicorp/go-retryablehttp@0.7.8
- Introduced through: github.com/argoproj/argo-cd/v3@0.0.0 › gitlab.com/gitlab-org/api/client-go@1.8.1 › github.com/hashicorp/go-retryablehttp@0.7.8
- Introduced through: github.com/argoproj/argo-cd/v3@0.0.0 › github.com/argoproj/notifications-engine/pkg/subscriptions@#e2e7fe18381a › github.com/argoproj/notifications-engine/pkg/services@#e2e7fe18381a › github.com/hashicorp/go-retryablehttp@0.7.8
- Introduced through: github.com/argoproj/argo-cd/v3@0.0.0 › github.com/argoproj/notifications-engine/pkg/cmd@#e2e7fe18381a › github.com/argoproj/notifications-engine/pkg/services@#e2e7fe18381a › github.com/hashicorp/go-retryablehttp@0.7.8
- Introduced through: github.com/argoproj/argo-cd/v3@0.0.0 › github.com/argoproj/notifications-engine/pkg/services@#e2e7fe18381a › github.com/opsgenie/opsgenie-go-sdk-v2/client@1.2.23 › github.com/hashicorp/go-retryablehttp@0.7.8
- Introduced through: github.com/argoproj/argo-cd/v3@0.0.0 › github.com/argoproj/notifications-engine/pkg/api@#e2e7fe18381a › github.com/argoproj/notifications-engine/pkg/subscriptions@#e2e7fe18381a › github.com/argoproj/notifications-engine/pkg/services@#e2e7fe18381a › github.com/hashicorp/go-retryablehttp@0.7.8
- Introduced through: github.com/argoproj/argo-cd/v3@0.0.0 › github.com/argoproj/notifications-engine/pkg/controller@#e2e7fe18381a › github.com/argoproj/notifications-engine/pkg/subscriptions@#e2e7fe18381a › github.com/argoproj/notifications-engine/pkg/services@#e2e7fe18381a › github.com/hashicorp/go-retryablehttp@0.7.8
- Introduced through: github.com/argoproj/argo-cd/v3@0.0.0 › github.com/argoproj/notifications-engine/pkg/subscriptions@#e2e7fe18381a › github.com/argoproj/notifications-engine/pkg/services@#e2e7fe18381a › github.com/opsgenie/opsgenie-go-sdk-v2/client@1.2.23 › github.com/hashicorp/go-retryablehttp@0.7.8
- Introduced through: github.com/argoproj/argo-cd/v3@0.0.0 › github.com/argoproj/notifications-engine/pkg/cmd@#e2e7fe18381a › github.com/argoproj/notifications-engine/pkg/services@#e2e7fe18381a › github.com/opsgenie/opsgenie-go-sdk-v2/client@1.2.23 › github.com/hashicorp/go-retryablehttp@0.7.8
- Introduced through: github.com/argoproj/argo-cd/v3@0.0.0 › github.com/argoproj/notifications-engine/pkg/api@#e2e7fe18381a › github.com/argoproj/notifications-engine/pkg/subscriptions@#e2e7fe18381a › github.com/argoproj/notifications-engine/pkg/services@#e2e7fe18381a › github.com/opsgenie/opsgenie-go-sdk-v2/client@1.2.23 › github.com/hashicorp/go-retryablehttp@0.7.8
- Introduced through: github.com/argoproj/argo-cd/v3@0.0.0 › github.com/argoproj/notifications-engine/pkg/controller@#e2e7fe18381a › github.com/argoproj/notifications-engine/pkg/subscriptions@#e2e7fe18381a › github.com/argoproj/notifications-engine/pkg/services@#e2e7fe18381a › github.com/opsgenie/opsgenie-go-sdk-v2/client@1.2.23 › github.com/hashicorp/go-retryablehttp@0.7.8

MPL-2.0 license

More about this vulnerability

## MPL-2.0 license

medium severity

- Manifest file: /argo-cd/argoproj/argo-cd/v3 › go.mod
- Package Manager: golang
- Module: github.com/hashicorp/go-cleanhttp
- Introduced through: github.com/argoproj/argo-cd/v3@0.0.0, github.com/hashicorp/go-retryablehttp@0.7.8 and others

### Detailed paths

- Introduced through: github.com/argoproj/argo-cd/v3@0.0.0 › github.com/hashicorp/go-retryablehttp@0.7.8 › github.com/hashicorp/go-cleanhttp@0.5.2
- Introduced through: github.com/argoproj/argo-cd/v3@0.0.0 › gitlab.com/gitlab-org/api/client-go@1.8.1 › github.com/hashicorp/go-cleanhttp@0.5.2
- Introduced through: github.com/argoproj/argo-cd/v3@0.0.0 › gitlab.com/gitlab-org/api/client-go@1.8.1 › github.com/hashicorp/go-retryablehttp@0.7.8 › github.com/hashicorp/go-cleanhttp@0.5.2
- Introduced through: github.com/argoproj/argo-cd/v3@0.0.0 › github.com/argoproj/notifications-engine/pkg/services@#e2e7fe18381a › github.com/opsgenie/opsgenie-go-sdk-v2/client@1.2.23 › github.com/hashicorp/go-retryablehttp@0.7.8 › github.com/hashicorp/go-cleanhttp@0.5.2
- Introduced through: github.com/argoproj/argo-cd/v3@0.0.0 › github.com/argoproj/notifications-engine/pkg/subscriptions@#e2e7fe18381a › github.com/argoproj/notifications-engine/pkg/services@#e2e7fe18381a › github.com/opsgenie/opsgenie-go-sdk-v2/client@1.2.23 › github.com/hashicorp/go-retryablehttp@0.7.8 › github.com/hashicorp/go-cleanhttp@0.5.2
- Introduced through: github.com/argoproj/argo-cd/v3@0.0.0 › github.com/argoproj/notifications-engine/pkg/cmd@#e2e7fe18381a › github.com/argoproj/notifications-engine/pkg/services@#e2e7fe18381a › github.com/opsgenie/opsgenie-go-sdk-v2/client@1.2.23 › github.com/hashicorp/go-retryablehttp@0.7.8 › github.com/hashicorp/go-cleanhttp@0.5.2
- Introduced through: github.com/argoproj/argo-cd/v3@0.0.0 › github.com/argoproj/notifications-engine/pkg/api@#e2e7fe18381a › github.com/argoproj/notifications-engine/pkg/subscriptions@#e2e7fe18381a › github.com/argoproj/notifications-engine/pkg/services@#e2e7fe18381a › github.com/opsgenie/opsgenie-go-sdk-v2/client@1.2.23 › github.com/hashicorp/go-retryablehttp@0.7.8 › github.com/hashicorp/go-cleanhttp@0.5.2
- Introduced through: github.com/argoproj/argo-cd/v3@0.0.0 › github.com/argoproj/notifications-engine/pkg/controller@#e2e7fe18381a › github.com/argoproj/notifications-engine/pkg/subscriptions@#e2e7fe18381a › github.com/argoproj/notifications-engine/pkg/services@#e2e7fe18381a › github.com/opsgenie/opsgenie-go-sdk-v2/client@1.2.23 › github.com/hashicorp/go-retryablehttp@0.7.8 › github.com/hashicorp/go-cleanhttp@0.5.2

MPL-2.0 license

More about this vulnerability

## MPL-2.0 license

medium severity

- Manifest file: /argo-cd/argoproj/argo-cd/v3 › go.mod
- Package Manager: golang
- Module: github.com/gosimple/slug
- Introduced through: github.com/argoproj/argo-cd/v3@0.0.0 and github.com/gosimple/slug@1.15.0

### Detailed paths

- Introduced through: github.com/argoproj/argo-cd/v3@0.0.0 › github.com/gosimple/slug@1.15.0

MPL-2.0 license

More about this vulnerability

## Regular Expression Denial of Service (ReDoS)

medium severity

- Manifest file: /argo-cd › ui/yarn.lock
- Package Manager: npm
- Vulnerable module: foundation-sites
- Introduced through: argo-cd-ui@1.0.0 and foundation-sites@6.8.1

### Detailed paths

- Introduced through: argo-cd-ui@1.0.0 › foundation-sites@6.8.1
- Introduced through: argo-cd-ui@1.0.0 › argo-ui@1.0.0 › foundation-sites@6.8.1

## Overview

foundation-sites is a responsive front-end framework

Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) due to inefficient backtracking in the regular expressions used in URL forms.

## PoC

    https://www.''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''

## Details

Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its original and legitimate users. There are many types of DoS attacks, ranging from trying to clog the network pipes to the system by generating a large volume of traffic from many machines (a Distributed Denial of Service - DDoS - attack) to sending crafted requests that cause a system to crash or take a disproportional amount of time to process.

The Regular expression Denial of Service (ReDoS) is a type of Denial of Service attack. Regular expressions are incredibly powerful, but they aren't very intuitive and can ultimately end up making it easy for attackers to take your site down.

Let’s take the following regular expression as an example:

    regex = /A(B|C+)+D/

This regular expression accomplishes the following:

- `A` The string must start with the letter 'A'
- `(B|C+)+` The string must then follow the letter A with either the letter 'B' or some number of occurrences of the letter 'C' (the `+` matches one or more times). The `+` at the end of this section states that we can look for one or more matches of this section.
- `D` Finally, we ensure this section of the string ends with a 'D'

The expression would match inputs such as `ABBD`, `ABCCCCD`, `ABCBCCCD` and `ACCCCCD`

It most cases, it doesn't take very long for a regex engine to find a match:

    $ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCD")'
            0.04s user 0.01s system 95% cpu 0.052 total

            $ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCX")'
            1.79s user 0.02s system 99% cpu 1.812 total

The entire process of testing it against a 30 characters long string takes around ~52ms. But when given an invalid string, it takes nearly two seconds to complete the test, over ten times as long as it took to test a valid string. The dramatic difference is due to the way regular expressions get evaluated.

Most Regex engines will work very similarly (with minor differences). The engine will match the first possible way to accept the current character and proceed to the next one. If it then fails to match the next one, it will backtrack and see if there was another way to digest the previous character. If it goes too far down the rabbit hole only to find out the string doesn’t match in the end, and if many characters have multiple valid regex paths, the number of backtracking steps can become very large, resulting in what is known as catastrophic backtracking.

Let's look at how our expression runs into this problem, using a shorter string: "ACCCX". While it seems fairly straightforward, there are still four different ways that the engine could match those three C's:

1. CCC
2. CC+C
3. C+CC
4. C+C+C.

The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't match.

From there, the number of steps the engine must use to validate a string just continues to grow.

String | Number of C's | Number of steps
--- | --- | ---
ACCCX | 3 | 38
ACCCCX | 4 | 71
ACCCCCX | 5 | 136
ACCCCCCCCCCCCCCX | 14 | 65,553

By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.

## Remediation

There is no fixed version for `foundation-sites`.

## References

- GitHub Advisory
- GitHub Issue
- Vulnerable Code

More about this vulnerability

## Insecure Randomness

low severity

- Manifest file: /argo-cd › ui/yarn.lock
- Package Manager: npm
- Vulnerable module: formidable
- Introduced through: argo-cd-ui@1.0.0, superagent@8.1.2 and others

### Detailed paths

- Introduced through: argo-cd-ui@1.0.0 › superagent@8.1.2 › formidable@2.1.2

## Overview

Affected versions of this package are vulnerable to Insecure Randomness due to its use of the `hexoid()` function in the generation of fingerprint IDs.

## Remediation

Upgrade `formidable` to version 2.1.3, 3.5.3 or higher.

## References

- GitHub Commit
- Vulnerability Report

More about this vulnerability

## Regular Expression Denial of Service (ReDoS)

low severity

- Manifest file: /argo-cd › ui/yarn.lock
- Package Manager: npm
- Vulnerable module: brace-expansion
- Introduced through: argo-cd-ui@1.0.0, argo-ui@1.0.0 and others

### Detailed paths

- Introduced through: argo-cd-ui@1.0.0 › argo-ui@1.0.0 › minimatch@5.1.6 › brace-expansion@2.0.1
- Introduced through: argo-cd-ui@1.0.0 › redoc@2.4.0 › @redocly/openapi-core@1.30.0 › minimatch@5.1.6 › brace-expansion@2.0.1
- Introduced through: argo-cd-ui@1.0.0 › minimatch@3.1.2 › brace-expansion@1.1.11

## Overview

brace-expansion is a Brace expansion as known from sh/bash

Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) in the `expand()` function, which is prone to catastrophic backtracking on very long malicious inputs.

## PoC

    import index from "./index.js";

            let str = "{a}" + ",".repeat(100000) + "\u0000";

            let startTime = performance.now();

            const result = index(str);

            let endTime = performance.now();

            let timeTaken = endTime - startTime;

            console.log(`匹配耗时: ${timeTaken.toFixed(3)} 毫秒`);

## Details

Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its original and legitimate users. There are many types of DoS attacks, ranging from trying to clog the network pipes to the system by generating a large volume of traffic from many machines (a Distributed Denial of Service - DDoS - attack) to sending crafted requests that cause a system to crash or take a disproportional amount of time to process.

The Regular expression Denial of Service (ReDoS) is a type of Denial of Service attack. Regular expressions are incredibly powerful, but they aren't very intuitive and can ultimately end up making it easy for attackers to take your site down.

Let’s take the following regular expression as an example:

    regex = /A(B|C+)+D/

This regular expression accomplishes the following:

- `A` The string must start with the letter 'A'
- `(B|C+)+` The string must then follow the letter A with either the letter 'B' or some number of occurrences of the letter 'C' (the `+` matches one or more times). The `+` at the end of this section states that we can look for one or more matches of this section.
- `D` Finally, we ensure this section of the string ends with a 'D'

The expression would match inputs such as `ABBD`, `ABCCCCD`, `ABCBCCCD` and `ACCCCCD`

It most cases, it doesn't take very long for a regex engine to find a match:

    $ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCD")'
            0.04s user 0.01s system 95% cpu 0.052 total

            $ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCX")'
            1.79s user 0.02s system 99% cpu 1.812 total

The entire process of testing it against a 30 characters long string takes around ~52ms. But when given an invalid string, it takes nearly two seconds to complete the test, over ten times as long as it took to test a valid string. The dramatic difference is due to the way regular expressions get evaluated.

Most Regex engines will work very similarly (with minor differences). The engine will match the first possible way to accept the current character and proceed to the next one. If it then fails to match the next one, it will backtrack and see if there was another way to digest the previous character. If it goes too far down the rabbit hole only to find out the string doesn’t match in the end, and if many characters have multiple valid regex paths, the number of backtracking steps can become very large, resulting in what is known as catastrophic backtracking.

Let's look at how our expression runs into this problem, using a shorter string: "ACCCX". While it seems fairly straightforward, there are still four different ways that the engine could match those three C's:

1. CCC
2. CC+C
3. C+CC
4. C+C+C.

The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't match.

From there, the number of steps the engine must use to validate a string just continues to grow.

String | Number of C's | Number of steps
--- | --- | ---
ACCCX | 3 | 38
ACCCCX | 4 | 71
ACCCCCX | 5 | 136
ACCCCCCCCCCCCCCX | 14 | 65,553

By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.

## Remediation

Upgrade `brace-expansion` to version 1.1.12, 2.0.2, 3.0.1, 4.0.1 or higher.

## References

- GitHub Advisory
- GitHub Commit
- GitHub Gist
- GitHub PR

More about this vulnerability