Last updated: August 19, 2026 at 1:47 AM UTC
All 741 Vulnerability 286 Breach 129 Threat 319 Defense 7
Tag: secrets (2 articles)Clear

Critical Rails flaw turns an image upload into a read of server secrets

The Ruby on Rails team disclosed a critical flaw in Active Storage that lets an unauthenticated attacker read arbitrary files by uploading a crafted image. Tracked as CVE-2026-66066 and scored 9.5, it affects applications that use the libvips image library and accept image uploads from untrusted users, which is the default in modern Rails. Active Storage passes uploads to libvips without disabling its unsafe image loaders, so a malicious file can read the server process environment, exposing the secret key base, database passwords, cloud storage keys, and API tokens. Those secrets can enable code execution and lateral movement. Rails is not aware of exploitation, and full details are held until August 28.

Check
Determine which Rails apps use Active Storage with libvips and accept untrusted image uploads, upgrade to the fixed releases, and ensure libvips is version 8.13 or newer.
Affected
Rails 7.0 through 8.1 applications using libvips Active Storage with untrusted image uploads (CVE-2026-66066); an unauthenticated upload can read server secrets, opening the door to code execution.
Fix
Upgrade Rails, update libvips to 8.13 or later, and rotate every secret the app can read, including the secret key base, master key, storage and database credentials, and third-party tokens.

Ghostcommit hides secret-stealing instructions inside images to slip past AI reviewers

Researchers at the ASSET Research Group demonstrated Ghostcommit, an attack that hides malicious instructions inside a PNG image so AI code reviewers miss them entirely. A harmless-looking conventions file points the coding agent to the image, whose rendered text tells the agent to read the repository's .env file and encode its secrets as a list of numbers written into the code. Because tools like CodeRabbit and Bugbot skip image files by default, the pull request passes review clean; the trap springs later when a developer asks the agent for an unrelated task. The outcome depended on the tool wrapping the model: some agents leaked secrets, while Claude Code refused.

Check
Review how your AI code reviewers and coding agents handle images and convention files like AGENTS.md, and check whether reviewers inspect image contents rather than skipping them as opaque binary files.
Affected
Teams using AI code reviewers that skip images and coding agents that auto-follow repository convention files; a merged pull request can later drive an agent to read .env and leak its secrets.
Fix
Configure AI reviewers to inspect image contents, treat convention files and repo content as untrusted input, keep secrets out of agents' reach, and require human review before agents read sensitive files.