Tentacle container image ships with vulnerable NuGet dependencies

[pm7y]

Team

• I've assigned a team label to this issue

What happened?

The current latest octopusdeploy/tentacle:9.1.3772 Docker image bundles NuGet packages with known CVEs inside the Tentacle binary (/opt/octopus/tentacle/Tentacle.deps.json). These are compile-time dependencies that consumers of the image cannot patch via OS-level updates, apt-get upgrade, or any other post-build remediation.

Azure Defender for Cloud flags these vulnerabilities during container registry scanning. Some date back to 2017.

CVE	Severity	Package	Installed	Fixed
CVE-2017-11770	High	System.Security.Cryptography.X509Certificates	4.1.0	4.1.2
CVE-2023-29331	High	System.Security.Cryptography.Pkcs	6.0.1	6.0.3
CVE-2024-38095	High	System.Formats.Asn1	6.0.0	6.0.1
CVE-2018-8292	Medium	System.Net.Http	4.1.0	4.3.4
CVE-2019-0657	Medium	System.Private.Uri	4.3.0	4.3.2
CVE-2019-0820	Medium	System.Text.RegularExpressions	4.3.0	4.3.1
CVE-2019-0980	Medium	System.Private.Uri	4.3.0	4.3.2
CVE-2019-0981	Medium	System.Private.Uri	4.3.0	4.3.2

Expected: Container images published to Docker Hub should not contain NuGet packages with known, fixable CVEs.

Reproduction

1. Pull octopusdeploy/tentacle:9.1.3772
2. Inspect /opt/octopus/tentacle/Tentacle.deps.json for the package versions listed above
3. Cross-reference with NVD entries linked in the table

Alternatively, push the image to any container registry with vulnerability scanning enabled (Azure Defender, Trivy, Snyk, etc.) and observe the findings.

Error and Stacktrace

N/A — these are dependency-level CVEs, not runtime errors.

More Information

• All vulnerabilities trace to /opt/octopus/tentacle/Tentacle.deps.json
• These are transitive NuGet dependencies compiled into the Tentacle .NET application
• Image: octopusdeploy/tentacle:9.1.3772 (linux/amd64)
• Scanner: Azure Defender for Cloud (MDVM)
• Date: 2026-03-31
• PR Fix CVE vulnerabilities in transitive NuGet dependencies (#1204) #1205

Updating the affected NuGet package references in the Tentacle project to their fixed versions and publishing an updated container image would resolve these findings.

Workaround

No workaround available. The vulnerable packages are embedded in the application binary and cannot be patched externally. The only option for consumers is to suppress/accept these findings in their vulnerability scanner until an updated image is published.