Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

Security through obscurity is based on the idea that if attackers don’t know how a system works or even if it exists, they’ll have a harder time breaching it. Despite repeatedly broken implementations and lacking support from standards bodies, this concept continues to be widely used. Secret doesn’t always mean safe – and it can even give a false sense of security.

A critical heap buffer overflow vulnerability in the AWS C Common library was discovered autonomously through an AI-automated fuzz testing solution, CI Fuzz, and has been fully addressed with a patch. In this post, we explore the vulnerability and its potential impact on embedded systems.

Using strong cryptography is essential for data protection and application security, such as tasks required for hashing passwords (which, technically, isn’t classic cryptography for the sake of encryption). However, some legacy code may still be deployed to production using weak and outdated cryptographic algorithms that weren’t found. How can Snyk Code help you find these vulnerable applications?

Last November, the Open Web Application Security Project (OWASP) released its Top Ten List for LLMs and Gen AI Applications 2025, making some significant updates from its 2023 iteration. These updates can tell us a great deal about how the LLM threat and vulnerability landscape is evolving - and what organizations need to do to protect themselves.

We are excited to announce the launch of Seal OS, the first holistic solution designed to automatically fix vulnerabilities in both Linux operating systems and application code. Seal OS delivers long-term support for a wide range of Linux distributions, encompassing Red Hat Enterprise Linux, CentOS, Oracle Linux, Debian, Ubuntu, Alpine, and more. This support extends to various deployment models, including containers, virtual machines, and bare metal installations.

CWE, or Common Weakness Enumeration 73, occurs when an unauthorized user gains external access to control a file in your system. CWE provides a standardized language and classification system to help identify, understand, and mitigate vulnerabilities in software and systems. External Control of Filename or Path is a vulnerability that occurs when an application allows an external entity to influence the selection of a file or directory location within the system.

Today’s risk environment is constantly evolving as threat actors exploit the complexity of modern software. That's why it's crucial to prioritize security throughout the entire application lifecycle, from beginning to end. However, many software teams only start thinking about security when application development is well underway.

Let’s be real—spreadsheets have been the go-to tool for vulnerability management for years. They’re easy to set up, familiar, and flexible. But here’s the hard truth: they’re costing you time, accuracy, and security. Imagine trying to track thousands of vulnerabilities across an ever-changing attack surface using a tool designed for budgeting, not security.