Skip to main content

Product Updates

Engine
Surface
AI Workflows
Area
Release Status

Showing 1 - 10 of 66 updates

New model risk scoring for AI models in Evo

General availability

Starting August 17, 2026, Evo by Snyk uses a rebuilt model risk score to evaluate the AI models discovered in your organization.

The previous Risk Index is replaced by a single score from 0–1,000 that combines attack success rate with the potential impact of a successful attack, tested against categories including prompt injection, data exfiltration, and insecure code generation. The result is a score that reflects both how easily a model can be compromised and how much damage that compromise could cause — not just whether an attack succeeded.

What's new:

  • Impact-weighted scoring: Risk scores now factor in the real-world consequence of an attack succeeding, not only its likelihood.

  • Four severity bands: Scores map to low (0–249), medium (250–499), high (500–749), and critical (750–1,000), so you can triage at a glance.

  • Broader attack coverage: Testing spans a wider range of direct and indirect attack categories against each discovered model.

  • Framework-mapped: Findings map to OWASP LLM Top 10, OWASP Agentic Security, MITRE ATLAS, and NIST AI 600-1/100-2e2025, so you can connect model risk to the compliance frameworks you already report against.

  • Policy-ready from day one: Evo applies default policies across common attack categories automatically, and you can create custom policies scoped to specific attack categories or goals to match your organization's risk tolerance.

If you have policies built on the old Risk Index: those policies remain visible but no longer evaluate under the new scoring. Review and recreate any Risk Index-based policies against the new model risk score to keep enforcement active.

Read more in the Risk intelligence documentation.

Headshot of Ranko Cupovic

Ranko Cupovic | Principal Product Manager

Announcing Snyk CLI v1.1306.4

Fix

We are pleased to announce Snyk CLI release, v1.1306.4

This release contains fixes and minor improvements. To learn more beyond what is highlighted below, please reference the full release notes.

This update includes the following:

  • Clearer error messages when the CLI cannot reach a configured proxy. Failures now report the proxy URL the CLI attempted to use, with credentials redacted, along with the specific error code SNYK-CLI-0028, making proxy misconfiguration quicker to diagnose in CI and behind corporate networks.

  • An updated embedded runtime, moving Node.js from 22.22.2 to 22.23.2 and OpenSSL from 3.5.5 to 3.5.7, which brings in fixes for six high-severity CVEs plus additional OpenSSL security fixes.

  • Fixed vulnerabilities:

If you have any questions, feel free to reach out to the Snyk support team. We encourage everyone to upgrade to the latest version to take advantage of these improvements.

Matt Dolan | Senior Product Manager

Tags:

Announcing Snyk CLI v1.1306.3

Fix

We are pleased to announce Snyk CLI release, v1.1306.3

This release contains security fixes. To learn more beyond what is highlighted below, please reference the full release notes.

This update includes the following:

  • Updates bundled dependencies to remediate known vulnerabilities, keeping the CLI current for teams with supply chain policies on the tools running in their pipelines.

  • Fixed vulnerabilities:

If you have any questions, feel free to reach out to the Snyk support team. We encourage everyone to upgrade to the latest version to take advantage of these improvements.

Matt Dolan | Senior Product Manager

Tags:

Snyk secrets scanner reaches general availability

New

Starting August 4, 2026, Snyk secrets scanner is generally available to help secure your entire SDLC against credential leaks.

Stolen credentials remain a leading initial access vector in security breaches, and the rise of AI-generated code increases the risk of exposing sensitive data. You can now use Snyk secrets scanner to detect hardcoded credentials, API keys, and tokens across your repositories and prevent them from reaching commits or being leaked.

Key capabilities include:

  • Machine learning driven detection and prevention across your development surfaces.

  • Secrets detection for both human-written and AI-generated code.

  • Governance and finding management directly within the Snyk web UI.

For more information, please read the blog and Snyk Secrets documentation

Governed ignores with Ignore Approval Workflow (IAW)

General availability

Until now, a developer could suppress a Snyk Code finding on their own — directly in the Web UI or IDE — with no review step.

Suppression happened silently and unilaterally, leaving security teams without a gate on what got ignored.

Ignore Approval Workflow changes that.

An ignore is no longer applied automatically — it becomes a request that only takes effect after a reviewer approves it. Developers submit ignores from where they work; a reviewer approves or rejects from the web; both sides are notified of the outcome. Suppression moves from an ungoverned action to a reviewed, auditable one.

What you can do

  • Submit ignore requests from the CLI, IDE, or API — a reason is required, and the ignore is created as Pending rather than applied.

  • Review from the web — reviewers with the review permission approve or reject on the Ignore Requests page.

  • Auto-approve your own — reviewers can bypass triage for ignores they create themselves.

  • Stay notified — reviewers are emailed on new requests and requesters on the outcome.

  • Control access with roles — read / create / edit / review / delete permissions; by default Collaborators request and Admins review, with custom roles supported.

  • Audit everything — export ignore-request data via the audit-logs API.

Announcing Snyk CLI v1.1306.2

Fix

We are pleased to announce Snyk CLI release, v1.1306.2

This release contains fixes and minor improvements. To learn more beyond what is highlighted below, please reference the full release notes.

This update includes the following:

If you have any questions, feel free to reach out to the Snyk support team. We encourage everyone to upgrade to the latest version to take advantage of these improvements.

Tags:

Announcing Snyk CLI v1.1306.1

Fix

We are pleased to announce Snyk CLI release, v1.1306.1

This release contains fixes to ensure security. To learn more beyond what is highlighted below, please reference the full release notes.

This update includes the following:

  • Fixed vulnerabilities:

    • CVE-2026-41907

    • CVE-2026-13149

    • CVE-2026-59869

    • CVE-2026-59873

    • CVE-2026-39244

Release notes can be found here.

If you have any questions, feel free to reach out to the Snyk support team. We encourage everyone to upgrade to the latest version to take advantage of these improvements.

Matt Dolan | Senior Product Manager

Tags:

Announcing Snyk CLI v1.1306.0

New

We are pleased to announce the latest stable Snyk CLI release, v1.1306.0.

We are introducing the following key improvements in this version. To learn more about bug fixes and additional enhancements beyond what is highlighted below, please reference the full release notes.

This update includes the following:

  • Doctor

    • Adds a new snyk doctor command, giving you a quick way to diagnose common CLI problems by generating a diagnostic report for your system or analyzing debug log output.

  • Container

    • Container scans now detect the Java runtime version across a wider range of JVM base images, and can find vulnerabilities in .NET application dependencies.

  • Snyk Studio MCP

    • The breakability evaluation tool in the Snyk MCP Server is now enabled by default and no longer requires an experimental flag.

  • SCA Test

    • Improves dependency detection for Gradle projects.

  • Additional Reliability and Performance Improvements

    • Shows a warning when a request is automatically retried due to rate limiting, instead of retrying silently.

    • Skips the reachability upload when no supported files are present, instead of failing.

    • Fixes dependency resolution for Swift Package Manager projects that reference packages by registry identity, so they're correctly matched to their GitHub source for vulnerability scanning.

    • Fixes scanning of sbt projects with custom Scala configurations.

    • Fixes a bug where scanning Yarn workspaces could report vulnerabilities from a workspace member's dev dependencies as production dependencies, when that member was consumed by a sibling package.

    • Updates dependencies to fix vulnerabilities.

Release notes can be found here.

If you have any questions, feel free to reach out to the Snyk support team. We encourage everyone to upgrade to the latest version to take advantage of these new features and improvements.

Matt Dolan | Senior Product Manager

Snyk Open Source ecosystem coverage update

General availability

We've expanded Snyk Open Source coverage with improved scanning capabilities. These updates help you close security gaps and manage dependencies more effectively. Key improvements include new support for the uv package manager and enhanced Go scanning for private dependencies.

uv SCM support

The uv package manager is an emerging tool in the Python ecosystem. Following our earlier CLI release, uv is now available in SCM integrations. You can import uv projects and workspaces, use PR Checks, and monitor your code directly from your connected Git repositories. You do not need to use the CLI for these tasks. uv joins pip, Poetry, and Pipenv as the fourth Python ecosystem with native support in Snyk Open Source.

To get started, enable this feature for your Groups and Organizations in Snyk Preview. You can find more details in the Snyk documentation.

Improved Go scanning

Our Go scanning improvements are now generally available. This update features support for private dependencies. Go teams that use private module proxies, such as Artifactory or Nexus, or private repositories via Broker, can now achieve the same depth of scanning available for public modules.

This ensures you have no blind spots in your dependency graph when a module lives behind authentication. We support both brokered and direct connections across all SCM integrations. We are rolling this out to all users over the next two weeks. You can learn how to configure private dependencies in the Snyk documentation.

Announcing Snyk CLI v1.1305.2

Fix

We are pleased to announce Snyk CLI release, v1.1305.2.

This release contains fixes and minor improvements. To learn more beyond what is highlighted below, please reference the full release notes.

This update includes the following:

  • Bumped the Go runtime to version 1.26.4.

  • Improved MCP logging and addressed security issues in the Snyk MCP Server.

  • Fixed vulnerabilities:

    • CVE-2026-44705

    • CVE-2026-45570

    • CVE-2026-49982

If you have any questions, feel free to reach out to the Snyk support team. We encourage everyone to upgrade to the latest version to take advantage of these improvements.

Matt Dolan | Senior Product Manager

Tags: