Skip to main content

Product Updates

Engine
Surface
AI Workflows
Area
Release Status

Showing 1 - 10 of 63 updates

Snyk Code November update

Improved

This update will be available on November 23, 2026.

Snyk Code reports additional findings in this update. Affected projects will report them on their next scan.

Newer language versions

Snyk Code supports PHP up to 8.5 and Swift up to 6.4. JavaScript and TypeScript analysis covers current syntax, including using declarations.

Kong plugins

Snyk Code analyzes Kong Gateway plugins written in Python, JavaScript, TypeScript and Go. It reports additional findings, such as command injection, where request data reaches a shell command.

More detection

Snyk Code reports additional findings in these areas:

  • Python: cross-site request forgery protection in Django, response handling in Flask, and JWT signature verification.

  • JavaScript: command injection and prototype pollution.

  • PHP: cookie security settings.

  • Java: SQL injection.

Fewer false positives

Snyk Code reports fewer false positives in Kotlin, JavaScript, Python and Java.

Refinements

Go, TypeScript and JavaScript: Snyk Code reads the project's own configuration to resolve imports. It now follows data across a project's own packages and modules, and analyzes these projects more deeply and more accurately.

Headshot of Sebastian Roth

Sebastian Roth | Senior Product Manager

Tags:

Pending ignore requests are now visible on the Project's Issues page

Improved

What Changed?

When you submit an ignore request under Ignore Approval Workflow, the issue now shows a clear "Pending Ignore Request" status directly on the Project's Issues page and in the issue details — so you can see at a glance that a request is awaiting review, instead of it looking like any other open issue.

You can also filter your Issues list to show only findings with a pending ignore request, making it easy to see and act on the queue of requests awaiting a decision without scanning every issue.

For API and integration users, the issues API now reports pending as part of an issue's ignore status, so you can distinguish open, pending, and ignored findings programmatically.

This enhancement will be rolled out gradually during the next 2 weeks.

Why we changed it?

Previously, a finding with a submitted-but-not-yet-approved ignore request looked identical to any other open issue.

There was no way to tell that a request was already in pending — which meant developers had no way to check whether their request had registered, and reviewers had no way to see pending requests from the view they already use to triage issues.

What does it mean to you?

If your organization uses Ignore Approval Workflow, pending ignore requests now appear automatically in the Issues page and issue details after your next scan — no configuration needed. The Pending Ignore filter is available alongside the existing Open and Ignored filters. No action is required to adopt this change.

Additional Information about Ignore Approval Workflow

https://docs.snyk.io/scan-fix-and-prevent/fix/prioritize-issues-for-fixing/ignore-issues/ignore-approval-workflow

Snyk Code October update

Improved

This update will be available on October 26, 2026.

Snyk Code reports significantly more findings in this update. Affected projects will report the additional findings on their next scan.

Snyk Code now analyzes more deeply and more accurately in Java, Kotlin, Go, TypeScript, JavaScript, Python, C#, PHP and Ruby.

Go, TypeScript and JavaScript

Snyk Code reads the Project's own configuration to resolve imports. For Go, it reads go.mod, which defines the module path that a project's packages import each other through. For TypeScript and JavaScript, it reads tsconfig.json and jsconfig.json, which define path aliases.

As a result, Snyk Code now analyzes these projects more accurately and with greater depth.

PHP

Snyk Code corrects boolean typing in PHP analysis. Previously skipped findings now appear across cross-site scripting, path traversal, SQL injection and other checks.

Java

Coverage is added or improved for these libraries:

  • Spring Data MongoDB

  • AWS SDK for Java, DynamoDB

  • AWS SDK for Java 2.x, DynamoDB

  • AWS SDK for Java 2.x, DynamoDB Enhanced Client

  • Apache Commons FileUpload

  • Google Cloud Big Query

Snyk Code adds a Mass Assignment rule for Spring applications. It reports request data that binds directly onto a database entity. Path traversal detection is wider.

More detection

Snyk Code reports additional findings in these areas:

  • Python: XML external entity injection.

  • JavaScript: deserialization, XML external entity injection and zip slip.

  • JavaScript, Bootbox: DOM-based cross-site scripting.

  • JavaScript, d3: DOM-based cross-site scripting.

  • C#: path traversal.

  • Go: SQL injection.

  • Go, AWS SDK for Go v2: path traversal through S3 object keys.

  • Ruby: path traversal, and a new server-side request forgery rule.

Template file analysis and serverless analysis

Snyk Code analyzes template files and serverless applications more accurately and with greater depth, building on the September update. Both will yield additional findings in projects that use template engines or serverless frameworks.

Learn more in the Snyk Code documentation.

Announcing Snyk CLI v1.1308.0

New

We are pleased to announce the latest stable Snyk CLI release, v1.1308.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:

  • HTML Reports

    • snyk code test and snyk secrets test can now generate an HTML report. Use --html to print it to stdout, or --html-file-output=<path> to write it to a file. This replaces the need for a separate snyk-to-html tool in most cases. Support for snyk test will be available in v1.1308.1.

  • Agent Scan (experimental)

    • The experimental snyk agent-scan command now reports risk indicators instead of issue codes. If you post-process its --json output, update your scripts to the new format.

  • Additional Reliability and Performance Improvements

    • Maven and Gradle SBOMs, and --print-graph, no longer stall on large multi-module builds and now finish seconds after the build tool exits. On projects with dependency cycles, the output may contain extra pruned: cyclic placeholder nodes. No packages or dependency edges are dropped.

    • Gradle projects with very deep inter-module dependency chains no longer fail with a stack overflow.

    • Projects built with Gradle 4.0 to 4.6 no longer fail to scan.

    • .NET scans fall back to legacy scanning when the .NET SDK isn't installed. They also handle projects restored in a different build directory, and work when global NuGet source-mapping rules are configured.

    • .NET scans no longer fail with NU1101 on SDK installs that lack the app host pack, such as distro-packaged SDKs.

    • .NET projects whose PackageReference uses a lowercase version attribute are now parsed correctly.

    • 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

Announcing Snyk CLI v1.1307.4

Improved

We are pleased to announce Snyk CLI release, v1.1307.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:

  • New experimental snyk studio command that sets up Snyk Studio in supported AI coding tools (Cursor, Claude Code, Codex, Copilot, Gemini, Kiro, and Windsurf), so the code they generate gets scanned in the background as it's written. This direct integration replaces the need for separate setup scripts (https://github.com/snyk/studio-recipes). Run snyk studio install --experimental to get started.

  • New snyk fix --agentic filtering flags: --severity-filter to fix only the severities you choose, --breakability-filter to fix only Open Source upgrades with the breakability you choose, and --exclude-ids to fix everything except the issue IDs you list.

  • snyk fix --agentic now keeps a failed fix's changes by default so you can review them, rather than reverting automatically. Pass --enable-revert to restore the automatic rollback behavior.

  • Fixed an issue where the --iac, --docker, --container, and --code flags on snyk test could be silently dropped for organizations on the unified test API, causing scans to fall through to an open-source test instead (which could fail with "No supported files found" or scan the wrong target). These flags now route to the correct scan again.

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

A change to the Snyk Code Priority Score

General availability

Snyk Code priority scores dropped by up to 200 points on September 1, 2026, for findings whose rule had a fix example.

What changed

A finding used to earn 200 of the 1,000 available priority score points when Snyk held a fix example for its rule. The August 17, 2026 release retired fix examples, and the scoring factor went with them. The removal became live on September 1, 2026.

Why

Fix-example availability describes Snyk's content coverage. It says nothing about the risk in your code. Two findings of the same severity could sit 200 points apart because one rule happened to have an example behind it. Priority score should rank findings by how urgently they need fixing, so we removed the factor.

What you saw

Snyk Code findings reordered when the factor came out. Every remaining scoring factor works as it did before, including severity, which still contributes the largest single share at up to 500 points. No finding was added, removed or re-rated.

We should have told you

The August 17 release notes said no action was required. That was wrong, and we apologize. We have added a check so that any future change to priority score appears in the release notes. The priority score documentation now lists the current factors.

Learn more in the Snyk Code priority score documentation.

Headshot of Sebastian Roth

Sebastian Roth | Senior Product Manager

Announcing Snyk CLI v1.1307.0

Improved

We are pleased to announce the latest stable Snyk CLI release, v1.1307.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:

  • Secrets

    • snyk secrets test now supports exclusions — add files or paths to the exclude section of your .snyk file to skip them during secrets scanning.

  • Container

    • Container scans now surface image provenance attestations by default, so signed-image provenance metadata appears in results without any extra flag.

  • .NET/NuGet

    • snyk test can now analyze already-restored .NET/NuGet projects fully offline and no longer requires .NET 6 to be installed.

  • MCP

    • The full Snyk MCP profile now includes Snyk Secrets.

  • Code & Secrets

    • SARIF suppressions now include reviewedOn and reviewedBy metadata.

  • AI BOM

    • snyk aibom test --severity-threshold now filters the displayed and JSON results by severity, not only the exit code.

  • Agent-optimized CLI

    • New experimental snyk agent command space — a scanning surface built for AI coding agents, with token-optimized output and ergonomics. snyk agent test runs Snyk Open Source, Code, and Secrets together.

  • Additional Reliability and Performance Improvements

    • Adds support for scanning pnpm v11 pnpm-lock.yaml lockfiles.

    • Fixes a crash when scanning dependencies of Gradle 7.4–8.2 projects.

    • Fixes a bug where arguments after -- (for example snyk test . -- -s settings.xml) were treated as scan targets, which could silently drop the Risk Score.

    • Fixes scanning of projects using Hex versions newer than 1.19.

    • Excludes the .git folder from file discovery, preventing intermittent scan failures caused by changes to .git contents during a scan

    • Prevents a possible connection leak when the Snyk API returns an error response.

    • 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 Code September Update

Improved

This update is available on September 14, 2026. It improves coverage and precision across Snyk Code: template files are analyzed, Java framework and library support is extended, detection gaps are closed in six languages, and .gitignore no longer hides committed files from analysis.

Template files

Snyk Code analyzes template files and follows data from your application code into the template. Cross-site scripting that only becomes exploitable where the template renders its output is now reported, with the data flow shown from the application through to the template.

Supported engines: Jinja2, Razor, FreeMarker, EJS, Handlebars, Pug, Thymeleaf, Twig, Mustache and Velocity.

Java

  • Apache CXF — the web services framework, including its HTTP transport.

  • OkHttp — the HTTP client.

  • Spring Security OAuth2 Client — OAuth2 and OpenID Connect authentication.

  • Google OAuth Client and Google API Client — Google authentication and API access.

  • MSAL4J — Microsoft identity platform authentication.

  • Apache Commons Collections — collection utilities.

  • Flyway — database migrations.

  • JAXB — XML binding.

  • SAP Commerce (Hybris) — FlexibleSearch queries, with parameter binding recognised as safe.

Coverage for these libraries is added or improved, resulting in improved data flow analysis.

Python

LangChain LiteLLM is recognised as a source of untrusted data.

Java 25

Java 25 source is analyzed.

Rule coverage improvements

Detection coverage is extended for Java, Kotlin, C#, Go, JavaScript and PHP — additional sources, sinks and unsafe API patterns, in particular for cryptography.

Expect additional true positives and fewer false positives.

Files matched by .gitignore

  • Committed files matched by a .gitignore rule are analyzed.

  • Secrets committed and later matched by a .gitignore rule are now detected. Git ignores only untracked files, so this brings Snyk Code and Snyk Secrets in line with Git.

  • These are pre-existing issues in code you already committed.

  • The change applies across all interfaces and cannot be disabled.

Required for CLI scans. Upgrade to Snyk CLI 1.1307.0 or later, available from 26 August. Earlier versions keep the previous behavior, so CLI results will differ from your SCM and web results. SCM imports and scans need no action.

What is unchanged

  • Untracked files matched by .gitignore remain excluded from analysis.

  • .snyk exclude patterns behave as before, and remain the way to exclude a path deliberately.

  • Severity levels and rule identifiers do not change.

Learn more in the Snyk Code documentation.

Tags:

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.

COBOL support for Snyk Code

New

COBOL support becomes generally available on August 17, 2026. Snyk Code brings SAST to your mainframe applications, scanning fixed-format COBOL across the integrations you already use, so mainframe code receives the same real-time, in-workflow security coverage as the rest of your stack. Detection is tuned with feedback from design-partner environments across large finance and mainframe estates.

What you can do

  • Scan COBOL applications for security issues alongside your other languages, with no separate workflow.

  • Catch real, actionable findings, with COBOL engagement in line with mainline languages.

  • Bring mainframe AppSec into the CLI, IDE, SCM, and PR-check integrations your teams already use.

Scope change at general availability

At general availability, the COBOL preview flag is removed and COBOL scanning runs automatically across all repositories. You may see new findings in repositories that were not scanned during the preview.

For design-partner customers

Thank you for shaping COBOL support during early access.

Learn more in the COBOL support documentation and the COBOL rules reference.

Headshot of Sebastian Roth

Sebastian Roth | Senior Product Manager

Tags: