Skip to content

151 results for β€œFlow”

What you seeeverything
  1. Over 1,000 GitLab servers vulnerable to ongoing RCE attacks

    CVE-2026-97229 is a maximum-severity integer overflow in GitLab's CI/CD Regular Expression Compiler that lets an unauthenticated attacker run code via a crafted regex in pipeline configuration. GitLab patched it on 12 October 2026 in versions 19.4.2, 19.3.5 and 19.2.8. CISA added it to KEV, and Shadowserver tracks over 1,000 unpatched servers, plus 11,300 exposed to the related CVE-2026-110264.

    bleepingcomputer.comarticlePublished and added 2 Nov 2026πŸ›‘οΈ Security

  2. Backporting security fixes at scale with Codex

    Trail of Bits describes a Codex (GPT-5.6) workflow that backports security fixes to stable Linux kernel trees, Ubuntu LTS and Fedora. By 29 October 2026 it had helped land fixes for 149 CVEs in stable kernels. Agents find missing fixes, adapt patches and assemble validation evidence; a human review takes about 30 minutes to 3 hours. It also sizes the unfixed-CVE backlog in kernel branches, Debian 13 and Ubuntu 26.04.

    blog.trailofbits.comarticlePublished and added 2 Nov 2026πŸ›‘οΈ Security

  3. Backporting security fixes at scale with Codex

    Trail of Bits describes a Codex agent workflow that backports security fixes to stable Linux kernel trees and distro packages. By 29 October 2026 it had helped land fixes for 149 CVEs in stable kernel trees, plus several Fedora and Ubuntu package fixes. Human preparation and review takes about 30 minutes for a simple backport and about three hours for a harder one. The post also counts CVEs still unfixed in stable kernel branches, Debian 13 and Ubuntu 26.04.

    blog.trailofbits.comarticlePublished and added 2 Nov 2026🧠 AI

  4. Alpine Linux rebuilds GitLab after attempted RCE attack

    Alpine Linux rebuilt its GitLab server and reset all passwords after attackers tried to exploit CVE-2026-97229, a maximum-severity integer overflow in the Onigmo regex engine bundled with Ruby, on October 20-21. Eight worker crashes occurred and four were partially successful. Missing logs and outbound connection records meant compromise could not be ruled out. Alpine had run GitLab 19.3.4, then 19.3.6, which lacked the Ruby patch; the fixed image is alpinelinux/gitlab:19.3.6 with Ruby 3.3.13.

    bleepingcomputer.comarticlePublished and added 1 Nov 2026πŸ›‘οΈ Security

  5. In Other News: Anthropic Breach Dispute, UEFI Flaw Hits Most Servers, Cloudflare AI Data Leak

    SecurityWeek's weekly roundup of 30 October 2026 covers CVE-2026-97631, a 16-year-old buffer overflow in TianoCore EDK II that affects PXE network boot on most servers. It also covers a Cloudflare Workers AI cross-tenant leak caused by an SGLang bug, Anthropic's dispute with Cathedral over a bug bounty intrusion, and fake AI bots probing for secrets. Other items include AI-assisted ransomware (Gold Ogre, Aur0ra), the NIK C2 framework, and North Korean IT worker sanctions.

    securityweek.comarticlePublished and added 30 Oct 2026πŸ›‘οΈ Security

  6. 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.

    bleepingcomputer.comarticlePublished and added 30 Oct 2026πŸ›‘οΈ Security

  7. TeamViewer Flaw Could Let Malicious Hosts Take Over Support Technicians’ Machines

    CVE-2026-111585 (CVSS 8.8) is an integer overflow in the remote-control screen processing of TeamViewer clients on Windows, macOS, Linux and Android. A malicious or compromised host can announce an oversized screen surface (for example 32768 by 32768 at 32 bpp), forcing a software decode path and an out-of-bounds write that crashes the viewer or runs code. Remedio's research shows a pointer overwrite routed to WinExec. Version 15.83 fixes it, along with CVE-2026-92372, CVE-2026-92374 and six local privilege escalation bugs.

    securityweek.comarticlePublished and added 30 Oct 2026πŸ›‘οΈ Security

  8. Inside mobile taint analysis: how source-to-sink tracking finds real data-leak paths | Oversecured Blog

    Oversecured explains taint analysis for Android and iOS apps and contrasts it with pattern-matching SAST such as MobSF. It covers source, flow and sink, cross-component tracking over Intents, flag-based sanitizer modeling and implicit intent simulation. The case study is an unsafe Class.forName().newInstance() on a Serializable transportFactoryClassName field in Google's com.google.auth.oauth2 credential classes, which Google fixed with a $3,133.70 bounty.

    oversecured.comarticleAdded 29 Oct 2026πŸ›‘οΈ Security

  9. 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.

    endorlabs.comarticlePublished and added 29 Oct 2026πŸ›‘οΈ Security

  10. 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 code. It defines formulas in five categories: AI supply chain visibility, agent action security, agent-generated code security, package risk and developer flow. It advises normalizing findings per merged change, comparing against a human baseline, and baselining six to eight metrics for a month.

    endorlabs.comarticlePublished and added 29 Oct 2026🧠 AI

  11. Police seize Virtualine bulletproof service tied to ransowmare, cybercrime

    Virtualine, a bulletproof hosting service also operating as Secury, Massgod, Spamhouse, Lanedo and Omegatech, had its main domain seized by the FBI with German, Dutch and UK partners. Chainalysis and TRM Labs traced its Bitcoin payments to ransomware (5% of flows), a Russian drug market (about 44%), sextortion and the StealC infostealer. Dutch police seized dozens of servers in Limburg and recovered data on over 3,000 customers.

    bleepingcomputer.comarticleAdded 30 Oct 2026, published 28 Oct 2026πŸ›‘οΈ Security

  12. Treasury Sanctions Russians, North Koreans supporting DPRK IT Worker Fraud

    Chainalysis analysis of the 28 October 2026 OFAC designation of 10 individuals and one entity (FFTDC) supporting DPRK IT worker schemes. It traces on-chain flows from a DPRK developer wallet through sanctioned consolidation addresses to Russian converters Obertas and Boykov, then to Garantex. It also covers Alis, Amnokgang and Chinyong links and DPRK use of generative AI and deepfakes in hiring.

    chainalysis.comarticlePublished and added 28 Oct 2026πŸ›‘οΈ Security

  13. Long-Hidden Flaws Patched in EPICS Research Facility Control Software

    Four vulnerabilities in EPICS Base 7.0.10 and earlier, the control-system toolkit used at ITER and the Advanced Photon Source, were disclosed by CISA. CVE-2026-114595 (CVSS 9.8) is an integer overflow that could allow remote code execution, though only an out-of-bounds heap write and crash were demonstrated. All flaws sit in Channel Access and pvAccess handling (TCP 5064 and 5075), need no authentication, and are fixed in 7.0.11.

    securityweek.comarticlePublished and added 28 Oct 2026πŸ›‘οΈ Security

  14. 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.

    endorlabs.comarticlePublished and added 28 Oct 2026πŸ›‘οΈ Security

  15. lee1981 (@lee1981b) on X

    CyberForge CVE of the Day #087 covers CVE-2026-115889, a Cranelift value-index overflow in Wasmtime that can miscompile crafted WebAssembly and possibly escape the sandbox (CVSS 9.9, CWE-197 and CWE-843). Affected: below 36.0.19, and 37.0.0 up to but excluding 43.0.0; fixes are 36.0.19 and 43.0.0. It gives a SOC investigation trail from module digest to compiled artifact to host telemetry. EPSS is 0.454%, with no KEV entry.

    x.comarticleAdded 28 Oct 2026, published 26 Oct 2026πŸ›‘οΈ Security

  16. Crypto exchange CoinDCX β€˜lying’ about $16M hack, say blockchain investigators

    Protos reports that on-chain investigators, including Darcy of Salus, ZachXBT and SpecterAnalyst, say CoinDCX misattributed about $16M in outflows from compromised wallets. CoinDCX says the addresses were created in January 2025, compromised in July 2025, and that a sweeping process failed. Investigators cite gas distribution, hot wallet transfers as late as May 2026, and funds sent to Huione and Xinbi addresses.

    protos.comarticlePublished and added 22 Oct 2026πŸ›‘οΈ Security

  17. Unboxing Phishing Kits: Huntress Examines 3 Real Kits

    Recap of a Huntress Tradecraft Tuesday session (October 2026) on phishing kits that target Microsoft 365 tokens, including EvilTokens (a device-code phishing campaign abusing Railway) and the Kali365 control panel. It explains device-code phishing, adversary-in-the-middle and token replay. It lists detections (unfamiliar cloud sign-ins, device-code auth, new devices) and response steps (revoke refresh tokens, remove rogue devices, block device-code flow).

    huntress.comarticlePublished and added 22 Oct 2026πŸ›‘οΈ Security

  18. Localizing compliance at scale: achieving South Korea’s ISMS certification

    Cloudflare's account of obtaining South Korea's ISMS-P certification after a ten-day KISA audit of 80 controls and a preparation period of about a year and a half. It explains that the certificate covers a service delivery boundary rather than a product list, that auditors required readable data flow diagrams, and how Korean sign-up uses itemized consent with social login removed.

    blog.cloudflare.comarticleAdded 29 Oct 2026, published 22 Oct 2026πŸ›‘οΈ Security

  19. Several Linux kernel vulnerabilities accidentally posted to public mailing list

    Phoronix reports that Trend Micro's Zero Day Initiative mistakenly sent several Linux kernel vulnerability reports to the public kernel mailing list instead of the private security list. They include two CVSS 9.0 remote code execution bugs (SMB Direct integer underflow, ksmbd race condition), a skb_zerocopy local privilege escalation, a vmwgfx out-of-bounds write, an NVMET information disclosure and a search-domain TCP stack buffer overflow. Some have patches in -next branches, and none were yet in mainline.

    phoronix.comarticleAdded 23 Oct 2026, published 22 Oct 2026πŸ›‘οΈ Security

  20. Stolen Ethereum laundering resumes as 25,700 ETH flow into Tornado Cash mixer

    Report on wallets linked to the April 2026 Drift Protocol hack resuming laundering on 20 October 2026. Lookonchain counted 25,700 ETH (about $61.56 million) sent to Tornado Cash in 100 ETH batches, with 81,864 ETH still held. It recaps the six-month fake-VC social engineering, Cursor and VSCode compromise of Security Council devices, and TRM Labs and Chainalysis attribution to DPRK's UNC4736.

    en.cryptonomist.charticlePublished and added 20 Oct 2026πŸ›‘οΈ Security

  21. ZachXBT Flags $20M XMR Laundering Ring on Hyperliquid

    FreedomXMR (FXMR) is a centralized Monero swap service on Hyperliquid Core that appeared in August 2026. ZachXBT's manual review of every inflow above $10K traced over $20M, more than 87% of volume, to ransomware, malware and exploits including DCENT Wallet, Fetch.ai, Axelar and Gamdom. The admin sources XMR liquidity from KuCoin and won the FXMR ticker in an auction for 518.28 HYPE.

    bankless.comarticlePublished and added 20 Oct 2026πŸ›‘οΈ Security

  22. Huda (@AlAssaf_H) on X

    Source-level review of x64dbg-MCP, GhidraMCP and IDA Pro MCP security, dated October 2026. It covers GHSA-4478-h5jv-647m (missing authentication, 0.0.0.0 bind) and GHSA-jgj3-97w2-9v9r (Content-Length integer overflow before the token check, causing a DoS panic), and compares tags 1.0, v1.1 and v1.2. It separates network reachability, tool authority and semantic influence from hostile binaries. No new exploit is claimed.

    x.comarticleAdded 21 Oct 2026, published 19 Oct 2026πŸ›‘οΈ Security

  23. Broadcom Wi-Fi vulnerability leaves over 1.5 million Belgian gateways exposed

    A Broadcom SDK flaw in the WPS code that reassembles fragmented EAP messages allows a buffer overflow and unauthenticated code execution over Wi-Fi, bypassing WPA2/WPA3 passwords. Quentin Kaiser of ONEKEY demonstrated it at Hexacon on 16 October 2026 against Orange Belgium and Proximus gateways, and published a fingerprinting script and YARA rule. Broadcom's 2018 patch was incomplete, it refused a CVE, and over 1.5 million Belgian gateways are exposed.

    en.cryptonomist.charticlePublished and added 19 Oct 2026πŸ›‘οΈ Security

  24. lee1981 (@lee1981b) on X

    CyberForge Weekly CVE Rundown #006 covers six CVEs from 12-17 October 2026: BotSharp default signing key, GitLab CI/CD regex compiler overflow (CVSS v3.1 10.0), Ivanti Connect Secure auth bypass, Cisco Secure Email Gateway, BeyondTrust Remote Support and the Linux kernel PwnEscape guest-to-host bug. It gives fixed versions, KEV and EPSS status as of 18 October, and separates patch verification from compromise investigation.

    x.comarticleAdded 20 Oct 2026, published 18 Oct 2026πŸ›‘οΈ Security

  25. In Other News: ICS-Sniper Attack, Hacking XWorm Malware Operators, $250k Chrome Exploit

    SecurityWeek's weekly roundup covers ICS-Sniper, a UBC proof-of-concept that uses VPN-encrypted packet size, direction and timing to drop critical SCADA traffic on cloud-hosted ICS (tested on the SWaT water testbed). It also covers an unauthenticated RCE PoC against the XWorm RAT C2 panel (up to 7.4) via path traversal DLL overwrite, and Langflow CVE-2026-105740 (MCP Stdio command injection, fixed in 1.9.0) exploited from September 19, before the CVE was published. Other items: XBOW's AI-assisted Chrome full-chain exploit (GPT-5.6 Sol, $250k bounty), Group-IB's KGB RAT analysis, Anthropic's disclosure of Claude rule-bending on live sites, Intel ending SGX after Diamond Rapids, Bank of America's Mythos-driven patching, the Burger King Japan breach and a West African scam-center takedown.

    securityweek.comarticlePublished and added 16 Oct 2026πŸ›‘οΈ Security

  26. F5, Juniper Networks Patch Critical Vulnerabilities

    SecurityWeek reports F5 fixed 11 NGINX vulnerabilities. Three are critical: CVE-2026-15176 and CVE-2026-93479 are unauthenticated buffer overflows via crafted HTTP requests, and CVE-2026-97205 is memory corruption. All three can lead to RCE if ASLR is disabled or bypassed. Juniper Networks published 17 advisories covering over 150 flaws in Junos OS and Junos OS Evolved, plus four in Cloud-Native Router. About two dozen are critical, with root code execution, device takeover, kernel panic and an off-by-one buffer overflow. Neither vendor reports exploitation in the wild.

    securityweek.comarticlePublished and added 16 Oct 2026πŸ›‘οΈ Security

  27. What We Can Learn About GitHub Actions Security from the Trivy Breach | Endor Labs

    Endor Labs analyzes the March 2026 Trivy compromise (CVE-2026-33634, CVSS 9.4). A pull_request_target misconfiguration leaked a PAT, and attackers then force-pushed malicious commits to 75 of 76 trivy-action tags and all 7 setup-trivy tags. The TeamPCP credential stealer harvested SSH keys, cloud and CI tokens and runner memory, and exfiltrated to a typosquatted domain. It gives three checks: audit pull_request_target workflows, pin Actions to full commit SHAs, and scope GITHUB_TOKEN permissions. It also notes the limits of SHA pinning.

    endorlabs.comarticlePublished and added 16 Oct 2026πŸ›‘οΈ Security

  28. GitHub Action tj-actions/changed-files supply chain attack: what you need to know | Endor Labs

    Endor Labs explains the March 2025 compromise of the tj-actions/changed-files GitHub Action (CVE-2025-30066). Attackers pushed a malicious commit and retroactively repointed version tags, so a Python payload dumped CI/CD secrets to workflow logs across about 23,000 repositories. The post gives response steps: find usage with a GitHub code search, remove the Action from all branches or enforce an Actions allowlist, audit logs for suspicious outbound requests and IPs, and rotate exposed secrets. It also notes the March 17 restoration and the risk of transitive Action dependencies. It includes Endor Labs customer steps (the `--ghactions --secrets --git-logs` scan flags).

    endorlabs.comarticlePublished and added 16 Oct 2026πŸ›‘οΈ Security

  29. PWN Request Threat: A Hidden Danger in GitHub Actions | Endor Labs

    Explains the "pwn request" weakness in GitHub Actions. A workflow triggered by pull_request_target runs with write permissions and secrets, so if it checks out and builds PR head code, attacker-controlled code runs in a privileged context. It gives a three-step check for susceptible workflows: the trigger, a checkout of the PR head SHA or ref, and build steps such as npm install or make. It also covers mitigations: switch to pull_request or workflow_run, gate on a label, and never pass secrets to scripts that run on PR code. It notes safe patterns and cites the puppetlabs finding.

    endorlabs.comarticlePublished and added 16 Oct 2026πŸ›‘οΈ Security

  30. Scaling Indic Pretraining: 2.8 Trillion Tokens and an Open Data Generation Pipeline

    Announces Nemotron-pretraining-Indic-v1, about 2.8T tokens across 22 Indian languages (2,601B native-script, 224.6B romanized; 34 language-script configs), built by translating 15 Nemotron-CC-v2 subsets with NeMo Data Designer and Gemma-4-31B-it. The pipeline covers document-level translation, an MQM-inspired judge with a 75/100 threshold, feedback-based repair, and a separate Indic Translate workflow for ten languages. Continued pretraining of Nemotron 3.5 Super VL with 10B Indic tokens raised all five Indic benchmarks by 4.98–9.82 points. The post also gives dataset loading code and notes limitations: automated judging, translator-as-judge, and no semantic dedup.

    huggingface.coarticlePublished and added 16 Oct 2026🧠 AI

  31. Granite Switch 4.1: Chat, Decisions, and Speech from One Endpoint

    IBM announces Granite-Switch-4.1-8B and -30B. Each composes a base Granite model with a Decision aLoRA, a Guardian safety aLoRA and the Granite-Speech-5.0-Turbo-CTC ASR model into one model that uses about the same VRAM as the base alone. Because the adapters are Activated LoRAs, they reuse the base model's KV cache, and with IBM's vLLM contributions for faster LoRA inference one endpoint can handle chat, decision and speech requests. The post compares the setup with Jev (a 5-step RAG workflow race, and a 3B Doom-playing model at 60–100 decisions/s against Jev's reported 10), and says users can compose their own Switch models from Granite Libraries adapters.

    huggingface.coarticlePublished and added 15 Oct 2026🧠 AI

  32. AWS Security Agent (now part of AWS Continuum) exploited 33 of 37 new real-world CVEs

    AWS reports results for its autonomous pentesting agent, AWS Security Agent (now part of AWS Continuum), on an internal CTF-style benchmark of 37 recent 2025–2026 CVEs. Each CVE ran as a live docker-compose target with a hidden flag, and the agent started from an endpoint and a one-line hint with runtime CVE lookup disabled. It captured 35 flags, 33 (89.2%) through the intended vulnerability after an audit against canonical PoCs. The post describes the 7-stage pipeline (crawler, specialist agents, validator, exploitation agent, flag check, audit), three exploit walkthroughs (CMS upload-to-admin chain, AI workflow builder RCE, tRPC full-read SSRF), the two audit reclassifications caused by benchmark bugs, and two misses where the agent took the target down. It also argues that saturated public benchmarks like CVE-Bench and XBOW are contaminated.

    aws.amazon.comarticlePublished and added 15 Oct 2026πŸ›‘οΈ Security

  33. Welcome FLUX.3 Image Klein in Diffusers

    Hugging Face blog post introducing Black Forest Labs' open FLUX.3 Image Klein (distilled and base checkpoints) in Diffusers. It covers text-to-image, multi-reference image-to-image and bounding-box layout control, FP8/NVFP4 single-file quantized weights, DreamBooth LoRA training scripts for generation and editing, memory/speed figures (about 2 s per 1024Γ—1024 image on an H100), and a detailed architecture tour: Qwen3-VL text encoder, two-stage per-stream then joint transformer blocks, per-token timestep modulation, 4D RoPE, and flow-matching denoising. It also shows how to customise the Modular Diffusers pipeline.

    huggingface.coarticlePublished and added 15 Oct 2026🧠 AI

  34. XBOW Used AI to Hack Google Chrome in Six Days, Earning $250,000

    News write-up of XBOW's research in which AI agents (OpenAI gpt-5.6-sol) plus human researchers built a full Chrome exploit chain on Windows in six days, at about $40,000 in API cost, earning a $250,000 Chrome VRP reward. The chain combined a V8 Maglev bounds-check bypass, a WebP animated-decoder heap buffer overflow, and a Crashpad out-of-bounds write that escaped the sandbox and called CreateProcessW() to launch Calculator. The common root cause was trusting conditions (immutability, unchanged data, suspended process) that could change; Chrome 153+ is patched.

    en.cryptonomist.charticlePublished and added 14 Oct 2026πŸ›‘οΈ Security

  35. North America: Inside the Growth of Agentic Commerce

    Chainalysis's North America chapter of its 2026 crypto adoption report. Its centrepiece is an on-chain analysis of Coinbase's x402 protocol, which lets AI agents pay autonomously: over 138M transactions on Base, 87% of payments between $0.0001 and $0.10, and growing wallet re-funding (70.6% to 89.3% within 30 days). Wallets also move from funding to first spend faster (73 days to 18 minutes at the median). It breaks down what agents buy (data/search APIs, code review, model inference, agent frameworks), shows US wallets making 88% of inference payments and Chinese wallets dominating security-audit spend, and argues compliance should screen agent funding, counterparty and behaviour pattern rather than each payment. The remainder covers dollar stablecoin exports, tokenized Treasuries and Canada's peer-to-peer and remittance flows.

    chainalysis.comarticlePublished and added 14 Oct 2026🧠 AI

  36. Chrome, Firefox Updates Patch 114 Flaws as Mozilla Unveils Firefox Enterprise

    SecurityWeek covers Chrome 155.0.8059.79/.80, which fixes 37 flaws including seven critical memory bugs (an ANGLE buffer overflow and use-after-free bugs in Browser, PDF, Network, Core, SVG and Media). It also covers Firefox 158, which fixes 77 flaws including 30 high-severity use-after-free, sandbox escape, JIT miscompilation and integer overflow bugs, plus matching Thunderbird and Firefox ESR releases. At least 15 of the Chrome bugs were reported by Xinyang Ge (Anthropic) assisted by Claude, and Amy Burnett of OpenAI found 9 Firefox bugs. The article also notes Mozilla's new Firefox Enterprise, a Gecko-based browser with a self-hosted management console for policy, access, data transfer and AI use.

    securityweek.comarticlePublished and added 14 Oct 2026πŸ›‘οΈ Security

  37. Gemini 4 Argon

    Google DeepMind's launch page for Gemini 4 Argon, a frontier model pitched at long-horizon software engineering, science and math, robotics, cyber defense and professional workflows. Stated specifics: a 1M-token output window for full-repository generation and long proofs, a tie for #1 on CWE-Bench (68%) for vulnerability remediation, and a 14% accuracy gain over Gemini 3.1 Pro in Box's evaluation. It also describes safeguards (resistance to indirect prompt injection, chain-of-thought monitoring, sandbox hardening under the Frontier Safety Framework) and availability via Google AI Pro/Ultra, Gemini API, AI Studio and Antigravity. Much of the evidence is partner testimonials and vendor-reported results.

    deepmind.googlearticlePublished and added 13 Oct 2026🧠 AI

  38. XBOW Built a Chrome Full-Chain Exploit Affecting a Billion Users in Six Days | XBOW

    XBOW describes building a Chrome full-chain exploit, made of three independent bugs, that takes a user from an ordinary web page to remote takeover of a Windows machine. The team built it in six days with a publicly available model (GPT-5.6 Sol) for about $40,000 of compute, and Google paid a $250,000 bounty, the first under its 2026 rules. The bugs are now fixed. The post covers the human-agent workflow, the modular design that allowed swapping in a backup bug after Google said it already knew one, and the claim that agents could find each bug on their own within a year.

    xbow.comarticlePublished and added 13 Oct 2026πŸ›‘οΈ Security

  39. How Anthropic’s Dynamic Workflows Coordinate Claude Agents

    Latent Space report from an Anthropic workshop at AI Engineer New York 2026 on "dynamic workflows" (flows) in Claude Managed Agents. Instead of developers configuring a coordinator and a roster of subagents, the lead Claude agent writes an orchestration program that launches agents, collects results and manages information flow. The Q&A covers parallelism defaults and evals, session budgets, the Claude Console graph view, subagents sharing a filesystem, "dreaming" memory consolidation, and the higher cost of flows compared with a single agent.

    latent.spacearticlePublished and added 12 Oct 2026🧠 AI

  40. Just say no to OpenAI and Anthropic

    Micah Lee argues for dropping OpenAI and Anthropic in favor of open-weight models, claiming they trail proprietary ones by about four months. They report GLM-5.3 as roughly on par with Claude Opus 5.5 for software engineering, and GLM-5.3-Flash as similar to Opus 4.8 and feasible to run locally. The post compares private inference through secure enclaves (Tinfoil, Maple AI) with cheaper non-private routers (OpenCode Go). It gives pricing, data-trust caveats about Z.ai, and the author's own workflow: OpenCode harness, GLM-5.3 on low reasoning, Tinfoil for private work.

    micahflee.comarticlePublished and added 12 Oct 2026🧠 AI

  41. XRP Ledger’s Payment Engine Had a Counterfeiting Bug Hiding Since 2015

    XRP Ledger maintainers disclosed a critical integer overflow in the payment engine, reported via bug bounty in September. A payment consuming hundreds of crafted order-book offers made the buyer's owed sum wrap around to a tiny value while sellers were paid in full, minting XRP. The built-in "no XRP created" invariant check used the same flawed arithmetic and missed it. The fix shipped in 3.4.1 on Sept. 25, bypassing the usual amendment vote and two-week wait for the first time, so the open-source patch would not expose a live exploit. No exploitation evidence was found.

    decrypt.coarticlePublished and added 12 Oct 2026πŸ›‘οΈ Security

  42. Why a bug that could have threatened XRP's 100 billion supply cap stayed hidden for years

    CoinDesk reports on an 11-year-old integer-overflow bug in the XRP Ledger's DEX code. Hundreds of crafted offers could make the computed buyer cost wrap to near zero while sellers were credited in full, which would have minted billions of XRP beyond the 100 billion cap. The post-transaction no-new-XRP invariant check used the same miscounted total, and the per-account receive limit was sidestepped by spreading funds across hundreds of accounts. Researcher Cayden Liao and Veria AI reported it on Sept. 22, RippleX patched it with no evidence of exploitation, and the XRP Ledger Foundation plans AI adversarial testing, formal verification and a stronger bug bounty.

    coindesk.comarticlePublished and added 12 Oct 2026πŸ›‘οΈ Security

  43. XRP Ledger patches decade-old bug that could have minted trillions of XRP

    The Block reports on the XRP Ledger disclosure of a critical bug that had been in the payment engine since 2015. Order-book offer totals had no overflow check, so a single payment consuming a few hundred crafted offers could wrap the sum and mint spendable XRP past the 100B cap. Veria Labs' AI agent found it and built a working exploit, and RippleX shipped the fix in xrpld 3.4.1 on Sept. 25, bypassing the usual amendment vote to avoid tipping off attackers. The article also covers the $250K bounty, a separate Batch bug, and the closed-source-release criticism.

    theblock.coarticlePublished and added 11 Oct 2026πŸ›‘οΈ Security

  44. An XRP Ledger security bug could have created 18.45 trillion XRP

    Reports a decade-old integer overflow in the XRP Ledger payment engine's DEX offer-crossing code (added 2015). A single transaction across hundreds of seeded accounts could have minted about 18.45 trillion XRP, because the overflowed total understated what the buyer paid and the mint-check safeguard used the same wrong total. Veria AI found it on 2026-09-21 and reported it through the bug bounty. RippleX reproduced it on a standalone server and shipped xrpld 3.4.1 on 2026-09-25 as binaries only, with no patch source. RippleX's Mayukha Vadari warns that AI makes silent critical patches easy to reverse engineer, and the withheld source drew open-source criticism.

    en.cryptonomist.charticlePublished and added 11 Oct 2026πŸ›‘οΈ Security

  45. [AINews] TypeSafe/Jev at >$100M ARR, $7.5B valuation 3 weeks after launch

    AINews issue for 10/8–10/9/2026 from Latent Space. It leads with "decision models" (typed single-pass outputs) becoming a product category after Jev, with OpenAI Decisions API, Microsoft-Decision-1, Perplexity pplx-decider, Cloudflare clef, Liquid d1, and Unsloth/Qwen3.5 training recipes. It also covers Claude Managed Agents dynamic workflows (up to 1,000 agents), a Vals AI study of agent teams, Codex updates, model releases (Qwen-Image-2.1-Turbo, StepFun Step 5 Preview, Solar Mini 4, Gemini 4 Argon), and inference/training systems news (vLLM/SGLang on Vera Rubin, TRL v1.15, DeepSeek stride weak spots).

    latent.spacearticlePublished and added 10 Oct 2026🧠 AI

  46. A new feature for my, blog built using my voice

    Simon Willison describes building a new "Newsletters" index feature for his Django-powered blog almost entirely by talking to the ChatGPT desktop app's Codex voice mode (running GPT-6 Astra) while cooking dinner, then switching to typed prompts to review and fix the resulting GitHub pull request. He details the workflow β€” starting a local dev server, voice-describing requirements including a new model, migrations, four import scripts, and search integration β€” and reflects on where voice-driven coding agent interaction excels (multitasking, visual preview of changes) versus where typing remains more efficient (pasting errors, highlighting specific code).

    simonwillison.netarticlePublished and added 9 Oct 2026🧠 AI

  47. In Other News: AI Used in Korean Bank Breaches, Poem-Guided Botnet, Empire Admin Gets 40 Years

    SecurityWeek's weekly news digest covering PoeLLM malware that resolves its C&C IP from keywords hidden in a GitHub-hosted poem, the GhostAction campaign spreading malicious GitHub Actions workflows to steal secrets from 772 more repos, South Korean authorities probing suspected AI-assisted bank breaches where CrowdStrike found Claude Code and Claude memory artifacts on attacker infrastructure, a high-severity Nvidia DCGM Exporter flaw (CVE-2026-47483) exposing GPU telemetry from over 12,000 hosts, and a Shai-Hulud-style credential-stealing worm shipped in Tensorlake's npm SDK. Also notes legal outcomes (Uranium Finance hacker conviction, Empire Market co-founder's 40-year sentence) and policy moves (CISA retention pay changes, an OT cybersecurity directive proposal).

    securityweek.comarticlePublished and added 9 Oct 2026πŸ›‘οΈ Security

  48. Post-quantum authentication: Why organizations should start testing certificate ecosystems now

    Microsoft Security Blog post arguing that post-quantum cryptography planning must extend beyond encrypted-data confidentiality to authentication and certificate ecosystems, since larger PQC certificate chains and new algorithms like ML-DSA-87 can break PKI workflows, HSMs, and legacy infrastructure. It details Microsoft's PQC TLS Pilot Program, launched August 27, 2026, which lets approved certificate authorities (ComSign, DigiCert, HARICA, IdenTrust, Sectigo, Shanghai Electronic Certification Authority, SSL.com) test ML-DSA-87 certificate issuance under the Microsoft Trusted Root Program, plus Windows 11 builds (KB5101681, KB5101684) that support evaluating ML-DSA certificates via Schannel in non-production environments. It lays out a six-step readiness plan: inventory certificate dependencies, map trust relationships, assess vendor roadmaps, identify long-lived infrastructure, build test environments, and plan a multi-year migration.

    microsoft.comarticlePublished and added 8 Oct 2026πŸ›‘οΈ Security

  49. Understanding AI, Part I: The Machines That We Taught

    Galaxy Research's explainer traces AI's intellectual history from the 1956 Dartmouth Workshop and the Logic Theorist through the symbolic-AI era (expert systems like Mycin and XCON, the Cyc project) to the sub-symbolic/connectionist revival (Perceptron, Hopfield networks, backpropagation, LeCun's CNN zip-code reader) that culminated in deep learning and the 2017 Transformer architecture. It then surveys three machine-learning paradigms (supervised, reinforcement, unsupervised) and five deep generative architectures (autoregressive, diffusion, GANs, VAEs, normalizing flows), closing with how modern LLM chatbots combine these via pretraining, SFT, and RLHF, and how multimodal, reasoning, RAG, agent, and world-model systems extend base LLMs.

    galaxy.comarticleAdded 8 Oct 2026🧠 AI

  50. Why isn't the industry freaking out about DeepSeek 4.1 Flash?

    A developer's blog post recounting a month of heavy daily use of DeepSeek 4.1 Flash across coding projects, arguing it matches frontier-model quality (Claude Opus 5.5, GLM) at a tiny fraction of the cost (around $1/day vs much more for Claude). The author credits a roughly 437x KV-cache size reduction versus DeepSeek's V1 model for the cost savings, discusses why self-hosting the model is economically unattractive despite being technically possible, and reflects on how a cheap "good enough" model changes workflow habits and on environmental/economic implications of model efficiency.

    dgt.isarticlePublished and added 8 Oct 2026🧠 AI

  51. Configuring your AI vulnerability harness, Part 2: The steering file

    AWS Security Blog's second post in a series on building an "AI vulnerability harness" explains the configuration (steering file) that stops an AI model from hallucinating vulnerabilities and inflating severity during security code review. It details five configuration sections β€” structural verification of findings, an evidence-based confidence formula (weighting confirmed taint flow at 0.30), infrastructure-aware severity multipliers for controls like AWS WAF and IAM, CISA KEV/EPSS threat-intel boosting, and a four-tier priority classification β€” and reports validation numbers (e.g., unsteered models fabricated code paths in ~30% of findings; steered confidence of HIGH without structural confirmation was only 34% exploitable vs 89% with confirmed taint). The steering file is shipped as a Kiro steering file, a Kiro skill, and a CLAUDE.md for Claude Code, with full source in a linked GitHub repo.

    aws.amazon.comarticlePublished and added 7 Oct 2026πŸ›‘οΈ Security

  52. Building your AI vulnerability harness, Part 1

    AWS Security Blog describes a three-layer AI-assisted pipeline for triaging vulnerability scanner findings: Layer 1 cross-checks multiple scanners (e.g., Semgrep, CodeQL) for agreement, Layer 2 verifies a scanner's claimed data-flow path against the code's actual abstract syntax tree to catch hallucinated findings, and Layer 3 cross-references infrastructure-as-code (CloudFormation/Terraform) to weigh whether existing controls like AWS WAF rules actually mitigate the exploit path. It argues progressive, escalating-evidence filtering plus mandatory structural verification of LLM claims before human review is what turns noisy scanner output into a short, trustworthy, prioritized list, and lays out an adoption order (indexing, then multi-scanner triage, then AI hypothesis generation, then infra context, then live PoC verification).

    aws.amazon.comarticlePublished and added 7 Oct 2026πŸ›‘οΈ Security

  53. I'm not paying $20 for ChatGPT or Claude because a free local LLM does

    A personal workflow writeup describing how the author replaced $20 per month ChatGPT and Claude subscriptions with Qwen3.8-27B (Unsloth UD-IQ4_XS GGUF quant, 13.3GB) run locally via llama.cpp on a 4070 Ti Super GPU with 16GB VRAM, achieving about 33.7 tokens per second at a 16K context window. It covers use cases like grammar and email cleanup, sentiment analysis, data extraction, and iterative Python coding where the local model matched cloud performance without rate limits, five hour caps, or data leaving the machine, while noting Claude still leads on raw coding ability.

    xda-developers.comarticleAdded 8 Oct 2026, published 7 Oct 2026🧠 AI

  54. Kubernetes Agent Sandbox Explained

    Kubernetes Agent Sandbox is a Kubernetes SIG Apps project that gives each AI agent session an isolated, stateful, single-Pod workspace for running untrusted code. The newsletter explains the Sandbox CRD, SandboxTemplate, SandboxWarmPool, SandboxClaim and Sandbox Router workflow, gVisor and Kata Containers isolation, and suspend/resume and scheduled deletion. It points to a hands-on guide with a Kubernetes troubleshooting agent.

    newsletter.devopscube.comarticleAdded 21 Oct 2026, published 7 Oct 2026🧠 AI

  55. Google Launches Nano Banana 2.1: Better Than Its Predecessor at Half the Price

    Decrypt reports on Google October launch of Nano Banana 2.1, an image generation and editing model built on Gemini, rolling out in the Gemini app, Search AI Mode, Google Ads, Google AI Studio, Flow and Stitch. It claims gains over Nano Banana 2 and Nano Banana Pro in text to image ELO scoring and infographic factuality, supports up to fourteen reference images, four tracked characters, ten objects, 4K output and wide aspect ratios, with Google Search grounding and adjustable thinking time, while developer API pricing drops to roughly half of Nano Banana 2 pricing for a standard 1K image.

    decrypt.coarticlePublished and added 6 Oct 2026🧠 AI

  56. Advancing computer use with Ironclad

    OpenAI describes a research collaboration with Ironclad (contract lifecycle software) to train and evaluate computer-use agents on complex business workflows such as configuring NDAs, procurement approval rules and reusable legal clauses. It covers 11 tasks scored against 8–50 criteria each, hosted Ironclad environments, synthetic training tasks and reinforcement learning. On this research eval GPT-6 Astra (Max reasoning) averaged 55.0% against 41.6% for GPT-5.6 Sol (High reasoning), with estimated time per attempt down from 37.0 to 19.2 minutes. An internal model reached 63.7%. The post also invites other software companies to partner. The results are self-reported, on a non-public eval.

    openai.comarticlePublished and added 6 Oct 2026🧠 AI

  57. The Era of Software Quality, or the Era of Ostriches?

    GNOME security maintainer Michael Catanzaro details how AI-generated vulnerability reports have transformed GNOME's security workload: CVE counts for GNOME and WebKitGTK rose an order of magnitude, driven largely by AI scanning. He breaks down the now-closed YesWeHack-hosted GNOME Bug Bounty Program (sponsored by Germany's Sovereign Tech Agency) which paid €183,900 for 71 vulnerabilities across libsoup, GLib, and glib-networking, a Red Hat-commissioned AISLE Research AI scan of GLib that found 118 issues with a ~40% false-positive rate (mostly gobject-introspection typelib misclassifications), and a Codean Labs human security audit that found critical Flatpak and xdg-desktop-portal sandbox escapes AI likely would have missed. He argues maintainers should permit AI-generated vulnerability reports in their contribution policies, warns about integer-overflow bugs and Cargo supply-chain risk in Rust, and offers a draft AI-usage policy for GNOME contributors.

    blogs.gnome.orgarticlePublished and added 5 Oct 2026πŸ›‘οΈ Security

  58. The Agent Said It Was Done. The Database Disagreed.

    ThinkingBox is an agent sandbox and ThinkingBox-Bench is a 507-task stateful business-workflow benchmark (retail, auto insurance, etc.) that grades agents by checking the terminal backend database state and side effects they leave behind, not just whether tool calls succeeded or the final reply sounds right. Across 121,680 trials over 12-18 LLMs run 20 times each, the post finds most failures are clean-looking: 67% of failed trials still terminated without a tool error, yet executable checks caught wrong field values, missing effects, or unintended extra effects. It also reports pass@1 vs. 20/20 consistency gaps (e.g. Kimi K3 solves the most tasks at least once but is among the least consistent, while Claude Opus 5 and Claude Opus 5.5 are the most dependable) and cost-per-success/cost-per-dependable-task metrics, and ships the benchmark through an OpenEnv interface for reproducible evaluation.

    huggingface.coarticlePublished and added 3 Oct 2026🧠 AI

  59. Why AI Coding Agents Keep Writing Broken Access Control

    Snyk argues AI coding agents reliably write broken access control (BOLA/IDOR, OWASP's top category since 2021) because the facts needed to add an ownership check β€” what an object belongs to, who may access it, where tenant boundaries sit β€” are tacit product knowledge that exists nowhere in the code or prompt an agent sees. It explains why SAST tools catch patterned sub-categories like path traversal or SSRF but structurally cannot catch CWE-639/862/863 (missing or incorrect authorization), since there's no bad pattern to match, and proposes reasoning over an assembled "application-context graph" of architecture, data flows and trust boundaries instead. It closes with a five-step team checklist (inventory ID-accepting endpoints, document ownership rules, add authorization-specific PR review, write cross-tenant tests, run deep contextual analysis) and pitches Snyk's Evo Agentic AppSec as the tool built around that approach.

    snyk.ioarticlePublished and added 1 Oct 2026🧠 AI

  60. Securing the Kubernetes Supply Chain: Introducing WizOS Helm Charts

    Wiz Research examined the source repositories and CI/CD pipelines behind 1,500 popular Helm charts on Artifact Hub (mapping to 814 unique GitHub repos) and found 61 repos (7.5%) with confirmed supply-chain risk, including 20 charts with CI/CD workflow weaknesses and 25 depending on unmaintained/archived upstream projects. Two disclosed findings illustrate the risk classes: KubeView's go.mod referenced a Go module under a GitHub username that didn't exist, making it hijackable by anyone who registered the name, and Meilisearch's Helm chart repo had a GitHub Actions workflow triggered by PR comments that injected the commenter's branch name into a shell command while skipping author-association checks, letting any GitHub user run commands with a bot token that had push access. The post then pivots to promoting WizOS Helm Charts, Wiz's hardened/signed/CVE-scanned chart catalog built to close these gaps.

    wiz.ioarticlePublished and added 30 Sep 2026πŸ›‘οΈ Security

  61. Connect Orca’s ChatGPT Plugin: Cloud Risk Context in Chat and Codex

    Orca Security's plugin connects ChatGPT and Codex to Orca's MCP server, letting security teams and developers query cloud alerts, attack paths, effective IAM permissions, and code-to-cloud origins directly from chat or a coding agent instead of logging into a console. The post walks through six security-team use cases (exposure discovery, CVE impact triage, alert-to-blast-radius investigation, identity permission review, CISO reporting) and three developer workflows in Codex where alerts are traced back to the Terraform/code that created the misconfiguration and fixed in place.

    orca.securityarticleAdded 2 Oct 2026, published 30 Sep 2026πŸ›‘οΈ Security

  62. [AINews] OpenAI DevDay 2026: Dots, 6.1 Sol, Ultrafast, Decisions API, Agents API, Spaces, Marketplace, and 1.2 Billion ChatGPT WAU

    AINews daily digest covering OpenAI DevDay 2026: the launch of 'dots' (always-on GPT-6 Astra-powered agents with app/Slack/Teams connectivity), GPT-6.1 Sol (a cheaper 'near-Astra' model at $2/$10 per M tokens), Ultrafast inference mode, a new Decisions API for fast classification/routing on GPT-6 Luna, ChatGPT Spaces/Pages, and a B2B model marketplace via Baseten. It also rounds up independent evals (Artificial Analysis, planted-bug tests, Roboflow vision benchmarks) comparing GPT-6.1 Sol against Claude Opus/Sonnet 5.5, plus safety/eval-integrity stories (scrapped GPT-6.1 Astra, evaluation awareness, GLM-5.3 cyber capability), agent infrastructure research (DeepSeek DSec sandboxing, StepFun KITE, vLLM day-0 support), and industry news (Anthropic's IPO filing, Hugging Face acquisition by NVIDIA).

    latent.spacearticlePublished and added 30 Sep 2026🧠 AI

  63. Vulnerability Discovery and Exploitation Trends in the AI Era (Google Cloud)

    Google Threat Intelligence Group analyzes vulnerability disclosure and exploitation trends from January 2025 to August 2026, finding disclosures doubled, exploitation nearly doubled, and AI-assisted discovery surfaces proportionally more Medium and High-risk flaws, with 50 percent leading to remote code execution versus 26 percent baseline. It documents real-world exploitation of an AI-discovered CVE in BeyondTrust PRA and a surge in vulnerabilities targeting the AI/LLM operational stack, especially agent orchestration frameworks like Langflow and Flowise and inference gateways like LiteLLM and vLLM, citing specific CVEs in those products.

    cloud.google.comarticleAdded 8 Oct 2026, published 30 Sep 2026πŸ›‘οΈ Security

  64. Quoting Anthropic Frontier Red Team

    Simon Willison quotes Anthropic's Frontier Red Team report "GLM-5.3 and the spread of advanced cyber capabilities," which ran several models against 100 randomly-selected tasks from an internal Binary Exploitation benchmark. GLM-5.3 produced full control-flow hijack exploits in 4% of trials and Claude Mythos Preview in 6%, while earlier models (Claude Opus 4.6, GLM-5.2) succeeded in none β€” marking what Anthropic frames as a newly crossed capability threshold for AI-assisted exploit development.

    simonwillison.netarticleAdded 30 Sep 2026, published 29 Sep 2026πŸ›‘οΈ Security

  65. GLM-5.3 and the spread of advanced cyber capabilities

    Anthropic's Frontier Red Team analyzes GLM-5.3, an open-weight model from Zhipu AI (Z.ai), finding it matches Claude Mythos Preview's exploit-development capability (50/410 vs 56/410 end-to-end exploits on ExploitBench against Chrome's V8 engine; 4% vs 6% full control-flow hijacks on an internal OSS-Fuzz binary exploitation benchmark) but ships with safeguards attackers bypass 64-100% of the time via prompting tricks, prefill, or "abliteration" of the open weights. The post documents a researcher using GLM-5.3 to chain previously unknown JavaScript-engine vulnerabilities into a working browser file-read exploit, and GLM-5.3-Flash autonomously building a reliable ARM64 PAC-bypass exploit chain for CVE-2026-11645 for about $20. It argues GLM-5.3's lack of meaningful safeguards marks a step change in freely accessible offensive cyber capability and calls for independent government safety testing of such open-weight models.

    anthropic.comarticleAdded 2 Oct 2026, published 29 Sep 2026πŸ›‘οΈ Security

  66. OpenAI DevDay 2026 live blog

    Simon Willison's minute-by-minute live blog of OpenAI's DevDay 2026 keynote and breakout sessions in San Francisco, covering the launch of "dots" (personal ChatGPT agents styled like Meta's Muse), the new GPT-6.1 Sol model, an "Ultrafast" 8x-speed inference tier, a Decisions API for near-instant model responses, ChatGPT Spaces/Sites, Codex Security Cloud (with an open-source Codex Security CLI and automated patch/verify-fix workflow), a GPT-Live voice-agent demo, and a closing Q&A with Sam Altman and Thibault Sottiaux touching on agent-to-agent communication, pricing philosophy, and the future of coding. It's a dense, well-sourced snapshot of a major platform's simultaneous product, model, and infrastructure announcements.

    simonwillison.netarticlePublished and added 29 Sep 2026🧠 AI

  67. Getting the Source Right, Not Just the Fact: Source-Aware Verification for MCP Agents

    Multiverse Computing's blog introduces ProvenanceGuard, a post-generation verification layer for MCP-based LLM agents that checks not just whether a claim is factually supported somewhere in retrieved evidence, but whether it is attributed to the correct MCP source β€” catching a failure mode they call cross-source conflation (e.g., a refund-policy fact wrongly attributed to an account record). The pipeline decomposes answers into claims, routes each to its most relevant source (MiniLM), scores support with a DeBERTa NLI model, checks source attribution, and can trigger RARR-style repair or fallback for blocked answers. On a 361-claim medical-agent benchmark it caught 138/139 claims that should be blocked, detected all 50 injected source-swap errors, and the approach has already been adopted in NVIDIA NVFlow's finance-agent grounding stage.

    huggingface.coarticleAdded 7 Oct 2026, published 29 Sep 2026πŸ›‘οΈ Security

  68. Near Intents blocks $50 million in Bitget hacker swaps, here's what happened

    After attackers stole $388M from Bitget, they tried routing $50M+ through the cross-chain swap service NEAR Intents; its SHIELD system β€” which ingests KYT and intelligence-provider signals to flag deviations in flow β€” froze roughly $503,000 mid-swap while $166,000 slipped through. The piece contrasts this with THORChain's refusal to block the same attacker addresses, letting $6.3M complete ether-to-bitcoin swaps, and details the resulting debate over whether a "permissionless" protocol can hold user funds without a defined process for release or appeal.

    coindesk.comarticleAdded 30 Sep 2026, published 29 Sep 2026πŸ›‘οΈ Security

  69. How we found 24 Android vulnerabilities using our open source AI security agent

    GitHub Security Lab describes the architecture behind its open-source "Taskflow Agent," a set of YAML-defined prompt workflows (e.g. gather_mobile_entry_point_info.yaml, classify_application_local.yaml) that guide an LLM through structured, multi-step code audits rather than a single free-form prompt. Using these taskflows on Android apps via GitHub Copilot, the team found 24 vulnerabilities, including a location-tracking bug in OsmAnd via exported-activity intent extras and a cookie-leaking account-takeover chain in the Wikipedia app via a deeplink hostname-parsing flaw. The post's more durable contribution is its analysis of LLM auditing behavior: strong at recognizing API-level unsafe patterns and generating working PoCs, but unreliable at severity estimation and prone to false positives from mitigating factors the model doesn't account for, requiring human review and repeated/guided runs.

    github.blogarticleAdded 8 Oct 2026, published 28 Sep 2026🧠 AI

  70. Researchers Detail DifyTap Flaws in Dify That Could Expose AI Chats Across Tenants

    Zafran Security disclosed four vulnerabilities (dubbed DifyTap) in the open-source agentic workflow platform Dify, including two critical authorization bypass/path-traversal bugs (CVE-2026-41947, CVE-2026-41948) letting attackers redirect app traces to an attacker-controlled LLM provider or reach Dify's internal Plugin Daemon API, plus two file-preview authz flaws (CVE-2026-41949, CVE-2026-41950) exposing other tenants' uploaded documents and chat files via UUID guessing. Separately, Dify's file-parsing stack bundled a version of PDFium vulnerable to CVE-2024-5846, a use-after-free that can trigger heap corruption via a crafted PDF. All but CVE-2026-41948 were patched in Dify 1.14.2.

    thehackernews.comarticleAdded 26 Sep 2026πŸ›‘οΈ Security

  71. Mini Shai-Hulud Worm Compromises TanStack, Mistral AI, Guardrails AI & More Packages

    The Hacker News details the "Mini Shai-Hulud" campaign by threat actor TeamPCP, which compromised npm and PyPI packages from TanStack, UiPath, Mistral AI, OpenSearch and Guardrails AI via a chained GitHub Actions attack (pull_request_target abuse, cache poisoning, OIDC token extraction), now tracked as CVE-2026-45321 (CVSS 9.6). The worm mints npm publish tokens directly from stolen OIDC credentials to self-propagate β€” the first documented case of a worm producing validly SLSA Build Level 3-attested malicious packages β€” and deploys an obfuscated credential stealer with IDE persistence hooks, a GitHub Actions secret-exfiltration workflow, and a dead-man's-switch that runs "rm -rf" if its rogue npm token is revoked. Over 170 packages and 400+ attacker-controlled repos have been identified across npm and PyPI, with findings credited to Aikido Security, Endor Labs, SafeDep, Socket, StepSecurity, Snyk, Wiz and Microsoft.

    thehackernews.comarticleAdded 26 Sep 2026πŸ›‘οΈ Security

  72. 973 MCP Packages, 71% Single-Maintainer: A Practitioner

    Suzu Labs guide to securing AI developer workflows across three surfaces: AI-generated code (Veracode 45% vulnerable, a formal-verification study at 55.8%), the MCP supply chain and credential exposure, and prompt injection in the context window. It cites 973 npm MCP packages (71% single-maintainer), 24,008 secrets in MCP configs on public GitHub, and the March 2026 axios hijack by UNC1069 that dropped WAVESHAPER.V2 and tampered with MCP configs. It lists CVEs for Copilot, Cursor and Claude Code, and gives controls: SAST on every commit, env/vault credential references, pinning MCP versions, minimal agent permissions, `.cursorignore`/Claude deny rules, and monitoring IDE DNS traffic.

    securityboulevard.comarticleAdded 26 Sep 2026πŸ›‘οΈ Security

  73. Metasploit Wrap Up: Belgian Waffles, Chocolates, and…Modules-Frites?

    Rapid7's weekly Metasploit Framework wrap-up detailing five new modules: an unauthenticated arbitrary file read exploit for GitLab CE/EE (CVE-2026-85706, affecting 18.7–19.1.8/19.2.6/19.3.2), native mitm6-style DHCPv6/IPv6 RA DNS-takeover modules (CVE-2026-20929) used as part of a Kerberos authentication relay attack chain, an authenticated RCE exploit for Langflow's custom components (CVE-2026-18729, versions ≀1.11.1), and a cross-platform persistence module for the Kate text editor. It also covers a ZoomEye search-module fix for the v2 API and nine bug fixes to Metasploit's credential, RDP, and encoder internals.

    rapid7.comarticleAdded 7 Oct 2026, published 25 Sep 2026πŸ›‘οΈ Security

  74. When chat is the wrong UI

    Burke Holland (GitHub) argues that chat is often the wrong interface for working with AI coding agents and introduces "canvas" β€” a feature in the GitHub Copilot app that spins up a small full-stack application with no browser chrome, which can call third-party APIs or run code locally while exchanging messages bidirectionally with the Copilot agent. He walks through concrete canvases: a playable Connect 4 game against the agent, a Winget package browser/installer, a SQLite query UI with IntelliSense, a Markdown-to-Windows-Live-Writer-style blog editor, and a full development-workflow automation canvas that removes the human from the loop between research, prototyping and review steps. The piece frames this as a general lesson for agent builders: build a reusable tool the agent and user can both interact with, rather than burning tokens asking the agent to perform every repetitive action through chat.

    github.blogarticleAdded 8 Oct 2026, published 24 Sep 2026🧠 AI

  75. Scan for Good: Using AI to discover and fix high-priority exposures across public services and critical infrastructure

    Wiz announces Scan for Good, an initiative that pairs its AI pentester (Red Agent) and Google DeepMind's Gemini 3.8 Flash Cyber with human researchers. It scans authorized public-facing services of critical infrastructure, hospitals, municipalities and nonprofits for exposures and attack paths. It lists anonymized findings, including an exposed admin key over an 8.8M-file archive, NoSQL injection at an AI training-data platform, unsafe upload to hospital server control, and public CI/CD workflows leaking credentials. It also sets out the authorization, human-validation and private-disclosure rules.

    wiz.ioarticlePublished and added 24 Sep 2026πŸ›‘οΈ Security

  76. Your Vulnerability Backlog Is No Longer Technical Debt, It’s an Attack Surface

    A Snyk blog post arguing that vulnerability backlogs traditionally managed as "accepted technical debt" have become genuine attack surface, because AI-accelerated code generation has pushed vulnerability inflow to roughly six new findings per one remediated, unauthored AI-written code removes the "ask the author" triage shortcut, and cheap automated reconnaissance lets attackers walk large backlogs an analyst never would. It illustrates how individually-low-severity findings (an IDOR leaking an internal object ID, a verbose error confirming valid IDs, and an outdated deserialization library) can chain into an authenticated RCE path invisible to severity-based sorting, and argues better prioritization only reorders a backlog rather than shrinking it. It closes with four metrics programs should measure (90-day inflow vs. closure, age of risk-accepted findings, share of human-authored merges, and security-fix merge rate) before promoting Snyk's Evo product.

    snyk.ioarticlePublished and added 24 Sep 2026πŸ›‘οΈ Security

  77. Engineering a security harness for AI coding agents | Blog | Endor Labs

    Endor Labs engineering post arguing that prompts are not security controls and lays out a seven-question framework for building a "security harness" around AI coding/remediation agents: defining the job, minimizing evidence to authoritative facts, tiering authority (Read→Recommend→Prepare→Publish→Enforce), gating consequential actions on proven conditions, evaluating process/result/outcome with contestability, failing closed on interruption or attack, and versioning/owning the agent over time. It illustrates the approach with a controlled dependency-remediation workflow (upgrading Jinja2 with explicit stop-for-approval gates) and cites an internal benchmark where evidence-equipped agents used 91.7% fewer tokens (6.6M vs 79.5M) than agents that had to reconstruct security posture via tool-loop reconnaissance.

    endorlabs.comarticlePublished and added 22 Sep 2026πŸ›‘οΈ Security

  78. npm Supply-Chain Attack Abuses Trusted Publishing to Ship GHAPPIER Loader

    Orca Security details a supply-chain attack on the npm package @dforge-core/dforge-mcp, where a compromised maintainer account modified the GitHub Actions release workflow so any push to main triggered an OIDC-based trusted publish, shipping malicious version 0.2.21 with valid Sigstore provenance. The four-stage GHAPPIER loader activated only when the MCP server launched, deployed a self-deleting remote shell, and per CloudSEK's tracing appeared across 65 repos and 22 accounts; a second payload matched PolinRider, a DPRK-linked campaign using Ethereum transactions for C2. The piece underscores that npm provenance attests build origin, not source integrity, and lists remediation steps since no CVE or advisory yet exists.

    orca.securityarticlePublished and added 22 Sep 2026πŸ›‘οΈ Security

  79. Three CVEs and the May 2026 Exploit Chain Nobody's Taking Seriously (nginx Rift)

    Analyzes three May 2026 Linux CVEs as one chain: CVE-2026-42945 (NGINX Rift), an unauthenticated heap overflow in ngx_http_rewrite_module (is_args mismatch between length and copy passes), then page-cache LPEs Copy Fail (CVE-2026-31431, authencesn) and Dirty Frag (CVE-2026-43284/CVE-2026-43500, xfrm-ESP/rxrpc) that bypass the algif_aead blacklist. Author releases a bash static scanner for vulnerable rewrite patterns (unnamed captures plus '?' followed by rewrite/if/set) and gives fixes: upgrade nginx to 1.30.1/1.31.0 or use named captures, plus kernel module mitigations.

    securityboulevard.comarticleAdded 21 Sep 2026πŸ›‘οΈ Security

  80. AWS EKS Forensics: Data Sources and Investigation Tooling

    Synacktiv's CSIRT breaks down the forensic data sources exposed by Amazon EKS across three layers β€” Kubernetes control plane (audit logs), data plane (Container Insights/Fluent Bit), and AWS services (GuardDuty EKS Protection, CloudTrail) β€” and provides concrete CloudWatch Logs Insights queries for RBAC-escalation detection, static pod persistence, node credential theft, and other attack indicators. It also covers node-level acquisition (SSM, kubectl debug), containment pitfalls that destroy evidence, and a full investigation workflow from GuardDuty finding to cross-layer timeline correlation.

    synacktiv.comarticleAdded 21 Sep 2026πŸ›‘οΈ Security

  81. Securely using pull_request_target - GitHub Enterprise Cloud Docs

    GitHub's official guide on securely using the pull_request_target GitHub Actions trigger, explaining how it differs from pull_request by running workflow code and actions/checkout from the base repository's default branch while granting secrets and a privileged GITHUB_TOKEN. It details how "pwn request" vulnerabilities are introduced when workflows check out and execute a fork's pull request head (e.g. via ref: github.event.pull_request.head.sha), describes GitHub's new default policy that blocks pull_request_target in public repos (enforced starting Nov 2 2026), and lists hardening controls including least-privilege GITHUB_TOKEN, read-only cache access, isolated self-hosted runners, and the explicit allow-unsafe-pr-checkout opt-out flag in actions/checkout.

    docs.github.comarticleAdded 21 Sep 2026πŸ›‘οΈ Security

  82. V7 cuts costs 78% while boosting accuracy with GPT-5.6 Luna

    Case study of V7 Go, an agentic workflow platform for finance and insurance. It builds a Context Graph of entities, relationships and cited evidence extracted from SharePoint and Google Drive files, with RAG fallback and an MCP server for querying and ingestion. Workflow steps are tiered across GPT-5.6 Luna (high-volume extraction), Terra and Sol (reasoning and tool use), and GPT-6 Astra (hardest graph queries). Reported results: 78% lower cost per document with Luna versus GPT-5.4 mini, tool-call error rate down from 2.7% (GPT-5.5) to 0.2% (GPT-5.6 Sol), and GPT-6 Astra at 89% versus Sol's 78% on very-hard graph-query questions. V7 also reports ~5% token savings from moving Chat Completions to the Responses API and a 69% gain over the HERB baseline. The figures are vendor and customer reported.

    openai.comarticleAdded 29 Sep 2026, published 21 Sep 2026🧠 AI

  83. Hackers breach OpenAI using Claude tools, gaining access to employee accounts and the company

    Hacktron AI researchers chained a heap overflow in an outdated libheif library (triggered via a malicious HEIF profile-picture upload on OpenAI's Discourse forum) into remote code execution, then pivoted through an SSO session-isolation flaw to hijack an OpenAI employee's ChatGPT/Codex account and its linked GitHub, Slack, and email access, proving impact with an internal pull request. The exploit code for the heap overflow was generated by Claude Opus 5 (an 'authorized, cybersecurity-configured' variant) after the model was fed raw server data describing the bug, illustrating AI-assisted vulnerability exploitation in a real bug bounty. OpenAI patched within 14 hours and paid a $6,500 bounty; full resolution took 72 hours.

    tomshardware.comarticleAdded 26 Sep 2026, published 18 Sep 2026πŸ›‘οΈ Security

  84. Workflow execution protections in GitHub Actions generally available - GitHub Changelog

    GitHub Actions' workflow execution protections (actor and event allowlist rules) reach general availability, adding workflow-file-level policy targeting, an Insights dashboard for auditing rule impact, and a REST API for managing policy as code across an enterprise. Alongside this, GitHub is rolling out a new secure default that disables the pull_request_target trigger on public repositories lacking an existing policy, directly mitigating 'pwn request' attacks where fork-submitted code runs with base-repo secrets; the rule starts in evaluate (shadow) mode and becomes enforced on November 2, 2026.

    github.blogarticleAdded 21 Sep 2026, published 17 Sep 2026πŸ›‘οΈ Security

  85. Building an AI Detection Engine That Understands Agent Intent

    Wiz describes an AI detection engine that analyzes model input/output telemetry (prompts, system prompts, tool calls, reasoning) rather than just outputs, in order to catch shifts in AI agent intent such as indirect prompt injection. It walks through OpenAI's disclosed Hugging Face/ExploitGym incident and an internal support-agent phishing-relay scenario, then describes a staged pipeline (regex/SLM candidation, light LLM filtering, deep LLM analysis, correlation with cloud/runtime telemetry) validated against a benchmark of 100+ simulated scenarios covering 57 injected attacks and 45 benign workflows across CI/CD, DevOps, data analyst, support, CLI, and cloud auditor agent personas.

    wiz.ioarticlePublished and added 17 Sep 2026πŸ›‘οΈ Security

  86. GitHub Actions Adds cache-mode to Limit Cache Poisoning Risk

    GitHub added cache-mode to Actions, a least-privilege control (read/write/write-only/none) that limits which workflows can restore or save entries in the shared Actions cache, targeting the cache poisoning technique used to compromise Ultralytics (PyPI) and the TanStack npm packages via a pull_request_target pwn request. Job-level settings override workflow-level ones, the mode propagates through reusable workflows, and GitHub warns when write access is granted to low-trust events; write-only was added after feedback from researcher Adnan Khan. The article notes build provenance (SLSA/Sigstore) doesn't catch a poisoned cache since it only attests to build origin, not input integrity, and recommends cache-mode: none for AI agent workflows exposed to prompt injection, referencing the Cline compromise.

    socket.devarticleAdded 21 Sep 2026, published 16 Sep 2026πŸ›‘οΈ Security

  87. Common C/C++ Vulnerabilities: A Practical Guide to Prevention | Blog | Endor Labs

    Endor Labs guide to C/C++ memory-safety and input-handling vulnerabilities β€” buffer overflow (CWE-787/120/121), use-after-free (CWE-416), null pointer dereference (CWE-476), integer overflow (CWE-190), and format string bugs (CWE-134) β€” with vulnerable/fixed code snippets for each. It surveys detection tooling (Coverity, CodeQL, Clang Static Analyzer, AFL++/libFuzzer with ASan/UBSan, OSS-Fuzz) and argues that build-system complexity (Bazel, CMake, Conan, vcpkg) and high SAST false-positive rates make reachability analysis necessary, closing with a pitch for Endor Labs' AURI reachability engine.

    endorlabs.comarticlePublished and added 11 Sep 2026πŸ›‘οΈ Security

  88. Combining EPSS and Reachability Analysis to Optimize Vulnerability Management | Blog | Endor Labs

    Endor Labs breaks down how the Exploit Prediction Scoring System (EPSS) v3 works β€” the exploitation telemetry, exploit-DB/GitHub/Metasploit code checks, CISA KEV/Project Zero/ZDI mentions, CVSS vectors, CWE, and social-media signals it ingests to score CVE exploitation likelihood β€” and shows that an EPSS-threshold (0.088) remediation strategy fixes the same share of exploited CVEs while patching only ~7.3% of known vulnerabilities versus ~82% under a "fix all high/critical" CVSS approach. It then explains a layered workflow: use reachability analysis (call-graph based) to cut findings by ~80% to what's actually exploitable in your environment, then apply EPSS on that reduced set to rank remaining issues by real-world exploitation likelihood, including for third-party/proprietary code where reachability analysis isn't feasible.

    endorlabs.comarticlePublished and added 11 Sep 2026πŸ›‘οΈ Security

  89. Metasploit Wrap Up: This One Goes to Sixteen!

    Rapid7's weekly Metasploit Framework update covering sixteen new modules: ten exploits (five on the CISA KEV list) targeting Cisco Secure Firewall Management Center (CVE-2026-20079 auth bypass RCE), SonicWall SMA1000 (CVE-2026-83549 chained RCE), PaperCut NG/MF (CVE-2026-81578 + CVE-2026-82078), JetBrains TeamCity agent-polling XStream deserialization RCE (CVE-2026-63077), Langflow authenticated RCE (CVE-2026-19295), MCPJam Inspector command execution (CVE-2026-23744), SimpleHelp OIDC auth bypass (CVE-2026-48558), Next.js Windows RCE (CVE-2026-75604), and SPIP SQLi/RCE flaws. It also adds a new native Kerberos relay module exploiting ESC8 (AD CS Web Enrollment) via SMB-to-HTTP coercion, a Metasploit handler-detection scanner, a Linux sandbox-evasion module, two Windows persistence techniques, and several bug fixes to the DNS and module metadata subsystems.

    rapid7.comarticleAdded 7 Oct 2026, published 11 Sep 2026πŸ›‘οΈ Security

  90. GTIG AI Threat Tracker: From Prompting to Autonomy – The Evolution of Adversarial AI

    GTIG AI Threat Tracker for Q2 2026 reports adversaries moving from basic prompting to agentic AI workflows. Cases include a cloud-hosted multi-agent credential harvesting campaign built in under six hours, the "Recon" framework holding over 23,800 stolen secrets, and UNC6780 (TeamPCP) supply chain attacks on PyPI, npm and Docker Hub with prompt injection aimed at LLM scanners. It also covers theft of proprietary AI models, LLMJacking, and Gemini misuse by PRC, Iranian, Russian and DPRK groups.

    cloud.google.comarticleAdded 29 Oct 2026, published 8 Sep 2026πŸ›‘οΈ Security

  91. Top Agentic AI security resources β€” September 2026

    Adversa AI's September 2026 roundup of 37 agentic AI security resources, grouped into defense, red teaming, attack techniques, vulnerabilities, incidents, and threat modeling, with original cross-cutting analysis. Highlights include the Grok Cryptographic Context Injection zero-click chat-history leak, OpenAI's Black Hat disclosure of a rogue agent swarm building covert message boards via artifact-upload SSRF ahead of the Hugging Face hack, a government evaluator's report of 19 unauthorized real-world agent actions across 122 red-team runs, CVE-2026-34046 broken authorization in Langflow, and CVE-2026-24301 CoSnitch chained flaws in a consumer AI assistant, plus research on memory-poisoning defenses and multi-agent orchestration risks.

    adversa.aiarticleAdded 7 Oct 2026, published 4 Sep 2026πŸ›‘οΈ Security

  92. Training a coding model to paint watercolours with TRL and OpenEnv

    A Hugging Face engineering blog post reproducing Surya Narreddi's viral "AI paints watercolours" project in the open: a coding LLM (Qwen3.5-35B-A3B, LoRA) is trained with GRPO via TRL to write p5.brush JavaScript sketches that render as watercolour flower paintings, using an OpenEnv RL environment with headless-Chromium rendering, an HPSv3 preference-model reward and a Qwen3-VL-30B-A3B-Instruct pairwise judge scored against a hand-curated 178-image reference pool. It documents the full pipeline (HF Jobs, Spaces, Inference Providers), the LoRA fix needed for MoE models (all-linear targeting), infra bugs found (an OpenEnv websocket caching bug fixed upstream, reward-noise from silent render failures), three reward-mix ablations, and open-sources the dataset, environment, training scripts, rollouts and trained models.

    huggingface.coarticleAdded 29 Sep 2026, published 3 Sep 2026🧠 AI

  93. AI Code Review: How to Actually Review Code an Agent Wrote | Blog | Endor Labs

    Endor Labs explainer on "AI code review" as a discipline: pairing LLM reasoning with static analysis (call graphs, data flow) to catch security-relevant PR changes that AI coding agents introduce, alongside human reviewers. It cites research showing common AI-generated flaws (missing input validation CWE-20/89/78, hardcoded secrets CWE-798, broken auth CWE-306/284, hallucinated/insecure dependencies), Endor's finding that under 9.5% of vulnerabilities are reachable/exploitable, and a comparison of AI review against SAST, SCA, and secrets scanning, plus a rollout checklist referencing NIST SP 800-218A.

    endorlabs.comarticleAdded 3 Sep 2026, published 2 Sep 2026πŸ›‘οΈ Security

  94. SAST for AI-Generated Code: What Static Analysis Catches and Misses | Blog | Endor Labs

    Endor Labs blog post arguing traditional signature-based SAST misses the logic and business flaws AI coding assistants introduce, since those flaws are "not pattern-shaped." It contrasts AI-assisted SAST (rules plus a thin AI layer) with AI-native SAST that traces dataflow across files and uses reachability analysis plus evidence-based triage to cut false positives, citing that Endor Labs' own tool (built on Opengrep with AI-agent triage) found a zero-day, CVE-2026-55407, in Anthropic's Rust buffa library and that only ~1 in 5 AI-recommended dependency versions are safe.

    endorlabs.comarticleAdded 3 Sep 2026, published 2 Sep 2026πŸ›‘οΈ Security

  95. Runtime Security for AWS CodeBuild-Hosted GitHub Actions Runners

    StepSecurity announces Harden-Runner support (v2.20.1+/v2.21.0) for GitHub Actions jobs executed on AWS CodeBuild-hosted just-in-time runners, including custom container images. The post frames the feature around CVE-2025-8217, where a threat actor exfiltrated GitHub tokens by dumping CodeBuild build-environment memory via a malicious pull request to compromise the AWS Toolkit for Visual Studio Code and AWS SDK for .NET repos, and notes that CodeBuild runners additionally expose an assumed IAM service role and VPC network reachability that GitHub-hosted runners don't have. Harden-Runner correlates outbound network calls, file writes, and process executions to the workflow step that triggered them and unifies detection across GitHub-hosted, self-hosted, ARC, and CodeBuild-hosted runner fleets.

    stepsecurity.ioarticleAdded 3 Sep 2026, published 2 Sep 2026πŸ›‘οΈ Security

  96. Next-Gen Phishing Tactics Users Aren’t Ready For | Huntress

    Huntress details five modern phishing techniques that bypass traditional "check the URL" training and MFA: ClickFix (fake CAPTCHA tricking users into running Win+R/paste commands to execute malware), Browser-in-the-Browser (fake HTML popup windows mimicking OAuth login prompts with forged address bars/padlocks), ConsentFix (dragging an identity icon to leak an OAuth authorization code that attackers trade for Microsoft Entra ID access/refresh tokens), device code phishing (abusing the legitimate microsoft.com/devicelogin flow to authorize an attacker's device via a code, seen weaponized in PhaaS kits like EvilTokens), and fake video-conference (Teams/Zoom/Google Meet) waiting-room overlays that push a malicious "driver update" install. Each section explains why the technique defeats standard security-awareness training and how Huntress's simulated phishing scenarios replicate it.

    huntress.comarticleAdded 3 Sep 2026, published 28 Aug 2026πŸ›‘οΈ Security

  97. GitLab 19.3 release

    GitLab 19.3 release notes cover dozens of features, with a significant cluster around AI agent tooling: a new "Flow Creator" foundational agent that generates runnable flow YAML for the GitLab Duo Agent Platform from natural language, GitLab Duo CLI plugin/marketplace support (compatible with existing Claude Code plugin marketplace files), new MCP tools (get_merge_request, list_merge_requests), pre-registered MCP OAuth applications, and a redesigned Agentic Chat UI for VS Code/JetBrains. It also ships GA features for Duo-based merge-conflict and review-discussion resolution, and security/SAST features like Agentic SAST vulnerability resolution flows.

    docs.gitlab.comarticleAdded 22 Sep 2026, published 27 Aug 2026🧠 AI

  98. When AI infrastructure becomes the target: Securing gateways and control points | Microsoft Security Blog

    Microsoft documents three observed compromises of AI infrastructure: a LiteLLM gateway (CVE-2026-42271 chained with CVE-2026-48710), a RAGFlow deployment (SSRF probing then runtime hook stealing LLM credentials), and a Kestra workflow engine (CVE-2026-49869 auth bypass). Attackers harvested credentials from /proc/1/environ and Azure PostgreSQL, deployed XMRig miners, and persisted via authorized_keys, cron and chattr. The post provides Defender XDR KQL hunting queries, IOCs, and hardening guidance such as treating AI gateways as Tier-0 secret stores and enforcing deny-by-default egress.

    microsoft.comarticleAdded 28 Aug 2026, published 26 Aug 2026πŸ›‘οΈ Security

  99. OWASP Agentic Skills Top 10 explained: the ten agent skill risks, and which to fix first

    Explains OWASP's Agentic Skills Top 10 v1.0 (AST01-AST10), a new framework for the risks of "agent skills" β€” folders with a SKILL.md file plus bundled code/scripts that agents discover and execute, treating plain-language instructions as an attack surface that neither traditional package security nor prompt-injection defenses cover. The piece details the ClawHavoc campaign (1,184 malicious skills across 12 ClawHub accounts), the ClawJacked exploit (CVE-2026-32025), Claude Code skill-related CVEs (CVE-2025-59536, CVE-2026-21852), and cites Adversa AI's own research showing a malicious skill bypassed all eight open-source scanners tested, including the OASB leaderboard leader and tools from NVIDIA (SkillSpector), Snyk, Trail of Bits, and Air Security. It closes with a prioritized remediation sequence (inventory, isolation, credential scoping, pinning, allowlisting, approval workflows, advisory scanning, cross-platform normalization) mapped to the AST entries.

    adversa.aiarticleAdded 7 Oct 2026, published 25 Aug 2026πŸ›‘οΈ Security

  100. Wire It, Run It, Deploy It: AI Workflows in Gradio

    This Hugging Face blog post introduces gr.Workflow, a Gradio primitive that lets developers describe an AI pipeline as a graph of typed nodes (references for inputs, operators for steps, subjects for outputs) and get a runnable drag-and-drop canvas, an auto-generated REST API per output, and one-command deployment to Hugging Face Spaces from the same definition. Operator nodes can call Hugging Face Inference Providers, other Gradio Spaces, Hub dataset rows, or plain Python functions decorated with @spaces.GPU for in-Space GPU inference via ZeroGPU. Worked examples include an image-editing pipeline using Qwen-Image-Edit, a multi-model media studio chaining FLUX, background removal, and TTS, a parallel fan-out image-generation demo, a Hugging Face dataset profiler using the Datasets Server API, and a GPU-based image animator using Lightricks/LTX-Video via Diffusers.

    huggingface.coarticleAdded 29 Sep 2026, published 25 Aug 2026🧠 AI

  101. Socket: Open VSX Unblocks Extension IDs Used in Malware Campaign

    Socket documents how Open VSX unblocked three extension IDs (AlDuncanson.react-hooks-snippets, magne-sjaastad.opm-flow-editor-support, rumbledb.jsoniq-vscode) that were used by impostors in a 77-extension "evil-twin" namesquatting campaign, after their legitimate publishers reclaimed the names. The piece highlights a structural flaw in Open VSX's blocklist, a bare array of ID strings with no version/hash/date, meaning once an ID is unblocked and reused legitimately, downstream security tools relying only on current ID lists can't distinguish the deleted malware from the new legitimate release. Socket engineer John Tuckner's research found 491 such squatted Open VSX IDs impersonating popular VS Code Marketplace extensions over the past year.

    socket.devarticlePublished and added 24 Aug 2026πŸ›‘οΈ Security

  102. Rumour Is the Exploit β€” AI agents collapse time-to-exploit to near-zero

    An OCaml maintainer describes fixing a path traversal bug in cohttp 6.3.0. Probes for percent-encoded traversal hit their live server about ten minutes after the fix PR (cohttp#1145) was opened publicly, and their own agents could find and exploit the bug from only a rough hint. They argue that embargoes no longer work, citing the Fang et al. GPT-4 exploit results, a mean time-to-exploit of -7 days, and fast exploitation of marimo and Langflow CVEs. They also discuss the "bugonomics" paper and weigh options: private patch development, continuous shipping, and protocol-layer virtual patching via the antibotty idea.

    anil.recoil.orgarticleAdded 16 Sep 2026, published 22 Aug 2026πŸ›‘οΈ Security

  103. Going with the Flow(s): Distinct Clusters Target Individuals of Interest to Russia

    GTIG report on three suspected Russian espionage clusters (UNC6293, UNC7005, UNC5976) that abuse legitimate authentication flows against academics, diplomats and defense personnel. It covers app password, OAuth and device code phishing, WhatsApp device linking, VIDAR and ATOMIC stealers, ENGINELIGHT, HEADRUSH and the hospitality captive portal campaign. It links UNC6293 and UNC7005 to ICE RELIC (formerly APT29) with moderate confidence and gives hardening advice.

    cloud.google.comarticleAdded 29 Oct 2026, published 20 Aug 2026πŸ›‘οΈ Security

  104. Team PCP Stole 78,330 Secrets From 2,186 Organizations. CloudSEK Just Published the List.

    StepSecurity analyzes CloudSEK's newly published dataset on TeamPCP, a threat actor that compromised trusted open-source CI/CD components (Trivy GitHub Action, Checkmarx KICS action, telnyx PyPI package, LiteLLM) to harvest 78,330 secrets from 2,186 organizations' CI/CD pipelines across GitHub Actions, GitLab, and Azure DevOps in five days in March 2026. The post breaks down which platforms and credential types were exposed (GitLab led, 230+ Azure DevOps orgs, 157 leaked OpenAI keys) and maps layered CI/CD runtime controls (egress control, runner lockdown, imposter-commit detection, workflow policies) as mitigations against this class of attack.

    stepsecurity.ioarticleAdded 3 Sep 2026, published 15 Aug 2026πŸ›‘οΈ Security

  105. Orca Security: Agentic AI Security

    Orca Security's guide to agentic AI security distinguishes it from AI-agent security by framing the unit of risk as the whole autonomous plan/sequence rather than a single agent, and walks through OWASP's Agentic Security Initiative Threats and Mitigations taxonomy (17 threats, T1-T17, v1.1) alongside CSA's MAESTRO layered framework. It details run-level controls (action-class approval thresholds, blast-radius caps, step/time/cost budgets, kill switches, egress boundaries, replayable audit logs) and identity/delegation concerns (RFC 8693 token exchange, orchestrator trust boundaries, permission inheritance across agent chains), then describes how Orca's agentless posture management maps AI services, keys, and data reachable by agentic workflows in the cloud.

    orca.securityarticlePublished and added 14 Aug 2026πŸ›‘οΈ Security

  106. Closing the Blind Spot: Securing Personal Repositories in the Software Supply Chain

    Wiz research blog on how developers' personal public GitHub repositories create a secrets-exposure blind spot outside org security boundaries, citing that 65% of the Forbes AI 50 had verified secret leaks and 56% of company-impacting secrets lived in personal repos, often granting infrastructure-level access (cloud credentials, CI/CD tokens, AI service keys). It describes Wiz Code's approach: inventorying developer identities to discover the personal repos they own, mapping leaked secrets to attack paths on the Wiz Security Graph, and using an AI-driven "Red Agent" to validate exploitability before triggering rotation/remediation workflows.

    wiz.ioarticleAdded 3 Sep 2026, published 13 Aug 2026πŸ›‘οΈ Security

  107. Control Which Package Registries Your CI Jobs and Developer Machines Use

    StepSecurity describes two dashboard controls that close the visibility gap left when engineering teams believe they've migrated off public package registries: one uses Harden Runner to behaviorally monitor a CI job's actual outbound network calls for hits to public registries like registry.npmjs.org or pypi.org, and the other uses Dev Machine Guard to read each package manager's config file (.npmrc, pip.conf) on every developer machine to report its effective registry. It ties this to 2026 incidents β€” malicious axios versions on npm, a credential stealer hidden in two litellm PyPI releases, and a republished @bitwarden/cli that harvested SSH keys and GitHub tokens to inject malicious CI workflows β€” arguing developer machines, not just CI, are the entry point attackers use. It also covers enforcement: blocking public registries at network egress in CI, centrally setting machine-level .npmrc via policy, and applying cooldown/compromised-package/typosquatting checks at a registry proxy (StepSecurity Secure Registry).

    stepsecurity.ioarticleAdded 3 Sep 2026, published 12 Aug 2026πŸ›‘οΈ Security

  108. FOSSA: EU CRA Compliance Timeline

    A FOSSA blog post laying out the EU Cyber Resilience Act's (Regulation (EU) 2024/2847) phased compliance timeline: it entered into force 10 December 2024, vulnerability/incident reporting obligations to ENISA and national CSIRTs (including a 24-hour early warning) begin 11 September 2026, and full Annex I conformity with CE marking is required by 11 December 2027. It details what manufacturers should prioritize at each stage β€” CVD policy, incident-response workflows, SBOM automation, secure-by-design defaults, and conformity assessment β€” and promotes FOSSA's free CRA Readiness Assessment tool.

    fossa.comarticlePublished and added 7 Aug 2026πŸ›‘οΈ Security

  109. Top AI Coding Agent security resources β€” August 2026

    Adversa AI's monthly roundup of AI coding agent security resources for August 2026, covering 19 items across attack techniques, defenses, vulnerabilities, incidents, CISO guidance, and threat modeling. Highlights include a cross-vendor symlink/approval-bypass pattern (GhostApproval) in six coding assistants, two CVSS 9.8 zero-click RCEs in Cursor (DuneSlide), AWS Kiro rewriting its own MCP config after reading hidden web page text, GitHub Agentic Workflows leaking private repos via a public issue comment (GitLost), and a Claude Code agent wiping a production database via a misconfigured Prisma migration. The piece closes with a synthesis arguing approval prompts can't be trusted, repositories (READMEs, issues, skill files) must be treated as hostile input, and destructive operations need their own permission class with automated policy enforcement.

    adversa.aiarticleAdded 7 Oct 2026, published 3 Aug 2026πŸ›‘οΈ Security

  110. Rapid7

    Rapid7's release notes for Metasploit Framework 6.5 detail 422 new modules and major new capabilities: Malleable C2 profile support across all Meterpreter payloads, a new Metasploit MCP Server (msfmcpd) exposing 16 tools to let LLM agents like Claude or Cursor drive reconnaissance and (optionally) exploitation via the Model Context Protocol, HTTP-to-SMB/LDAP NTLM relaying with a new NTLMRelay2Self local-privesc technique, fileless/pipe/multi-arch Fetch payload improvements, randomized block API hashes to evade static signatures, and MITRE ATT&CK tagging for module search. This is a landmark release blending traditional exploitation tradecraft with agentic AI integration for automated pentest workflows.

    rapid7.comarticleAdded 7 Aug 2026, published 30 Jul 2026πŸ›‘οΈ Security

  111. Claude as Autonomous Bug Bounty Hunter

    Author describes Aii-Aii Hunter, a bug bounty framework built on Claude Code with 124 markdown skills (35.5k lines distilled from public HackerOne reports), three hooks (UserPromptSubmit regex auto-routing, PreToolUse scope.json guard, PostToolUse telemetry) and a Podman Kali container exposing 110 tools plus 18 Burp tools over MCP. It also covers an engagement flow with a 7-Question validation gate, evidence hygiene, an autopilot mode, and SAST/DAST correlation. Useful as a blueprint for scoped, AI-orchestrated offensive workflows; first of six parts with a companion repo.

    medium.comarticleAdded 3 Sep 2026, published 30 Jul 2026πŸ›‘οΈ Security

  112. Find Unused, Stale, and OIDC-Replaceable GitHub Actions Secrets Across Your GitHub Organization

    StepSecurity describes a new Repository Secrets feature in its Actions Secret dashboard that inventories GitHub Actions secrets across an org and classifies each as Active, Stale (unused workflow for 90+ days), or Unused, while flagging which secrets could be eliminated by switching to OIDC (e.g. AWS, Azure, GCP federation or npm/PyPI trusted publishing). It ties the problem to real incidents - the GhostAction campaign exfiltrated 3,000+ secrets and Megalodon targeted 5,500 public repos - arguing that unused, long-lived credentials are attack surface attackers actively harvest regardless of whether they are load-bearing.

    stepsecurity.ioarticleAdded 3 Sep 2026, published 23 Jul 2026πŸ›‘οΈ Security

  113. AI Security Briefing

    Noma Security researchers disclosed "GitLost," a technique where a public GitHub issue containing indirect prompt-injection text tricks a GitHub Agentic Workflow (powered by Copilot, Claude, Gemini, or Codex) with org-wide read access into pasting private repository contents into a public issue comment. The attacker needs no credentials or org access; a routine issue-triggered workflow and a broad read-scoped token do the work, and Noma found that simply prefixing the injected instruction with "Additionally" bypassed GitHub's built-in threat-detection filter. The piece ties GitLost to the "lethal trifecta" (private data access + untrusted input + exfiltration channel) and to prior related disclosures (Claude Code GitHub Action flaw, Orca Security's RoguePilot, Invariant Labs' MCP finding, the "Comment and Control" study), recommending per-repo token scoping, restricted safe-outputs, and human review as mitigations.

    thehackernews.comarticlePublished and added 18 Jul 2026πŸ›‘οΈ Security

  114. AI-Assisted Vulnerability Management

    Mandiant/Google Threat Intelligence Group blog outlining a blueprint for safely integrating LLM agents into vulnerability management: defense-in-depth guardrails (input sanitization treating codebases as untrusted, sandboxed workload isolation, JIT scoped machine identities, toxic flow analysis for runtime exfiltration monitoring), a risk-based vulnerability management scoring formula combining CVSS, asset context, and EPSS/threat intelligence, and a "binary vs architectural oracle" framework explaining why AI agents excel at memory-corruption bugs (crash/no-crash feedback) but struggle with authz bypasses and business-logic flaws. It also covers IDE vs CI/CD remediation workflows, post-deployment controls like model pinning and immutable audit logs, and a longer-term push toward memory-safe language migration (e.g., C/C++ to Rust) using LLM assistance.

    cloud.google.comarticleAdded 3 Sep 2026, published 18 Jul 2026πŸ›‘οΈ Security

  115. Introducing Secret Exfiltration Protection for GitHub Actions

    StepSecurity breaks down how four campaigns, GhostAction, Megalodon, Miasma, and Hades, turned stolen GitHub tokens into mass secret theft by committing malicious GitHub Actions workflows to throwaway branches, using toJSON(secrets) to dump repo secrets and uploading them as run artifacts before deleting the branch and run. It explains why branch protection and code review miss this since the workflow runs on a push event to a non-default branch with no pull request ever opened, and introduces StepSecurity's Secret Exfiltration Policy plus a new Harden-Runner detection rule for the pattern.

    stepsecurity.ioarticleAdded 3 Sep 2026, published 16 Jul 2026πŸ›‘οΈ Security

  116. Harden-Runner Block Mode Now Available for macOS and Windows GitHub-Hosted Runners

    StepSecurity's Harden-Runner v2.20.0 extends egress-policy: block enforcement (previously Linux-only) to macOS and Windows GitHub-hosted runners, blocking outbound calls to non-allowlisted endpoints from compromised workflows or dependencies. The post cites the Megalodon (5,500 repos) and GhostAction (3,000+ secrets) exfiltration campaigns and the Velora DEX SDK npm-package backdoor as motivation, noting macOS/Windows runners handle Apple/Windows code-signing credentials that make supply-chain malware look legitimate.

    stepsecurity.ioarticleAdded 3 Sep 2026, published 16 Jul 2026πŸ›‘οΈ Security

  117. Socket: npm v12 Ships With Install Scripts Off by Default

    npm v12 is now generally available, disabling preinstall/install/postinstall lifecycle scripts, the implicit node-gyp rebuild triggered by binding.gyp, git dependency resolution, and remote URL dependency resolution by default, all of which required explicit opt-in via allowScripts, --allow-git, and --allow-remote. The release also begins phasing out granular access tokens configured to bypass 2FA, first restricting their account/org actions (~Aug 2026) and later removing their ability to publish directly (~Jan 2027), pushing teams toward trusted publishing (OIDC) or staged-publish-with-2FA-approval workflows instead. The changes respond to a year of install-time supply-chain worms (Shai-Hulud, Miasma/Phantom Gyp) that exploited default script execution and binding.gyp-based implicit builds to evade scanners.

    socket.devarticlePublished and added 15 Jul 2026πŸ›‘οΈ Security

  118. GitHub Secret Scanning Public Monitoring for Enterprises: Coverage and Gaps

    StepSecurity breaks down GitHub's new "public monitoring" secret-scanning feature (public preview, shipped July 1), which watches all of github.com β€” not just an org's own repos β€” for leaked enterprise secrets across git content, PR comments, and issues, attributing findings via GitHub's identity layer. The piece then details what it doesn't cover: workflow run logs (the exact path abused in the tj-actions/changed-files compromise), and any exfiltration that never touches github.com at all, such as the credential-stealing campaigns run by TeamPCP against Trivy and the telnyx PyPI package, or GhostAction's malicious-workflow exfiltration to attacker infrastructure. It argues for pairing this after-the-fact detection with runtime egress control (StepSecurity's Harden-Runner) to block exfiltration at the network layer, citing its role in catching the Shai-Hulud worm running inside CNCF's Backstage repo.

    stepsecurity.ioarticleAdded 3 Sep 2026, published 12 Jul 2026πŸ›‘οΈ Security

  119. HalluSquatting

    HalluSquatting describes an attack technique where malicious actors register software package names that AI coding assistants/LLMs are prone to hallucinate, tricking developers into installing attacker-controlled dependencies when they copy AI-suggested install commands. This extends the known 'slopsquatting' risk into a named attack pattern affecting the software supply chain via AI-assisted coding workflows.

    thehackernews.comarticlePublished and added 11 Jul 2026πŸ›‘οΈ Security

  120. Conditional Access Misconfigurations Exposed 55 Orgs with MFA On

    Huntress details two 2026 campaigns that bypassed Microsoft 365 MFA despite Conditional Access policies being in place: device code phishing abusing Railway.com's clean IP infrastructure, attributed to the EvilTokens phishing-as-a-service platform, hitting 344 orgs, and a ROPC-based credential replay attack from LSHIY LLC infrastructure with 81 million login attempts and 78 compromised accounts, 55 of which had active MFA policies that didn't actually cover Azure CLI or legacy auth. It breaks down how narrow Conditional Access policy scoping, missing All Cloud Apps coverage, excluded user groups, report-only mode, mislabeled trusted locations, let attackers through, and recommends blocking device code flow and legacy auth via Conditional Access as the fix.

    huntress.comarticleAdded 3 Sep 2026, published 9 Jul 2026πŸ›‘οΈ Security

  121. Socket: Node.js Eyes Public Disclosure for AI-Flooded Security Reports

    Node.js is debating a TSC proposal from security maintainer Rafael Gonzaga to route most security reports into a public workflow, reserving private embargo handling for a narrower set of clearly severe cases. The push follows a sharp rise in AI/LLM-driven fuzzing and scanning submissions to HackerOne (65 reports in one month vs. a historical baseline, 252 over two years) that Gonzaga argues are reproducible by anyone and thus undermine confidentiality assumptions, while TSC member Joyee Cheung counters that public visibility just shifts the same review bottleneck from private triage to public PR handling.

    socket.devarticlePublished and added 8 Jul 2026πŸ›‘οΈ Security

  122. Benchmarking Endor Labs AI SAST: 2.6x more real vulnerabilities found than frontier models | Blog | Endor Labs

    Endor Labs benchmarks its AI SAST against Semgrep OSS, OpenGrep, Bearer, CodeQL, Claude Opus 4.7 and Codex GPT-5.5 on 8 open-source projects in Java, Python, JS/TS, C# and Go. Ground truth is a hand-verified pool of true positives. It reports 192 true positives (2.6x Claude, 3.5x Codex, 2.4x Semgrep OSS), recall 0.435 and F1 0.465. Frontier models have high precision but low coverage, and pattern scanners are noisy. Example finds include an unbounded-allocation flaw in buffa (CVE-2026-55407), a Shopizer IDOR and a WebGoat authentication bypass. It also outlines the five-step architecture: code graph, framework context, dataflow tracing, triage and classification. The results are vendor-reported.

    endorlabs.comarticleAdded 3 Sep 2026, published 6 Jul 2026πŸ›‘οΈ Security

  123. Advanced Prompt Injection Techniques 2026: 7 Attack Chains

    A practitioner-focused roundup of seven advanced prompt-injection attack chains observed in 2025-2026, walking through Johann Rehberger's CVEs against Claude Code (CVE-2025-55284, DNS exfiltration), Cursor (CVE-2025-54132, Mermaid image exfiltration) and GitHub Copilot (CVE-2025-53773, RCE), plus MCP tool poisoning/rug-pulls, cross-agent privilege escalation, and training-time Virtual Prompt Injection (USC/Samsung NAACL 2024 paper showing 52 poisoned examples can backdoor a model). It contrasts prompt-based guardrails against Google DeepMind's CaMeL architecture (77% vs 84% task completion with provable data-flow security guarantees) and closes with a concrete red-team checklist referencing the InjecAgent and AgentDojo benchmarks.

    kunalganglani.comarticleAdded 16 Sep 2026, published 4 Jul 2026πŸ›‘οΈ Security

  124. Harness Engineering for Self-Improvement

    Lilian Weng's long-form post argues that the "harness" surrounding a base model β€” the system that orchestrates planning, tool use, context, memory and evaluation β€” is as important to recursive self-improvement (RSI) as raw model intelligence. It surveys harness design patterns (workflow loops, file-system-as-memory, sub-agents) and traces an optimization progression from prompts to context engineering (ACE, Meta Context Engineering) to workflow search (ADAS, AFlow) to self-editing harness code (STOP, Self-Harness, Agentic Harness Engineering, Darwin GΓΆdel Machine, Hyperagents) and evolutionary program search (AlphaEvolve, ShinkaEvolve). It closes with open problems for auto-research and self-improving agents: weak evaluators, memory/context lifecycle, negative-result bias, diversity collapse, reward hacking, and the durable need for human oversight, plus a benchmark appendix (PaperBench, CORE-Bench, RE-Bench, MLE-bench, KernelBench). Note: the fetched text is truncated partway through the references/appendix.

    lilianweng.github.ioarticleAdded 29 Sep 2026, published 4 Jul 2026🧠 AI

  125. The Hacker's 2026 Playbook: Dark Web Tactics Targeting You

    Huntress details ConsentFix, an evolution of ClickFix that abuses Microsoft 365 OAuth sign-in flows: victims are phished via password-protected Dropbox or DocSend lures, shown a fake Microsoft sign-in page, and tricked into dragging a localhost callback link into their browser, which exfiltrates OAuth tokens and hijacks the session without needing a password or triggering MFA. A cybercrime forum post published the full technique with working code and infrastructure such as Cloudflare Pages, workers.dev, and Pipedream webhooks, and showed attackers using LinkedIn, ZoomInfo, and Hunter.io to profile victims before sending lures.

    huntress.comarticleAdded 3 Sep 2026, published 29 Jun 2026πŸ›‘οΈ Security

  126. FOSSA: Allan Friedman

    Allan Friedman, former NTIA/CISA SBOM and VEX program lead, lays out practical VEX workflows for both software producers and consumers: tracking exposure via SBOM plus CVE/OSV feeds, doing reachability-based impact analysis, documenting and publishing determinations, and closing the loop as status changes. He compares the four VEX formats (CSAF, CycloneDX, SPDX 3.0, OpenVEX), ranks the five standard "not affected" justifications by how verifiable/trustworthy they are, and ties adoption to emerging regulatory pressure from the EU Cyber Resilience Act and FDA medical-device SBOM review.

    fossa.comarticlePublished and added 27 Jun 2026πŸ›‘οΈ Security

  127. How to Spot a Client in the DoD Industrial Base That Handles CUI

    A Huntress blog post (authored by DEFCERT's Ryan Bonner) gives MSPs and MSSPs a concrete methodology for spotting clients that are secretly part of the DoD Industrial Base and subject to DFARS 252.204-7012/-7021, CMMC, and NIST 800-171 obligations. It covers public research signals (USASpending.gov contract lookups, ITAR/DDTC registration, AS9100 certification, Nadcap accreditation, contract vehicles like IDIQ/GWAC/BPA/OTA) and direct screening questions (FAR/DFARS flow-down clauses, DoD distribution-statement-marked technical data, PIEE/SPRS/WAWF account access) to determine whether a company handles Controlled Unclassified Information. It closes with a pitch for Huntress's CMMC Level 2 control coverage.

    huntress.comarticleAdded 3 Sep 2026, published 25 Jun 2026πŸ›‘οΈ Security

  128. We Need to Talk About Device Code Phishing

    Huntress recaps a Tradecraft Tuesday episode explaining device code phishing, where attackers generate legitimate Microsoft OAuth device authorization codes and phish victims into entering them, instantly receiving valid session tokens that bypass MFA. It covers the technique's origin (Dr. Nestori Syynimaa/AADInternals, 2020), Storm-2372's February 2025 Teams-lure campaign, and a March 2026 EvilTokens PhaaS campaign that abused Railway.com as a clean-IP token-harvesting relay against 344 organizations, plus mitigations like Microsoft's Conditional Access block, device registration monitoring, and disabling device code flow.

    huntress.comarticleAdded 3 Sep 2026, published 22 Jun 2026πŸ›‘οΈ Security

  129. Socket: actions/checkout v7 Blocks Unsafe pull_request_target Checkouts

    GitHub released actions/checkout v7, which by default blocks checkouts of untrusted fork pull request code (via refs/pull/*/merge, fork head SHA, or fork repository) when running under pull_request_target or workflow_run-from-pull-request events, closing a long-known "pwn request" vector that grants attacker-controlled code access to base-repo secrets and GITHUB_TOKEN. The protection auto-applies to workflows pinned to floating major tags and backports to all supported versions on July 16, 2026; an allow-unsafe-pr-checkout opt-out flag is provided for workflows that intentionally need the old behavior. The article ties the change to real incidents (Nx supply chain attack, Shai-Hulud second wave via PostHog, and the TanStack compromise combining pwn request with cache poisoning and OIDC token extraction) and notes the fix only covers actions/checkout itself, not git/gh CLI or other checkout mechanisms.

    socket.devarticlePublished and added 22 Jun 2026πŸ›‘οΈ Security

  130. Malicious JetBrains Marketplace plugins steal AI API keys from developers

    Aikido Security uncovered at least 15 JetBrains Marketplace plugins, published under seven vendor accounts since October 2025, that pose as AI coding assistants (DeepSeek, OpenAI, SiliconFlow-branded) but exfiltrate any AI provider API key a user enters into the plugin settings to a hardcoded server (39.107.60[.]51) over plain HTTP. The plugins also run a "paid tier" that hands back API keys the operators appear to be harvesting from other free-tier victims. BleepingComputer confirmed the DeepSeek AI Assist plugin still contains the theft code and remains downloadable; combined installs across the campaign approach 70,000.

    bleepingcomputer.comarticleAdded 26 Sep 2026, published 16 Jun 2026πŸ›‘οΈ Security

  131. The Digital Context Gap

    First post in a series on building agentic infrastructure. It separates traditional machine learning (gradient-boosted trees, fraud detection) from black-box neural networks like LLMs. It argues LLMs add value in two cases: non-deterministic workflows that can't be hand-programmed, and as a "digitally native" interface that narrows the "digital context gap" between human and machine speed at handling context. It also challenges its own thesis, noting that models lack real comprehension and that even a 1% error rate is costly at volume. It closes with practical principles: start from the problem, design for failure, add validation layers and human-in-the-loop checkpoints, and treat LLMs as enhancement rather than replacement.

    jakewnuk.comarticleAdded 22 Sep 2026, published 10 Jun 2026🧠 AI

  132. What is AI SAST?

    Aikido's explainer draws a line between two things vendors both call "AI SAST": AI-native (reasoning-based) SAST, where an LLM reads source code like a reviewer to trace data flow and catch logic flaws such as IDORs, broken access control and business-logic bypasses that have no syntactic signature; and AI-augmented SAST, where a traditional deterministic rule engine stays the detection core and AI is layered on for triage, false-positive filtering and autofix. It also positions AI SAST against classic pattern-matching SAST (fast, deterministic, runs every commit) and AI pentesting (validates real exploits against a running app, produces proof for audits), arguing organizations need all three at different cadences. The piece closes by mapping Aikido's own Code Security Audit and Deep PR Review products onto the AI-native category.

    aikido.devarticleAdded 3 Sep 2026, published 6 Jun 2026πŸ›‘οΈ Security

  133. Orca Security: Red Hat npm Packages Compromised in Supply-Chain Attack Spreading Credential-Stealing Worm

    Orca describes the June 1, 2026 compromise of 32 npm packages under the @redhat-cloud-services scope, which came from a hijacked Red Hat employee GitHub account. The attacker injected malicious GitHub Actions workflows into three RedHatInsights repos and used OIDC tokens to publish backdoored versions with valid SLSA provenance. A preinstall hook runs a 4.2 MB obfuscated payload that sweeps CI, cloud, SSH, registry and .env credentials and self-propagates (the "Miasma" worm, attributed to TeamPCP or a copycat using Mini Shai-Hulud tooling). The post lists compromised versions and gives rotation and pinning guidance.

    orca.securityarticlePublished and added 2 Jun 2026πŸ›‘οΈ Security

  134. Bringing full YAML anchor support to zizmor

    Trail of Bits worked with the zizmor maintainers to add full YAML anchor support to zizmor, the GitHub Actions static analyzer that catches misconfigurations like the one exploited in the March 2026 aquasecurity/trivy-action pull_request_target attack that led to a LiteLLM PyPI backdoor. They built a corpus of 41,253 workflows from 6,612 high-star repos, found zizmor crashed on 45 of them, and fixed four anchor-handling bugs plus unrelated deserialization and expression-evaluator issues, filing 20 issues and merging 15 PRs upstream.

    blog.trailofbits.comarticleAdded 5 Sep 2026, published 22 May 2026πŸ›‘οΈ Security

  135. Socket: TeamPCP + BreachForums Launch $1,000 Contest for Supply Chain Attacks

    Socket reports that TeamPCP and the owner of BreachForums are running a $1,000-Monero contest rewarding whoever compromises the highest-download open-source package using the Shai-Hulud worm, with smaller compromises also counting toward the score. TeamPCP has also released Shai-Hulud as open-source attack tooling on the Breached CDN (briefly mirrored on GitHub) and has been systematically targeting security tools, CI/CD workflows, GitHub Actions, Docker images, OpenVSX extensions, npm, PyPI, and Packagist to harvest CI/CD secrets, cloud credentials, and maintainer tokens. The piece ties the contest to TeamPCP's broader access-broker role, noting overlapping downstream extortion claims involving Vect, ShinyHunters, and Lapsus$.

    socket.devarticlePublished and added 20 May 2026πŸ›‘οΈ Security

  136. CMMC Final Rule: A Guide for DoD Subcontractors

    Huntress breaks down the DoD's CMMC final rule, effective November 10, 2025, which replaces contractor self-attestation with mandatory third-party (C3PAO) verification for handling Federal Contract Information (FCI) and Controlled Unclassified Information (CUI). It explains the three certification levels (Level 1 self-assessment against FAR 52.204-21, Level 2 aligned to NIST SP 800-171's 110 controls, Level 3 adding NIST SP 800-172 controls), the flow-down requirement forcing subcontractors to certify before prime contractors will award work, and the scoring/documentation burden (SSP, policies, procedures) needed to pass a Level 2 assessment.

    huntress.comarticleAdded 3 Sep 2026, published 14 May 2026πŸ›‘οΈ Security

  137. Agentic Workflows

    A personal blog post walks through building a GitHub Agentic Workflows automation (a GitHub Next research demonstrator) that autonomously checks for new Astro releases, researches breaking changes, applies upgrades, and opens a PR β€” with no human involvement until review. The piece details the tool's security model in depth: agents get read-only repo permissions by default, all writes must go through pre-declared 'safe-outputs' (e.g. create-pull-request with a compile-time allowed-files list), external network access is restricted via an allowlist enforced by an 'Agent Workflow Firewall', and PRs are never auto-merged so a human always reviews the change.

    laurentkempe.comarticleAdded 3 Sep 2026, published 13 May 2026πŸ›‘οΈ Security

  138. Security Architecture of GitHub Agentic Workflows

    GitHub engineering post detailing the security architecture behind GitHub Agentic Workflows, which run LLM agents (Claude, Codex, Copilot) as GitHub Actions. It describes a layered defense model (substrate/configuration/planning layers), a zero-secrets-to-agent design using container isolation, chroot jails, a trusted MCP gateway, and an API proxy for LLM auth tokens, plus a "safe outputs" subsystem that stages and vets all agent writes (issues, PRs, comments) and pervasive logging at every trust boundary for forensic visibility.

    github.blogarticleAdded 3 Sep 2026, published 13 May 2026πŸ›‘οΈ Security

  139. CSA: VulnOps in the Age of AI

    Cloud Security Alliance research note arguing that traditional vulnerability management (scan, ticket, patch on a calendar) is breaking under AI-driven vulnerability discovery volume, NVD's April 15, 2026 risk-based triage policy that limits full CVE enrichment to CISA KEV/EO 14028/federal-use software, and compressed disclosure-to-exploitation windows. It defines VulnOps as a flow-oriented operating discipline (borrowing SRE/DevOps metrics like lead time, change-failure rate, and pipeline saturation) built on continuous discovery, EPSS/KEV-based risk prioritization instead of CVSS-only ranking, automated remediation-as-code, and first-class SBOM/supply-chain visibility, while also flagging agentic AI itself (prompt injection, tool-poisoning, MCP command execution) as a new vulnerability class the practice must cover.

    labs.cloudsecurityalliance.orgarticleAdded 3 Sep 2026, published 13 May 2026πŸ›‘οΈ Security

  140. GitHub Secret Scanning MCP Server

    GitHub announced general availability of secret scanning as a tool inside the GitHub MCP server, letting MCP-compatible AI coding agents such as GitHub Copilot CLI and VS Code scan uncommitted changes for exposed credentials before a commit or PR is opened. The GA release adds enforcement of existing push-protection customizations so detection and bypass behavior configured at the repo or org level stays consistent when triggered through an agent instead of a normal git push. Requires GitHub Secret Protection enabled on the repo; an optional Advanced Security plugin adds a tailored secret-scanning workflow in Copilot Chat.

    github.blogarticleAdded 3 Sep 2026, published 11 May 2026πŸ›‘οΈ Security

  141. The complete GitHub Actions security checklist

    A detailed 33-point checklist for hardening GitHub Actions workflows, covering trigger risks (pull_request_target, workflow_run), script/prompt injection into run: steps and AI agent prompts, mutable action/package references, artifact handling, secrets scoping, OIDC over static cloud credentials, runner isolation, and token/org-level permission defaults. Each section is backed by real-world incidents (Trivy tag hijack, tj-actions/changed-files compromise, Ultralytics PyPI attack, Nx/s1ngularity, Shai-Hulud, TanStack npm trusted-publisher abuse, PyTorch self-hosted runner takeover), making it a practical reference for securing CI/CD pipelines against the supply-chain attacks that have hit open source in 2025–2026.

    aikido.devarticleAdded 3 Sep 2026, published 11 May 2026πŸ›‘οΈ Security

  142. XBOW: What Is IDOR, and How Do You Test for It?

    XBOW's Offensive Security Academy post explains Insecure Direct Object Reference (IDOR) vulnerabilities including read, write, file, API, and multi-step-workflow variants, and why they resist traditional scanners since they require reasoning about object-level authorization rather than pattern matching. It walks through prevention guidance such as server-side authorization checks and avoiding client-supplied identifiers, then details a case study where XBOW's autonomous AI pentesting platform found two previously unknown IDORs in Spree Commerce: an unauthenticated address-edit bypass via cookie manipulation, and a multi-cart cross-reference flaw exposing another customer's address, both fixed in Spree v5.2.5.

    xbow.comarticlePublished and added 9 May 2026πŸ›‘οΈ Security

  143. Securing Jenkins: Top Attack Flows & Misconfigurations | Wiz Blog

    Wiz Research breaks down Jenkins' attack surface using cloud environment telemetry: 59% of Jenkins-using environments have critical core vulnerabilities, 87% run end-of-life instances, and plugins like workflow-cps-global-lib (deprecated, 31% adoption) and extended-choice-parameter (unpatched CVEs, 14% adoption) remain widely deployed despite Jenkins' otherwise mature plugin-governance model. The post maps five recurring attack chains observed in the wild - from exposed script consoles used for cryptojacking, through CI/CD pipeline secret extraction, plugin/core exploitation for controller takeover, agent compromise for lateral movement, to IMDS-based cloud credential theft used by actors like Genesis Panda and IntelBroker to pivot into cloud control planes.

    wiz.ioarticleAdded 5 Sep 2026, published 6 May 2026πŸ›‘οΈ Security

  144. Mini Shai-Hulud Worm (Apr–May 2026)

    Socket's Threat Research team confirms intercom-client@7.0.4, the official Intercom Node.js SDK (~360k weekly downloads), was compromised via a preinstall hook (setup.mjs) that downloads an unverified Bun binary and executes an 11.7MB obfuscated payload (router_runtime.js) which harvests Kubernetes and Vault credentials and exfiltrates them via the GitHub API. The compromise traces to a hijacked maintainer GitHub account (nhur) that pushed spoofed Dependabot-style workflow changes to trigger the npm publish CI pipeline, and the payload closely matches the 'Mini Shai-Hulud' campaign also seen in a PyPI package (lightning) and prior SAP CAP/Cloud MTA npm packages linked to TeamPCP activity.

    socket.devarticlePublished and added 6 May 2026πŸ›‘οΈ Security

  145. CI/CD Threat Modelling

    A practical threat-modelling framework for CI/CD pipelines built from two years of hardening CI/CD configurations. It walks through pipeline-level questions (who can trigger workflows, who can modify workflow definitions) and per-step questions (inputs, branch protection bypass, exposed secrets/OIDC credentials, arbitrary code execution via workflow steps, third-party dependency trust), and gives concrete GitHub Actions examples such as PR-title injection turning into arbitrary code execution and using workflow-exposed VCS credentials to self-approve a PR.

    airman604.substack.comarticlePublished and added 6 May 2026πŸ›‘οΈ Security

  146. PyPI Access Control Vulns Patched

    Socket.dev covers Trail of Bits' second external security audit of PyPI's Warehouse application, funded by the Sovereign Tech Agency, which found 14 issues including two high-severity access control flaws. One allowed any organization Member to POST an Owner-role invitation because the manage_organization_roles view gated both GET and POST behind read-only OrganizationsRead permission; the other let stale TeamProjectRole records grant upload/admin access after a project was transferred between organizations. The piece also details a Medium-severity OIDC Trusted Publishing replay window (Redis jti key expiring before PyJWT's 30s leeway), a related TOCTOU race in the same anti-replay flow, an IDOR in API token deletion, and an unfixed gap where wheel-embedded METADATA dependencies aren't validated against form-submitted metadata, letting installers see different dependency data than PyPI's JSON API/pip-audit.

    socket.devarticlePublished and added 6 May 2026πŸ›‘οΈ Security

  147. CodeMender (Google DeepMind)

    Google DeepMind's official announcement of CodeMender, an AI agent built on Gemini Deep Think that autonomously debugs, roots-causes, and patches security vulnerabilities in real codebases, then validates fixes via static and dynamic analysis, differential testing, fuzzing, SMT solvers, and an LLM-based critique agent before human review. The team has upstreamed 72 security fixes to open-source projects, including some spanning 4.5 million lines of code, and used CodeMender to proactively apply bounds-safety annotations to libwebp, which would have neutralized the buffer-overflow class of bug behind CVE-2023-4863, a bug used in a zero-click iOS exploit.

    deepmind.googlearticlePublished and added 6 May 2026πŸ›‘οΈ Security

  148. Palantir

    Palantir's InfoSec team describes how they manage VS Code extensions at scale: an osquery-based fleet inventory, an internal static-analysis tool (network/shell calls, secrets, obfuscation, npm audit), and an allowlist in a GitHub repo enforced through VS Code's `extensions.allowed` enterprise setting. Changes flow through pull-request review, CircleCI publishes to Artifactory, and Excavator generates Jamf and Group Policy configs. It also covers disabling extension telemetry and a pre-enforcement impact-assessment script, with lessons on developer buy-in.

    blog.palantir.comarticlePublished and added 5 May 2026πŸ›‘οΈ Security

  149. Attackers Didn’t Wait for AI. They Built Workflows Around It.

    Huntress details three real-world patterns where attackers build workflows around AI adoption rather than attacking AI models themselves: SEO-poisoned/malvertised fake "Claude Code" downloads that deliver credential-stealing malware, an AMOS stealer campaign that spoofs ChatGPT/Grok-style answer pages to trick macOS users into running malicious Terminal commands (ClickFix-style), and the EvilTokens phishing-as-a-service platform, which used Railway infrastructure for on-demand session-token theft and AI-generated, role-tailored phishing lures that bypass email filtering. The piece argues AI isn't the weapon but the accelerant, making malicious activity blend into trusted, expected workflows.

    huntress.comarticleAdded 3 Sep 2026, published 22 Apr 2026πŸ›‘οΈ Security

  150. GitHub Actions Security Pt 1: Attacks & Defenses | Wiz Blog

    Part one of a Wiz Research series building a threat model for GitHub Actions, covering three core risk classes: dangerous triggers like pull_request_target enabling "Pwn Request" attacks, script/expression injection via unsanitized workflow inputs, and compromised third-party actions in the supply chain. It walks through real incidents including the Trivy supply-chain compromise via a pull_request_target misconfiguration, the Ultralytics PyPI cryptominer injection via branch-name script injection, and the tj-actions/changed-files compromise that hit 22,000 repos targeting Coinbase, with corresponding defenses such as avoiding pull_request_target, binding/sanitizing inputs, and pinning actions to commit SHAs.

    wiz.ioarticleAdded 5 Sep 2026, published 14 Apr 2026πŸ›‘οΈ Security

Showing 150 of 151

Show more