Skip to main content

3 posts tagged with "security scan"

View All Tags

Atlas v1.4: Security Scanning, Database Profiler, Agent Skills, Drift Detection, and More

· 37 min read
Ariel Mashraki
Building Atlas

Hey everyone!

We're excited to announce Atlas v1.4. This release brings security scanning to your databases: the new atlas security scan command reports the CVEs affecting your database servers and extensions, from the CLI, CI, or Kubernetes. It also introduces agent skills, a profiler for the Atlas testing framework that works on production-like data, and drift checks between deployments.

Here is what you can find in this release:

  • Security Scanning for Databases - Vulnerability detection for your database servers and extensions with atlas security scan, from CI to Kubernetes, and blast-radius checks for roles.
  • Atlas Agent Skills - Teach Claude Code, Codex, Cursor, and GitHub Copilot to plan, lint, and test schema changes with Atlas.
  • Profiler for the Testing Framework - Measure the locks, rewrites, and space of migrations, queries, and database code, over a masked Amazon RDS snapshot, CSV files, or synthetic rows. In preview.
  • Drift Detection Between Deployments - atlas migrate drift reports every object that diverged from your migrations, for one database or every tenant.
  • Schema Repositories in Your Own Storage - Store schema repositories in your own S3, GCS, or Azure Blob Storage bucket, or an OCI registry, instead of Atlas Cloud.
  • Database Driver Improvements - Snowflake governance policies, SQL Server linked servers and filegroups, PostgreSQL temporal keys, Databricks metric views, Redshift datashares, and more.
  • Atlas Binaries Are Moving to atlasbinaries.com - Starting December 2026, release.ariga.io redirects to atlasbinaries.com. Direct downloads only need the new hostname.

PostgreSQL 19: Security Changes and Preparing with Atlas

· 13 min read
Noa Rogoszinski
DevRel Engineer

PostgreSQL 19 is scheduled for general availability on November 19, 2026, one week after PostgreSQL 14 reaches end of life on November 12. From then on, servers on PostgreSQL 14 get no more security fixes. Versions 15 through 18 are still supported, but version 19 will be supported the longest, into late 2031.

This post covers what version 19 changes for security and the schema objects that block an upgrade to it, and how to use the week before GA to prepare with Atlas: scan your servers for their versions and CVEs, keep upgrade blockers out with schema rules, and apply the same schema, roles, and grants to the new instance from code.

ClickHouse CVEs: Find Vulnerable Servers with Atlas

· 10 min read
Noa Rogoszinski
DevRel Engineer

On October 30, 2026, ClickHouse published CVE-2026-116366, an unauthenticated remote code execution vulnerability in ClickHouse Server. Under certain conditions, a user with network access to the server can run arbitrary code on it without logging in. ClickHouse rates it Critical, with a CVSS v4.0 score of 9.5.

ClickHouse Cloud and BYOC deployments are already patched. Self-managed servers are not, and finding every one of them across your environments is the hard part. Atlas can do that for you: atlas security scan now checks the server version of each ClickHouse server against the Atlas Security Graph, and reports every published CVE that affects it, this one included, along with the release that fixes it.