Smart search ranks by meaning as well as keywords (one row per story, last 45 days).
Dark Reading scheduled a virtual event on building enterprise AI security strategies; no article details were available.
Dark Reading is promoting a virtual event titled 'Building a Secure AI Strategy for the Enterprise.' No article text was available, so details such as date, speakers, and agenda are unknown.
oss-security moderator Solar Designer approved three AI-generated vulnerability reports from automated security researcher Eve, sparking debate over AI slop on the list.
oss-security moderator Solar Designer approved three posts submitted by Eve, described as an 'automated security researcher', noting they lacked Date headers and arrived on the list server on September 9. He expressed uncertainty about their value but suggested they may have historical significance as early examples of AI-generated security reports at the dawn of AI security research. The post is meta-commentary on AI-generated content reaching a vulnerability disclosure mailing list rather than a specific vulnerability disclosure itself.
Unit 42 warns attackers increasingly target CI/CD pipelines and developer tools rather than application code, urging full SDLC supply chain visibility.
Palo Alto Networks Unit 42 research argues attackers are shifting focus from application code to overlooked corners of the software development lifecycle supply chain, including CI/CD pipelines and developer tooling. The write-up calls for total SDLC visibility and strict security controls to defend these developer-facing attack surfaces.
New Relic study finds AI-generated code doubles critical runtime issues, with senior engineers losing a third of their week to fixes.
A New Relic survey of U.S. technology leaders reports AI now writes the majority of shipped code, with senior SRE and DevOps engineers spending up to a third of their week triaging and refactoring it. A large majority of organizations had at least one AI-related production failure in the past six months, and roughly three in ten saw newly introduced security vulnerabilities. AI-generated code showed nearly twice as many critical runtime issues as peer-reviewed human-authored code, with gaps concentrated in edge cases, concurrency, deprecated APIs, and complex state changes. Most teams now prompt AI tools to embed logs and traces directly into generated code.
BleepingComputer and Material Security will host a September 23, 2026 webinar on breaches caused by forgotten third-party Google Workspace integrations.
BleepingComputer announced a live webinar on September 23, 2026, titled 'Breach autopsy: How fast-growing companies are breached through Google Workspace' in partnership with Material Security. Speakers include Rajan Kapoor, VP of Security at Material Security, and Rick Fitzgerald, President of Fireside Consulting LLC. The session will examine real documented Google Workspace breaches involving overly permissive third-party integrations, social engineering entry paths, first-hours breach response decisions, and high-value security controls for lean security teams.
Wiz highlights personal developer repositories as a supply chain blind spot leaking corporate secrets, offering correlation-based risk validation and remediation.
Wiz argues that developers' personal code repositories are a blind spot in software supply chain security where corporate secrets quietly escape. The company describes an approach that correlates personal repositories to specific developers, validates the actual risk, and drives remediation. No specific incident or vulnerability is disclosed in the announcement.
Checkmarx argues Solidity developers need pre-deployment AppSec because disclosure-to-weaponization time has collapsed from 840 days to 1.6 days.
A Checkmarx write-up contrasts traditional software patch cycles with blockchain development, where there is no Patch Tuesday and fixes require on-chain upgrades. It cites stats that median disclosure-to-weaponization time collapsed from 840 days to 1.6 days and that 80% of exploitations now occur on or before disclosure day. The piece advocates fusion-grade application security for Solidity teams before contracts deploy.
Laurie Voss argues AI collapses code-writing and review costs, leaving product discovery and precise definition as the core of software engineering.
Simon Willison quotes Laurie Voss's essay "We are all Product Engineers now," which argues that AI is collapsing the cost of writing code and will likewise collapse the cost of reviewing, fixing, and operating it. Voss contends the remaining work is finding out what people want, defining it precisely, and making software pleasant to use. He expects the amount of software to grow without limit because demand has no ceiling, making product-definition skills the whole job. No specific models, tools, or incidents are named; this is career and industry commentary.
Opinion essay satirizing AI developers who advocate slowing AI development while continuing their own work; 101 points on Hacker News.
Xe Ito's essay titled 'Everyone should slow down AI development except for me' comments on AI development pacing and slowdown debates. The piece drew 101 points and 14 comments on Hacker News. No technical security or policy details are provided in the source metadata.
A FOSS maintainer manually graded 102 F-Droid apps from the September 12, 2026 update batch, finding many show signs of LLM-generated code.
A student and FOSS app maintainer reviewed 102 apps pushed to F-Droid on September 12, 2026, assigning each a three-tier rating for likelihood of LLM-authored code (mostly AI >50%, hard to say/mostly human, no signs of AI). The heuristic relies on commit aesthetics, README and branding style, and the presence of agentic infrastructure like Claude Code or Codex, which automatically places an app in the 'mostly AI' tier. Example ratings include Amber (Nostr event signer) as mostly AI, and Aria for Misskey as showing no AI signs. The author stresses reliable detection of LLM-generated code from text alone is impossible, so ratings are approximate.
91% of 115 surveyed TEE deployments across Intel SGX, TDX, and AMD SEV fail to provide reproducible builds needed for verifiable remote attestation.
A systematic study of 115 TEE deployments found 91% were not reproducible and 80% lacked both source code and a reference build, undermining remote attestation guarantees. Interviews with 12 developers of 50 Intel SGX projects confirmed that only one participant treats reproducibility as a development priority. The authors identify technical barriers such as embedded timestamps plus ecosystem-level issues like lack of build-environment control in multi-stakeholder projects, and call for holistic, committed reproducibility practices.
Opinion piece argues AI-driven shifts that transformed software development—agent-run SOCs, autonomous triage—will soon reshape cybersecurity operations and staffing.
A CSO Online analysis notes Google Cloud research found 90% of developers already use AI, while a March 2026 Federal Reserve paper found coder employment growth fell roughly 3% since ChatGPT's arrival. Gartner predicts 80% of organizations will run smaller, AI-augmented engineering teams by 2030. Security leaders from Contrast Security, Menlo Security and the Cloud Security Alliance expect agent-run SOCs, machine-speed containment and abundant vulnerability discovery, but caution that absorption capacity and autonomous production-environment validation remain bottlenecks.
New τ^τ-bench tasks coding agents with building deployable customer-service agents; best config, Claude Opus 5, passes only 23.9% of simulations.
Researchers introduce τ^τ-bench, an end-to-end benchmark where a developer agent must build a complete customer-service agent from real business records, a client with requirements, a production API, an inherited codebase, and cost/model limits, then is scored by deploying it against held-out simulated users. Across 53 tasks in four domains, the strongest configuration, Claude Opus 5 under Claude Code, passes just 23.9% of evaluation simulations versus an 82.2% expert-authored reference ceiling. Failure modes mirror those of human developers: shallow queries instead of deep record comprehension, almost no client communication, and shipping the first architecture that runs rather than experimenting.
BleepingComputer and Material Security will host a September 23 webinar analyzing first-hours response decisions in real Google Workspace breaches.
The September 23, 2026 webinar 'Breach autopsy' features Material Security VP of Security Rajan Kapoor and Fireside Consulting president Rick Fitzgerald examining publicly documented Google Workspace breaches. Two analyzed attacks combined social engineering with malicious OAuth applications to gain access. Sessions will cover scoping exposed users and data, confirming whether attacker access persists, and which early containment decisions limited or worsened impact for lean security teams.
Hacker News users debate coding without LLMs, with one developer fired for refusing AI tools and others describing daily hand-coding practice to counter skill atrophy.
An Ask HN thread collects experiences of developers who still write code without LLM assistance. One contributor says he was fired for political reasons after refusing to use LLMs despite adequate stated performance, and observes fewer job ads now require LLM use. Others describe starting each day with a LeetCode problem or 30-60 minutes of hand-coding to stay sharp, contractual bans on AI-generated code for a government-adjacent embedded product over unresolved copyright issues, and inconsistent corporate policies where ChatGPT or Codex use flip-flops between allowed and blocked while a CIO mandates 70-80% AI-generated code next year.
Zentera Systems CEO says AI supply chain attacks currently hit developer workflows first, advising segmentation over tooling and citing the Phantom Raven campaign.
In an interview, Zentera Systems CEO Dr. Jaushin Lee argues that most active AI supply chain incidents target developer workflows and open-source package repositories, while poisoned model weights, compromised MCP servers, and poisoned vector stores remain largely in research and demos. He cites the active 'Phantom Raven' campaign, where attackers register AI-hallucinated package names in public repositories with malicious payloads that silently infect vibe-coding build pipelines. He recommends software-defined segmentation, semiconductor-style project enclaves with egress controls, and warns that self-hosting models without agent sandboxing leaves exposure unchanged.
BleepingComputer webinar will dissect two Google Workspace breaches caused by malicious OAuth apps and social engineering, hosted September 23 with Material Security.
On September 23, 2026, BleepingComputer will host a webinar with Material Security examining two real attacks that used malicious OAuth applications and social engineering to breach Google Workspace environments. Rather than stealing credentials, attackers persuaded users to authorize malicious apps, gaining access to data through the granted permissions. The session covers first-hour response decisions and which security controls provide the greatest value for fast-growing organizations.
Dark Reading argues AI-assisted bug discovery is flooding vendors with vulnerability reports, straining disclosure processes and secure-by-design commitments.
The Dark Reading analysis describes a surge of bug reports driven by AI-powered discovery, exposing bottlenecks in vendor triage and disclosure pipelines. It argues this volume is revealing secure-by-design failures and questions whether vendors can keep pace with the rising tide of findings.
Wiz argues shift-left code-stage security cuts remediation costs and ships Wiz Code, WizOS, and WizCLI to catch flaws pre-deployment.
A Wiz blog post argues that fixing vulnerabilities at the code stage costs a fraction of production remediation, citing the node:20-slim base image which ships 14 known CVEs, three of them critical. It claims AI agents can now analyze open-source commits and generate working exploits in minutes, shrinking the window between a public fix and automated attacks. The post promotes WizOS near-zero-CVE base images, WizCLI and MCP-server checks inside developer and AI agent sessions, and Wiz Code scanning across pull requests, repositories, and pipelines covering SAST, SCA, secrets, and IaC misconfigurations.
Debian developers voted to encourage voluntary disclosure of AI assistance in contributions rather than banning or mandating labeling of LLM-generated code.
Debian's vote concluded August 28, with project secretary Kurt Roeckx announcing that the winning option encourages contributors to disclose generative AI assistance and stops there, adding no new mandatory review gates. The adopted resolution bars sending confidential material, embargoed security bugs, cryptographic keys and credentials to third-party AI services without explicit authorization, requires prior discussion for bulk automated work, and takes no position on whether model output is copyrightable. The project neither endorses nor prohibits generative AI and retains existing human review and licensing requirements.
SpecterOps released CDP-Enable-BOF, a Beacon Object File that enables Chrome DevTools Protocol in live Chrome or Edge processes on Windows for session hijacking.
SpecterOps released CDP-Enable-BOF, an x64 Beacon Object File that activates Chrome DevTools Protocol inside running chrome.exe or msedge.exe processes on Windows, exposing cookies, history, saved passwords, and authenticated sessions without administrator rights. It calls Chromium's StartRemoteDebuggingServer on the browser UI thread to stay reliable under CFG, TLS, and CET, and was tested on Chrome 147 and Edge 147. The technique builds on work by DeathFlamingo and Cedric Van Bockhaven; Google had hardened remote debugging in Chrome 136 after attackers used it to steal cookies post-App-Bound Encryption. Defenders can watch Sysmon Event IDs 8 and 10 for injection into browser processes.
IdeaAMBIG benchmark with 660 instances measures whether LLMs can spot and fix underspecified research-method details for faithful implementation.
Researchers introduce IdeaAMBIG, a benchmark of 660 evidence-grounded instances (163 real-world gaps from reproducibility reports and GitHub issues, 497 controlled synthetic gaps) built from papers, codebases, and reproduction artifacts. It evaluates codification-readiness assessment, defect localization, and clarification action generation. Across 13 LLMs, the best model achieved only 9.6% Macro Defect Recovery Rate on real-world instances but 80.6% clarification success when given the annotated defect. An oracle study showed gold resolutions raise the codification-ready rate from 14% to 98%, identifying defect localization as the main bottleneck.
Authors of the gpg.fail GnuPG vulnerability set published a retrospective with talk recording, slides, and a repo PoC.
Sam James shares that the researchers behind the 'gpg.fail' set of GnuPG vulnerabilities have published a retrospective, including a talk recording and slides. The slides appear to mention an additional vulnerability not yet widely reviewed, and a proof-of-concept is available in their repository. This follows earlier discussion of the gpg.fail findings on oss-security.