Last updated: November 2, 2026 at 1:20 PM UTC
All 957 Vulnerability 399 Breach 144 Threat 407 Defense 7
Tag: secret-theft (5 articles)Clear

Gheist campaign uses stolen GitHub tokens to leak private repository secrets through Actions logs

Wiz detailed Gheist, an automated campaign that uses stolen GitHub tokens to push a sync-check.yml workflow to a short-lived ci-sync branch, then reads the job's secrets from the run log. The workflow base32-encodes every secret the job can access, defeating GitHub's log masking, downloads the log through the API, and deletes the run seconds later, so nothing leaves through an attacker server. Since September 15, Wiz recovered more than 13,500 planted branches across more than 850 compromised accounts, succeeding in private repositories and GitHub Enterprise, where GitHub's hold on suspicious runs does not apply. Rotate every reachable secret, since deleting branches does not undo exposure.

Check
Hunt for ci-sync branches containing only a sync-check.yml workflow and runs deleted shortly after finishing, and rotate every secret those repositories could access.
Affected
Private GitHub repositories and Enterprise servers reachable with a stolen token can have all their accessible secrets leaked through a planted workflow's run logs.
Fix
Rotate repository, organization, and environment secrets, revoke the tokens that pushed commits, prefer short-lived fine-grained tokens, and require reviewers on environments holding production secrets.

Attackers backdoor five OVHcloud CLI releases on GitHub to steal developer secrets from disk

OVHcloud disclosed that five releases of its open-source command-line tool, versions 0.11.0 through 0.15.0, were backdoored on GitHub to steal secrets from disk. An attacker who had controlled a developer's GitHub account for more than half a year modified the existing releases because GitHub release immutability was disabled, uploading locally built malware without touching the CI/CD pipeline, and planted a hidden preinstall.js loader. OpenSourceMalware linked it to the GlassWorm campaign. The malicious builds covered macOS, Linux, and Windows and were live from 14:47 to 16:21 UTC on October 19. Source builds and Docker images were unaffected, and users should revoke secrets.

Check
Identify machines that ran OVHcloud CLI versions 0.11.0 through 0.15.0, remove or update the binary, clean the systems, and revoke all secrets they could reach.
Affected
Developers who installed the backdoored OVHcloud CLI releases on macOS, Linux, or Windows had secrets stolen from disk by locally built malware uploaded to GitHub.
Fix
Update to a clean OVHcloud CLI release, rotate all exposed secrets, enable GitHub release immutability on your own repositories, and inspect hosts for the preinstall.js loader.

Nearly one in ten exposed LiteLLM AI gateways still accept the example admin key

Researchers at Wiz found that nearly one in ten internet-facing LiteLLM servers still accept "sk-1234," the example administrator key printed in LiteLLM's own setup guide. LiteLLM is an open-source AI gateway that sits between an organization's apps and the model providers it pays for, and that admin key unlocks every stored provider API key; in Wiz's tests it even reached the cloud identity credentials of the host machine. The finding accompanies a cluster of exploited LiteLLM flaws that attackers have used to run code, steal secrets, and deploy crypto miners, with one ransomware group and a Microsoft-documented breach among them. Microsoft's advice is to treat AI gateways as top-tier secrets stores.

Check
Change the LiteLLM admin key immediately if it is still the default sk-1234, which needs no upgrade, and upgrade LiteLLM to 1.84.0 or later to close the exploited code-execution and auth-bypass flaws.
Affected
Organizations running internet-facing LiteLLM gateways, especially with the default admin key or on unpatched versions; an attacker can read every stored provider API key, reach cloud credentials, and sometimes execute code.
Fix
Replace default keys, patch to the latest LiteLLM, take gateways off the public internet, rotate all provider, cloud, and database credentials it can reach, and treat AI gateways as tier-zero secrets stores.

Attackers probe LiteLLM AI gateways to steal cloud and model provider secrets

Attackers are actively probing LiteLLM deployments for an authorization flaw that turns a low-privilege account into full control of the AI gateway. Tracked as CVE-2026-35029 and affecting versions before 1.83.0, the flaw is a missing permission check on the configuration-update endpoint, so a read-only user can change settings reserved for administrators. LiteLLM sits between applications and model providers and stores provider API keys, database details, and admin credentials, making it a rich target. By abusing configuration writes, an attacker can extract secrets from server environment files and even reset the dashboard login to seize admin access. Researchers recorded thousands of probing requests, some directly attempting to read known secret files.

Check
Upgrade LiteLLM to 1.83.0 or later, restrict access to its control plane and configuration endpoints, and rotate any provider, cloud, or database secrets the gateway could expose.
Affected
Organizations running LiteLLM before 1.83.0 as an AI gateway (CVE-2026-35029); a low-privilege authenticated user can modify configuration, read environment secrets, and escalate to administrator, exposing stored model provider and cloud credentials.
Fix
Patch, segment and firewall the LiteLLM control plane away from untrusted users, enforce least privilege, store secrets outside reachable environment files, rotate exposed keys, and monitor configuration endpoints for unauthorized changes.

Attackers exploit critical Langflow and Rails flaws to harvest secrets

VulnCheck reported active exploitation of two critical flaws, one in the AI workflow builder Langflow and one in Ruby on Rails. The Langflow bug, CVE-2026-0768, scored 9.8, lets an attacker run arbitrary Python code as root through improper input validation. The Rails bug, CVE-2026-66066 and nicknamed KindaRails2Shell at 9.5, lets an unauthenticated attacker read arbitrary files by uploading a crafted image that exploits a mismatch between Active Storage and the libvips image library, leaking secrets like the Rails master key and cloud credentials and ultimately enabling code execution. Detections jumped from about 50 to 360 within a day, with attackers querying environment variables for OpenAI and AWS keys and probing SSH access.

Check
Patch Langflow and Ruby on Rails to fixed versions now, and rotate any secrets an attacker could have read, including the Rails master key, database passwords, cloud credentials, and API keys.
Affected
Internet-facing Langflow servers (CVE-2026-0768) and Rails apps using Active Storage with libvips (CVE-2026-66066); attackers can run code as root or read files leaking the master key, cloud credentials, and API tokens.
Fix
Update both immediately, rotate exposed secrets, restrict internet exposure of Langflow, review logs for environment-variable probing and image-upload abuse, and treat any exposed instance as potentially credential-compromised.