Snyk now supports Alpine 3.12

Snyk now supports the newest release from Alpine - 3.12. Rescan to get started.

Prioritize the vulnerabilities that are reachable from your code

Customers who use Snyk to scan their Java Maven applications can now understand which vulnerabilities have a path from the source code to the vulnerable function and prioritize accordingly.

Reachable Vulnerabilities is Beta now and available for Java Maven projects scanned via the CLI. Run snyk test --reachable in order to start using.

Read more about Reachable Vulnerabilities in our documentation and read how it fits with all of our new prioritization features.

More accurate prioritization for Kubernetes projects

For Snyk Container customers using our Kubernetes integration we're providing even more context to our new Priority Score. Where we find vulnerable packages running in poorly configured workloads we'll increase the priority, making it even easier to identify high-risk vulnerabilities.


Read more about the new Snyk prioritization features and find our how to use the Snyk Container prioritization functionality in the documentation.

Snyk Priority Score

We're excited to formally introduce Snyk Priority Score, a new 0-1000 score encompassing not only basic CVSS, but also a range of other contextual factors that allow the score to reflect the value of fixing a vulnerability in the context of your project.

This not only allows you to focus your effort for the fastest risk reduction, but also the best ROI on valuable time and effort!

Read more about the score in the documentation, or find out how this fits in with a suite of other new Snyk prioritization functionality.

Exploit maturity now available for Linux

We are happy to update that exploit maturity information is also now available in Alpine, Ubuntu and Debian. Check out documentation to learn more!

IntelliJ Plugin now supports Gradle and Licences

Happy to share that we’ve just released a new version of the the Snyk Vulnerability Scanner plugin for IntelliJ!

The Snyk Vulnerability Scanner helps you find and fix security vulnerabilities and licence issues in your projects, all from within the IDE.

The new version is based on Snyk CLI and has an integral support for Gradle (in addition to Maven) and licenses.

To learn more about the the new version, visit the plugin page, at JetBrains marketplace.


Detect misconfigurations in Helm Charts

We're continuing to expand our new infrastructure as code features, with support for detecting security misconfigurations in Helm Charts now available to all. See the blog post for all the details.

Screenshot 2020-03-19 at 11.09.07.png

Tag your projects using the API

It's now possible to tag your projects via the API! 🎉 Project tags allow you to label your projects in any way you like, such as by team, risk status, or even the type of applications the projects are used by. You can then use the new API to filter all the projects that have the same tag.

For more information on how to use project tags, head on over to the documentation.

This feature will be available in the UI soon, but until then, happy tagging!

Snyk Broker Security Fixes

We have introduced several security fixes to our open source Broker. We’d like to thank Wing Chan of The Hut Group that responsibly disclosed the issues to us via our bug bounty program.

These issues pertained to increased privileges available to specific internal Snyk Personnel only. All issues were patched for all supported SCMs in version 4.80.0 of the Broker. We also have taken steps to improve the auditability of the Broker code, and have also improved both client and server-side logging in order to improve customer and Snyk visibility of activity on the service.

APIs for creating a new Git integration

Happy to share that we've just released new APIs that will allow you to create new Git integrations and to “Brokerize” existing integrations without having to contact Snyk support 🎉

All Git integrations are supported: GitHub, GitHub Enterprise, BitBucket Cloud, BitBucket Server, GitLab and Azure Repos.

With the new set of APIs, you'll be able to:

  1. Create new integration (Brokered / non Brokered)
  2. "Brokerize" an existing integration
  3. "Debrokerize" an existing integration

To find out more about the new endpoints, please take a look at our API docs: