Skip to content

⚙️ DevSecOps248

ListGrid
What you seeeverything
RecentOldestAddedA–Z
All types248Articles107Repos49Write-ups48Threads15Advisories11
Tools8Talks5Papers2Videos2Other1
⚙️ DevSecOps
bleepingcomputer.comarticle

CISA says max severity GitLab flaw now exploited in the wild

CVE-2026-97229 is a maximum-severity GitLab flaw in the CI/CD Regular Expression Compiler, caused by an integer overflow, that lets unauthenticated attackers run code via a crafted regular expression. CISA added it to the KEV Catalog and ordered federal agencies to patch under BOD 26-04. GitLab fixed it in CE/EE 19.4.2, 19.3.5 and 19.2.8, and Shadowserver tracks about 2,800 exposed CE instances.

GitLab
CVE-2026-97229CVE-2026-0723CVE-2026-110264+10

AppSec, DevSecOps, Threat Intel· Published and added 30 Oct 2026

securityweek.comarticle

Max-Severity GitLab Vulnerability Exploited Against Alpine Linux

CVE-2026-97229 is a CVSS 10 code execution flaw in Onigmo, Ruby's regular expression engine, reachable through crafted CI/CD configuration in GitLab. Attackers used it against Alpine Linux's GitLab on 20 and 21 October 2026 and failed; Alpine rebuilt the instance and found no tampering with aports or packages. Self-managed installs with their own Ruby need Ruby 3.3.13, 3.4.12 or 4.0.9, not just GitLab 19.3.6. CISA added it to KEV.

GitLabRubyOnigmo+2
CVE-2026-97229CISA KEVBOD 26-04+1

AppSec, Threat Intel, DevSecOps· Published and added 30 Oct 2026

vulncheck.comtool

VulnCheck - Outpace Adversaries

VulnCheck Open Source is an index of VulnCheck's open-source tooling for its vulnerability and exploit intelligence. It lists a Python API client, a CLI, a GitHub Action for CI/CD, go-exploit (a Go exploit framework), an MCP server for delivering intelligence to AI clients, and VulnCheck Insights, a Chrome extension that highlights CVEs, CPEs and PURLs on web pages and enriches them. The page gives only one-line descriptions.

GoPythonGitHub Actions+2
VulnCheckgo-exploitVulnCheck Insights+2

Offensive Security, DevSecOps· Added 29 Oct 2026

opensourcemalware.comtalk

The OpenSourceMalware Show #27

The OpenSourceMalware Show #27 (28 October 2026) is a podcast episode with transcript. It covers the Brotli decoder bug (CVE-2026-111497) vendored in C code across Python, Rust and PHP, and how to find copies via decode.c. It also covers the LiteLLM v1.107.0 compromise from an unrevoked admin key and a relaxed release control, and the MALFEX npm campaign hiding payloads in PNG-header files, plus an AGENTS.md lure and DPRK fake fonts in TTF/OTF.

BrotliLiteLLMnpm+3
CVE-2026-111497Node2ShellPHP2Shell+10

Supply Chain, Threat Intel, DevSecOps· Published and added 29 Oct 2026

endorlabs.comarticle

ADLC metrics: How to measure agentic development security | Endor Labs

ADLC metrics is an Endor Labs guide to measuring security in the agentic development lifecycle, where AI coding agents write much of the code. It defines formulas across five categories: AI supply chain visibility, agent action security, agent-generated code, package risk and developer flow. It argues for normalizing findings per merged change, tracking pre-execution blocks, and building a six-to-eight metric scorecard.

Claude CodeCodexCursor+3
ADLCOWASP Top 10 for LLM ApplicationsAgent Security League+4

AI Security, AppSec, DevSecOps· Published and added 29 Oct 2026

endorlabs.comarticle

The ADLC maturity model: 5 stages of agentic development security | Endor Labs

The ADLC maturity model is a proposed five-stage framework from Endor Labs for scoring security controls over coding agents, from unmanaged experimentation to continuous verification. Each stage has requirements on two tracks, agent actions (shell commands, MCP calls, package installs) and agent output (code, dependencies, secrets). It sets stage 3 at deterministic hooks that block actions, gives evidence-based assessment questions, and lists traps such as relying on prompt-level rules.

Endor LabsAURIModel Context Protocol+2
ADLC maturity modelOWASP SAMMOWASP Top 10 for LLM Applications+5

AI Security, GRC, DevSecOps· Published and added 28 Oct 2026

endorlabs.comarticle

How to evaluate ADLC security solutions: A buyer's checklist | Endor Labs

Buyer's checklist from Endor Labs for evaluating security tools in the agentic development lifecycle (ADLC), where AI coding agents write code and take actions such as package installs, CI edits and tool calls. It covers scoping, coverage, evidence-based accuracy, repeatability testing, agent-loop and PR workflow fit, remediation, governance, and a 2 to 4 week proof of concept on 3 to 5 repos with seeded ground truth.

Endor LabsAURIModel Context Protocol+3
ADLCIDORNIST SSDF+1

AppSec, AI Security, DevSecOps· Published and added 28 Oct 2026

x.comthread

Kizuno18 (@Kizuno18) on X

Thread by Kizuno18 on the move from local stdio/Docker Model Context Protocol servers to remote HTTP/SSE endpoints in enterprise infrastructure. It names three trade-offs: credential boundary inversion (short-lived OAuth/JWT tokens instead of long-lived admin tokens on workstations), tool schema bloat solved by deferred discovery, and governance via HCP Terraform policy-as-code (Sentinel/OPA), audit trails and approvals. It is opinion, with no data or implementation detail.

Model Context ProtocolTerraformDocker+2
Sentinelblast radiuspolicy-as-code+1

AI Security, Identity & Access, DevSecOps· Added 29 Oct 2026, published 27 Oct 2026

hackers-arise.comarticle

Pentesting: Twelve Caesars – Community Tools for Offensive Security

Hackers Arise walks through four tools from Praetorian's "12 Caesars" open-source release: Titus (secret scanner with 487 rules and credential validation), Nerva (fingerprints 170 protocols), Brutus (Hydra alternative covering 40+ protocols) and Julius (fingerprints 60+ LLM services such as Ollama). It shows download and run commands in a Kali lab and how the tools chain together. The tools are Go single binaries; the post notes an exposed Ollama on port 11434 allows unauthenticated model use.

GoKali LinuxOllama+3
Praetorian12 CaesarsTitus+4

Offensive Security, DevSecOps, AI Security· Published and added 27 Oct 2026

aikido.devarticle

How to patch PHP2Shell with free Aikido Images

Aikido Images are free patched PHP container images on public ECR (public.ecr.aws/aikido-dev/php) that backport the PHP2Shell fixes for CVE-2026-109618 and CVE-2026-109619 into release lines 5.5 to 8.5, except 8.0. Upstream fixed 8.2 to 8.5 in October 2026 and left 8.1 and older unpatched. The post shows docker pull and Dockerfile FROM changes, then rebuild, restart, session.upload_progress.enabled=0 and compromise checks.

PHPDockerAikido Security+1
CVE-2026-109618CVE-2026-109619PHP2Shell

DevSecOps, AppSec· Published and added 26 Oct 2026

x.comthread

David Gutierrez | Eng (@david_x_ai) on X

Thread on two October 2026 npm compromises: @subql/common 5.8.3 (5 October), published through GitHub Actions OIDC Trusted Publishing after the attacker tampered with the publish workflow, and tensorlake 0.5.144 (8 October), published by the project's own release workflow with valid provenance for about 1 hour 40 minutes. Both ran on install and stole cloud, GitHub, Kubernetes, Vault, SSH and .env credentials; tensorlake also took AI tool and MCP config. Its payload installed a gh-token-monitor service that deletes the home directory if the stolen GitHub token is revoked, so remove it before rotating.

npmGitHub ActionsGitHub+3
@subql/commontensorlakegh-token-monitor+3

Supply Chain, DevSecOps· Added 27 Oct 2026, published 26 Oct 2026

wiz.ioarticle

The Pwn Request Reckoning: What Still Works Against GitHub Actions

The Pwn Request Reckoning is a Wiz post updating the GitHub Actions pull_request_target threat model for 2026. It covers what GitHub's checkout protections, read-only cache tokens and event policies block, and what still works. Remaining paths: SHA-pinned pre-backport actions/checkout, custom checkout scripts, issue_comment and repository_dispatch triggers, script injection, artifact poisoning, self-hosted runner state and allow-unsafe-pr-checkout. It ends with grep and zizmor audit steps.

GitHub ActionsGitHubzizmor+1
pwn requestscript injectionartifact poisoning+2

DevSecOps, AppSec· Published and added 26 Oct 2026

x.comthread

Ricardo Arguello (@RicardoIQSource) on X

Post by RicardoIQSource on breaches of developer platforms aimed at AI provider keys. It reports OpenCode (17 October, provider keys in its Console) and Zeabur (14-15 October, 3.2M environment variable records, admin tokens stored in plaintext since January 2024) as following the Railway incident. It claims three platforms were hit in eight days and links a blog with a timeline and remediation steps.

OpenCodeZeabur
RailwayZeabur breachplaintext admin tokens

Threat Intel, DevSecOps· Added 29 Oct 2026, published 26 Oct 2026

x.comthread

alex lee (@alexlee20122022) on X

Gheist is a GitHub campaign disclosed by Wiz in October 2026. Stolen tokens push ci-sync-XXXXXX branches with a sync-check workflow that dumps repo secrets base32-encoded to evade log masking, fetches the logs via API, then deletes the run. 13,500+ branches and 850+ accounts were hit since 15 September. Public repos are protected by the approval hold; private and Enterprise repos are not. The thread lists IOCs (.gdmp_pat files, "gheist" user agent, "ci: sync config" commits) and rotation steps.

GitHub ActionsGitHubWiz+2
Gheistci-sync branchsync-check.yml+3

DevSecOps, Threat Intel, Supply Chain· Added 26 Oct 2026, published 25 Oct 2026

wiz.iowriteup

Gheist: Attempted Scaled Abuse of Stolen GitHub Tokens Stumbles

Gheist is a campaign tracked by Wiz Research since 15 September 2026 that uses stolen GitHub tokens to push a sync-check workflow on ci-sync-* branches in every reachable repository. The workflow prints base32-encoded secrets into logs, which the tool downloads through the GitHub API and then deletes. Over 13,500 branches from 850+ accounts were recovered. The post covers the two tool variants, a buggy self-hosted runner payload, GitHub's approval hold (which does not cover private repositories), overlaps with other campaigns, hunting queries, IOCs and hardening steps.

GitHubGitHub ActionsAWS+3
GheistGhostActionPolinRider+6

Threat Intel, DevSecOps, Blue Team & Detection· Published and added 25 Oct 2026

x.comthread

The Hacker News (@TheHackersNews) on X

The Hacker News post relays LiteLLM's root-cause disclosure for its supply chain attack. A master key leaked on GitHub in May was never revoked. Attackers used it to reach the Agent Platform, steal a GitHub owner token, and publish a malicious PyPI release in October. A reply says the agent tool held the org owner's personal CLI login, which skips GitHub's 2FA re-check.

LiteLLMPyPIGitHub
CWE-798

Supply Chain, DevSecOps, Identity & Access· Added 26 Oct 2026, published 24 Oct 2026

x.comthread

Prasenjit Sarkar (@stretchcloud) on X

Post on the LiteLLM supply-chain compromise. Attackers spent eleven days in the GitHub org, ran a workflow on a throwaway branch to take twenty secrets including a GitHub App private key, then used stolen GitHub CLI OAuth tokens to publish malicious release 1.107.0 from a lookalike Berri-AI repo. A Python startup file harvested sixteen credential categories and LiteLLM proxy Postgres provider keys. Socket flagged the wheels in seven minutes.

LiteLLMPyPIGitHub Actions+3
Berri-AIBerriAILiteLLM 1.107.0+3

Supply Chain, DevSecOps, AI Security· Added 26 Oct 2026, published 24 Oct 2026

socket.devwriteup

New Evidence Shows LiteLLM Secret-Stealing Workflows Ran 11 Days Before Supply Chain Attack

Socket's Threat Research team reports that malicious cache.yml workflows ran in the BerriAI/litellm repository on 10 and 12 October 2026, eleven days before the 21 October release attack that published litellm==1.107.0. Each commit pushed to a short-lived ci-tmp-<hex> branch, then deleted it, sending base64-encoded CI secrets to webhook.site. Evidence comes from Actions metrics and environment deployment records; 20 secret names were exposed.

LiteLLMGitHub ActionsGitHub+3
ci-tmp branchescache.ymllitellm==1.107.0+6

Supply Chain, DevSecOps, Blue Team & Detection· Published and added 23 Oct 2026

x.comthread

Rafter (@RafterSecurity) on X

Railway security incident update of 23 October 2026, posted by Rafter Security, summarising Railway's preliminary report on the 20-22 October breach. Up to 1.85% of workspaces (about 100,000) may have had environment variables exposed. Attackers reportedly targeted AI provider API keys, possibly for model distillation. Some encrypted secrets were accessed and a subset decrypted. Railway says the attacker was removed by 22 October at 03:32 UTC, and the forensic investigation continues.

Railway
model distillationRafter Security

Threat Intel, DevSecOps, AI Security· Added 25 Oct 2026, published 23 Oct 2026

endorlabs.comarticle

ADLC Security Best Practices for Teams Shipping with Coding Agents | Endor Labs

ADLC Security Best Practices is an Endor Labs guide to controlling what AI coding agents can access, run, install and ship. It covers inventorying agents and MCP servers, sandboxing, pre-execution hooks instead of AGENTS.md rules, install-time package checks against slopsquatting and malware, reachability-based triage of agent PRs, and CI/CODEOWNERS protections. A five-step worked example and coverage metrics are included.

Model Context ProtocolClaude CodeCursor+3
slopsquattingindirect prompt injectiontool poisoning+5

AI Security, Supply Chain, DevSecOps· Published and added 23 Oct 2026

blog.railway.comadvisory

Preliminary Report Oct 21st Security Incident

Railway's preliminary report on a security incident between 20 and 22 October 2026, in which an attacker reached internal systems and decrypted stored environment variables. At most 1.85% of workspaces (about 100,000) were confirmed affected. The attacker was after AI provider API keys for distillation. Railway notified vendors such as GitHub and Anthropic, rolled all keys, moved to single-tenant builders and advised customers to rotate secrets. Exploit details are withheld.

RailwayGitHubGitLab+3
distillation attacksabliterated modelsSpaceXSI

Threat Intel, DevSecOps, Blue Team & Detection· Added 24 Oct 2026, published 23 Oct 2026

securityweek.comarticle

LiteLLM Compromised in Fresh Supply Chain Attack

LiteLLM version 1.107.0 was published with malware to PyPI and Docker Hub on October 21, for about three hours and roughly 49,000 downloads. Attackers used GitHub CLI OAuth tokens, likely leaked through Claude Code into LiteLLM logs, to disable branch protections, redirect the releaser to a lookalike repository and sign poisoned artifacts. The payload is an infostealer and RAT; Wiz saw Amazon Bedrock abuse. The last clean version is 1.106.2.

LiteLLMPyPIDocker+3
Berri-AI/litellmLLMjackingdead drop+1

Supply Chain, DevSecOps, AI Security· Published and added 23 Oct 2026

stepsecurity.ioarticle

eMudhra / emSign CA Compromise: What Python, pip, and CI/CD Users Need to Update

Guidance on the October 2026 eMudhra / emSign CA incident, where eight intermediate CA certificates had private keys generated with insufficient randomness. It explains why updating certifi alone does not fix pip's vendored bundle, and lists fixed versions (certifi 2026.10.19, pip 26.2.2, Python 3.15.1, 3.14.9, 3.13.17). StepSecurity's OpenSSL 4.0.3 tests showed the older bundle accepted seven emSign paths, while both corrected bundles rejected all fourteen.

pipPythoncertifi+3
eMudhraemSigncertificate authority compromise+3

Supply Chain, DevSecOps· Published and added 22 Oct 2026

github.comrepo

Spectrmachina/Ztrust

ZTrust is a Python supply-chain scanner that checks manifests, lockfiles, source and GitHub workflows for vulnerable or malicious dependencies (via OSV.dev), typosquats, leaked secrets, unsafe lockfiles and risky CI patterns such as pwn requests and script injection. It outputs console, JSON and SARIF 2.1.0 and ships as a GitHub Action. It also includes a FastAPI bounty service using commit-reveal and shielded Zcash payouts for researchers.

PythonGitHub ActionsOSV+3
xz-utilstj-actions/changed-filesevent-stream+3

Supply Chain, DevSecOps· Added 27 Oct 2026, published 22 Oct 2026

x.comthread

Dark Web Intelligence (@DailyDarkWeb) on X

LiteLLM suspects its October 21 release compromise began with Claude Code responses containing GitHub CLI OAuth tokens that were written to logs of an internet-facing internal LiteLLM gateway. Attackers allegedly stole those tokens, used an organization-owner token to disable branch protections, and pushed poisoned artifacts from a lookalike repository. How they entered the gateway is unconfirmed, and this is not a proven Claude Code vulnerability.

LiteLLMClaude CodeGitHub+1
LiteLLM release compromiselookalike repositorybranch protection bypass

Supply Chain, DevSecOps, AI Security· Added 25 Oct 2026, published 22 Oct 2026

x.comthread

Muscle AI (@themuscleai) on X

Post on the LiteLLM 1.107.0 PyPI compromise published 21 October 2026 and quarantined about 1 hour 43 minutes later. A malicious .pth file ran at Python startup and stole cloud credentials, private keys, browser data and AI tool auth files, then POSTed a tarball to an attacker endpoint. The author says attackers used stolen GitHub CLI OAuth tokens to push a trojanized commit chain and build official wheels. It lists five defenses: hash-pinned lockfiles, per-tool capped keys, release cooling periods, secret isolation and egress monitoring.

LiteLLMPyPIPython+3
TeamPCPcook.pth

Supply Chain, DevSecOps, AI Security· Added 23 Oct 2026, published 22 Oct 2026

aikido.devarticle

eMudhra CA compromise: eight private keys, and one of them is 4

eMudhra's eight intermediate CA certificates, chaining to emSign ECC Root CA - G3, had private keys below 256 (one is 4), disclosed on 17 October 2026 by a researcher known as Wayne. Browsers and Microsoft blocked them via revocation pushes, but curl, git, containers, language runtimes and IoT may still trust them. The post gives patched ca-certificates versions, test commands and the timeline.

cURLDockermacOS+3
eMudhraemSign ECC Root CA - G3Wayne+6

Supply Chain, DevSecOps· Published and added 22 Oct 2026

adversa.aiarticle

Is Claude Code safe for the enterprise? What the official settings cover, and what they don't

Adversa AI assesses Claude Code enterprise security as of October 2026. Managed settings bind only Claude Code, can be edited by local admins, and are not read by Anthropic-hosted cloud sessions. Auto mode misses 17% of risky actions in Anthropic's test set. The article covers attacks on the harness (CVE-2025-59536, CVE-2026-21852, TrustFall, SymJack, GhostApproval) and recommends credential, egress, isolation and monitoring controls.

Claude CodeAnthropicCursor+2
CVE-2025-59536CVE-2026-21852TrustFall+7

AI Security, DevSecOps· Published and added 22 Oct 2026

x.comthread

SecureChap (@SecureChap) on X

Post describing a LiteLLM 1.107.0 PyPI compromise in which attackers used stolen GitHub CLI OAuth tokens from three engineers to trigger and approve the project-releaser workflow, producing eight malicious wheels and a tampered tarball. The wheels drop cook.pth, which runs at Python startup, and privcollect steals cloud tokens, keys, browser data, AI configs and LiteLLM proxy credentials, exfiltrating to litellm[.]dev/healthcheck. A second daemon polls a GitHub domain.txt hourly for new domains to fetch and execute. PyPI yanked the package the same day. The post is a single unsourced tweet.

LiteLLMPyPIpip+3
cook.pthprivcollectlitellm[.]dev+2

Supply Chain, DevSecOps, Threat Intel· Published and added 22 Oct 2026

blog.railway.comadvisory

Railway Security Disclosure

Railway's security disclosure of 21 October 2026 says an unauthorized third party may have accessed encrypted customer environment variables and decrypted some of them. Railway links it to a series of attacks on platform companies aimed at compromising AI inference providers, and has asked upstream providers to revoke keys. It tells all users to roll every environment variable, API key and registry credential, and it paused all deployments. The notice gives no technical details of the intrusion.

Railway
Railway security incident October 2026

Threat Intel, DevSecOps· Added 22 Oct 2026, published 21 Oct 2026

Showing 30 of 248

Show more