<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ - Development</title>
    <link>https://www.infoq.com</link>
    <description>InfoQ Development feed</description>
    <item>
      <title>How OpenAI Built a Secure Windows Sandbox for Codex Agents</title>
      <link>https://www.infoq.com/news/2026/06/codex-windows-sandbox-design/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Development</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/06/codex-windows-sandbox-design/en/headerimage/generatedHeaderImage-1780184710031.jpg"/&gt;&lt;p&gt;OpenAI details Codex Windows sandbox architecture, showing how SIDs, ACLs, restricted tokens, and dedicated sandbox accounts enable safe execution of autonomous coding tasks. The design balances isolation with real developer workflows and shows how OS security primitives must be composed for AI agents on local development environments.&lt;/p&gt; &lt;i&gt;By Leela Kumili&lt;/i&gt;</description>
      <category>Identity Management</category>
      <category>IDE</category>
      <category>Access Control</category>
      <category>Security</category>
      <category>AI Assisted Coding</category>
      <category>Integrated Development Environment</category>
      <category>CLI</category>
      <category>Operating Systems</category>
      <category>Design Systems</category>
      <category>Windows</category>
      <category>Agents</category>
      <category>DevOps</category>
      <category>Development</category>
      <category>Architecture &amp; Design</category>
      <category>news</category>
      <pubDate>Fri, 05 Jun 2026 14:37:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/06/codex-windows-sandbox-design/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Development</guid>
      <dc:creator>Leela Kumili</dc:creator>
      <dc:date>2026-06-05T14:37:00Z</dc:date>
      <dc:identifier>/news/2026/06/codex-windows-sandbox-design/en</dc:identifier>
    </item>
    <item>
      <title>Dropbox Introduces Nova, an Internal Platform for Running AI Coding Agents at Scale</title>
      <link>https://www.infoq.com/news/2026/06/dropbox-nova-ai-coding-agents/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Development</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/06/dropbox-nova-ai-coding-agents/en/headerimage/generatedHeaderImage-1779952906697.jpg"/&gt;&lt;p&gt;Dropbox has unveiled Nova, an internal platform designed to orchestrate and operationalize AI coding agents across the company's engineering workflows.&lt;/p&gt; &lt;i&gt;By Craig Risi&lt;/i&gt;</description>
      <category>AI Assisted Coding</category>
      <category>Artificial Intelligence</category>
      <category>AI Coding</category>
      <category>DevOps</category>
      <category>AI, ML &amp; Data Engineering</category>
      <category>Development</category>
      <category>news</category>
      <pubDate>Fri, 05 Jun 2026 12:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/06/dropbox-nova-ai-coding-agents/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Development</guid>
      <dc:creator>Craig Risi</dc:creator>
      <dc:date>2026-06-05T12:00:00Z</dc:date>
      <dc:identifier>/news/2026/06/dropbox-nova-ai-coding-agents/en</dc:identifier>
    </item>
    <item>
      <title>Google LiteRT-LM Speeds Up Local Inference Up to 2.2x With Gemma 4 Multi-Token Prediction</title>
      <link>https://www.infoq.com/news/2026/06/google-litertlm-gemma4/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Development</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/06/google-litertlm-gemma4/en/headerimage/google-litert-ml-gemma4-1780649451174.jpeg"/&gt;&lt;p&gt;LiteRT-LM brings native support for Gemma 4 Multi-Token Prediction (MTP) drafters, enabling up to 2.2x faster inference. The framework is expanding beyond Kotlin and C++ adding support for new Swift and a JavaScript APIs.&lt;/p&gt; &lt;i&gt;By Sergio De Simone&lt;/i&gt;</description>
      <category>Edge Computing</category>
      <category>Gemma</category>
      <category>TensorFlow</category>
      <category>Google</category>
      <category>Large language models</category>
      <category>Mobile</category>
      <category>Agents</category>
      <category>AI, ML &amp; Data Engineering</category>
      <category>Development</category>
      <category>news</category>
      <pubDate>Fri, 05 Jun 2026 09:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/06/google-litertlm-gemma4/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Development</guid>
      <dc:creator>Sergio De Simone</dc:creator>
      <dc:date>2026-06-05T09:00:00Z</dc:date>
      <dc:identifier>/news/2026/06/google-litertlm-gemma4/en</dc:identifier>
    </item>
    <item>
      <title>TypeORM Reaches 1.0 After Nearly a Decade, Signalling Renewed Maintenance</title>
      <link>https://www.infoq.com/news/2026/06/typeorm-1-released/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Development</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/06/typeorm-1-released/en/headerimage/generatedHeaderImage-1780570519122.jpg"/&gt;&lt;p&gt;TypeORM 1.0 is the first major release of the open-source TypeScript and JavaScript ORM since its inception in 2016. This version modernizes platform requirements, removes deprecated APIs, and introduces numerous bug fixes and new features. TypeORM now supports ECMAScript 2023, dropping older Node.js versions and dependencies while enhancing security and migration processes.&lt;/p&gt; &lt;i&gt;By Daniel Curtis&lt;/i&gt;</description>
      <category>JavaScript</category>
      <category>Web Development</category>
      <category>Database</category>
      <category>ORM</category>
      <category>TypeScript</category>
      <category>Development</category>
      <category>news</category>
      <pubDate>Fri, 05 Jun 2026 06:52:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/06/typeorm-1-released/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Development</guid>
      <dc:creator>Daniel Curtis</dc:creator>
      <dc:date>2026-06-05T06:52:00Z</dc:date>
      <dc:identifier>/news/2026/06/typeorm-1-released/en</dc:identifier>
    </item>
    <item>
      <title>30+ Updates per Second per Account: Uber Scales Ledger Processing with Batching</title>
      <link>https://www.infoq.com/news/2026/06/uber-payment-batching-system/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Development</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/06/uber-payment-batching-system/en/headerimage/generatedHeaderImage-1779570527807.jpg"/&gt;&lt;p&gt;Uber introduced a high-throughput financial ledger processing system designed to handle hot account write contention at scale. Using 250ms batching, Redis coordination, and optimistic atomic updates, the system supports 30+ updates per second per account while preserving consistency and auditability, reducing multi-hour processing pipelines to minutes in its distributed accounting infrastructure.&lt;/p&gt; &lt;i&gt;By Leela Kumili&lt;/i&gt;</description>
      <category>Distributed Systems</category>
      <category>HotSpot</category>
      <category>Event Driven Architecture</category>
      <category>Low Latency</category>
      <category>payment</category>
      <category>Transactions Processing</category>
      <category>Consistency</category>
      <category>Optimization</category>
      <category>Event Stream Processing</category>
      <category>Financial Applications</category>
      <category>Batch Processing</category>
      <category>Performance</category>
      <category>Development</category>
      <category>Architecture &amp; Design</category>
      <category>news</category>
      <pubDate>Thu, 04 Jun 2026 14:02:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/06/uber-payment-batching-system/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Development</guid>
      <dc:creator>Leela Kumili</dc:creator>
      <dc:date>2026-06-04T14:02:00Z</dc:date>
      <dc:identifier>/news/2026/06/uber-payment-batching-system/en</dc:identifier>
    </item>
    <item>
      <title>Article: Architectural Change Cases: A Practical Tool for Evolutionary Architectures</title>
      <link>https://www.infoq.com/articles/architectural-change-cases/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Development</link>
      <description>&lt;img src="https://res.infoq.com/articles/architectural-change-cases/en/headerimage/architectural-change-cases-header-1780316814045.jpg"/&gt;&lt;p&gt;Architectural change cases extend architecture decision record (ADR) thinking by evaluating how decisions may evolve over time. Change cases expose hidden assumptions and help teams estimate the reversibility and cost of change.&lt;/p&gt; &lt;i&gt;By Pierre Pureur, Kurt Bittner&lt;/i&gt;</description>
      <category>Transcripts</category>
      <category>Architecture Documentation</category>
      <category>Architecture Evaluation</category>
      <category>Architecture Decision Records</category>
      <category>Evolutionary Architecture</category>
      <category>Development</category>
      <category>Architecture &amp; Design</category>
      <category>article</category>
      <pubDate>Thu, 04 Jun 2026 09:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/articles/architectural-change-cases/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Development</guid>
      <dc:creator>Pierre Pureur, Kurt Bittner</dc:creator>
      <dc:date>2026-06-04T09:00:00Z</dc:date>
      <dc:identifier>/articles/architectural-change-cases/en</dc:identifier>
    </item>
    <item>
      <title>AWS Replaces Fat-Tree Data Center Networks with Random Graph Theory, Cutting Routers by 69%</title>
      <link>https://www.infoq.com/news/2026/06/aws-random-graph-data-center/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Development</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/06/aws-random-graph-data-center/en/headerimage/generatedHeaderImage-1780475849954.jpg"/&gt;&lt;p&gt;AWS disclosed that Resilient Network Graphs, a flat network architecture based on quasi-random graph theory, is now the default for most new data center builds. The design replaces fat-tree hierarchies with direct ToR-to-ToR mesh connections using passive optical ShuffleBoxes, cutting routers by 69%, boosting throughput by 33%, and reducing network power consumption by 40%.&lt;/p&gt; &lt;i&gt;By Steef-Jan Wiggers&lt;/i&gt;</description>
      <category>Amazon Web Services</category>
      <category>AWS</category>
      <category>Infrastructure</category>
      <category>Deployment / Datacenter</category>
      <category>Cloud</category>
      <category>DevOps</category>
      <category>Development</category>
      <category>Architecture &amp; Design</category>
      <category>news</category>
      <pubDate>Thu, 04 Jun 2026 08:25:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/06/aws-random-graph-data-center/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Development</guid>
      <dc:creator>Steef-Jan Wiggers</dc:creator>
      <dc:date>2026-06-04T08:25:00Z</dc:date>
      <dc:identifier>/news/2026/06/aws-random-graph-data-center/en</dc:identifier>
    </item>
    <item>
      <title>Next.js 16.2: 400% Faster Dev Startup, Faster Rendering, and Deeper Tooling for AI Agents</title>
      <link>https://www.infoq.com/news/2026/06/nextjs-6-2/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Development</link>
      <description>&lt;img src="https://www.infoq.com/styles/static/images/logo/logo_bigger.jpg"/&gt;&lt;p&gt;Vercel has released Next.js 16.2, featuring performance enhancements that make development startup 400% faster and rendering up to 60% quicker. The update includes AI-assisted development tools, improved Turbopack efficiency, and better error reporting. Migration from Next.js 15 is supported, and compatibility is set for Node.js 20.9 and TypeScript 5.1 or newer.&lt;/p&gt; &lt;i&gt;By Daniel Curtis&lt;/i&gt;</description>
      <category>Next.js</category>
      <category>React</category>
      <category>JavaScript</category>
      <category>Web Development</category>
      <category>TypeScript</category>
      <category>Development</category>
      <category>news</category>
      <pubDate>Thu, 04 Jun 2026 06:47:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/06/nextjs-6-2/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Development</guid>
      <dc:creator>Daniel Curtis</dc:creator>
      <dc:date>2026-06-04T06:47:00Z</dc:date>
      <dc:identifier>/news/2026/06/nextjs-6-2/en</dc:identifier>
    </item>
    <item>
      <title>Inside Google’s System for Coordinated A/B Testing across its Global Service Fleet</title>
      <link>https://www.infoq.com/news/2026/06/google-fleet-ab-experimentation/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Development</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/06/google-fleet-ab-experimentation/en/headerimage/generatedHeaderImage-1779569949510.jpg"/&gt;&lt;p&gt;Google has shared details of its fleet wide large scale A/B experimentation system designed to standardize experiment assignment, exposure logging, and configuration propagation across distributed services. The approach enables consistent measurement across products, reduces experiment conflicts, and improves reliability of data driven decision making at scale.&lt;/p&gt; &lt;i&gt;By Leela Kumili&lt;/i&gt;</description>
      <category>Distributed Systems</category>
      <category>Data-Driven Decision Making Series</category>
      <category>Infrastructure</category>
      <category>Feature Toggle</category>
      <category>Platforms</category>
      <category>Systems Thinking</category>
      <category>Logging</category>
      <category>User Experience</category>
      <category>A/B Testing</category>
      <category>DevOps</category>
      <category>Development</category>
      <category>Architecture &amp; Design</category>
      <category>news</category>
      <pubDate>Wed, 03 Jun 2026 14:54:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/06/google-fleet-ab-experimentation/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Development</guid>
      <dc:creator>Leela Kumili</dc:creator>
      <dc:date>2026-06-03T14:54:00Z</dc:date>
      <dc:identifier>/news/2026/06/google-fleet-ab-experimentation/en</dc:identifier>
    </item>
    <item>
      <title>Article: Two Misconfigurations That Caused Spark OOM Failures on Kubernetes</title>
      <link>https://www.infoq.com/articles/spark-oom-kubernetes-misconfigurations/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Development</link>
      <description>&lt;img src="https://res.infoq.com/articles/spark-oom-kubernetes-misconfigurations/en/headerimage/spark-oom-kubernetes-misconfigurations-header-1780044756757.jpg"/&gt;&lt;p&gt;After migrating Spark pipelines to Azure Kubernetes Service, two infrastructure settings interacted destructively: spark.kubernetes.local.dirs.tmpfs=true backed shuffle spill with RAM instead of disk, and a hard podAffinity rule forced all executors onto one node. Together, they caused repeated OOM kills invisible to standard diagnostics.&lt;/p&gt; &lt;i&gt;By Pranav Bhasker&lt;/i&gt;</description>
      <category>Apache Spark</category>
      <category>Cloud</category>
      <category>Kubernetes</category>
      <category>DevOps</category>
      <category>AI, ML &amp; Data Engineering</category>
      <category>Development</category>
      <category>Architecture &amp; Design</category>
      <category>article</category>
      <pubDate>Wed, 03 Jun 2026 09:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/articles/spark-oom-kubernetes-misconfigurations/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Development</guid>
      <dc:creator>Pranav Bhasker</dc:creator>
      <dc:date>2026-06-03T09:00:00Z</dc:date>
      <dc:identifier>/articles/spark-oom-kubernetes-misconfigurations/en</dc:identifier>
    </item>
    <item>
      <title>Node.js Moves to One Major Release Per Year, Starting with Node 27</title>
      <link>https://www.infoq.com/news/2026/06/nodejs-release-changes/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Development</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/06/nodejs-release-changes/en/headerimage/generatedHeaderImage-1780400494858.jpg"/&gt;&lt;p&gt;Node.js will change its release schedule starting with version 27 in October 2026, moving from two major releases per year to one. All releases will become Long-Term Support (LTS), removing the distinction between odd and even versions. An Alpha channel for early testing will also be introduced. This decision addresses maintenance challenges and aims to align with user needs.&lt;/p&gt; &lt;i&gt;By Daniel Curtis&lt;/i&gt;</description>
      <category>Versioning</category>
      <category>Semantic Versioning</category>
      <category>Release Management</category>
      <category>Web Development</category>
      <category>Node.js</category>
      <category>Development</category>
      <category>news</category>
      <pubDate>Wed, 03 Jun 2026 06:40:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/06/nodejs-release-changes/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Development</guid>
      <dc:creator>Daniel Curtis</dc:creator>
      <dc:date>2026-06-03T06:40:00Z</dc:date>
      <dc:identifier>/news/2026/06/nodejs-release-changes/en</dc:identifier>
    </item>
    <item>
      <title>Google Workspace CLI: Unified Command-Line Tool Built for Humans and AI Agents</title>
      <link>https://www.infoq.com/news/2026/06/google-workspace-cli/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Development</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/06/google-workspace-cli/en/headerimage/generatedHeaderImage-1780314884182.jpg"/&gt;&lt;p&gt;Google has released a new CLI for Google Workspace, offering a unified interface for various services like Drive, Gmail, and Calendar. Built in Rust, the tool dynamically adjusts to API changes and features over 100 bundled skills. It requires Node.js and a Google Cloud project for setup. Initial community feedback is mixed, highlighting both its dynamic capabilities and setup challenges.&lt;/p&gt; &lt;i&gt;By Daniel Curtis&lt;/i&gt;</description>
      <category>Google</category>
      <category>CLI</category>
      <category>Web Development</category>
      <category>Development</category>
      <category>news</category>
      <pubDate>Tue, 02 Jun 2026 06:33:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/06/google-workspace-cli/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Development</guid>
      <dc:creator>Daniel Curtis</dc:creator>
      <dc:date>2026-06-02T06:33:00Z</dc:date>
      <dc:identifier>/news/2026/06/google-workspace-cli/en</dc:identifier>
    </item>
    <item>
      <title>Java News Roundup: OpenJDK JEPs, Hazelcast, Quarkus, Hibernate, Koog, JHipster, Introducing Endive</title>
      <link>https://www.infoq.com/news/2026/06/java-news-roundup-may25-2026/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Development</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/06/java-news-roundup-may25-2026/en/headerimage/java-news-roundup-image-1780348608154.jpg"/&gt;&lt;p&gt;This week's Java roundup for May 25th, 2026, features news highlighting: lifecycle changes with two of the JEPs that were targeted for JDK 27; the GA release of Koog 1.0; point releases of Hazelcast, Quarkus, Hibernate and JHipster; the eighth milestone release of Spring AI 2.0; and introducing Endive, a JVM-native WebAssembly (Wasm) runtime.&lt;/p&gt; &lt;i&gt;By Michael Redlich&lt;/i&gt;</description>
      <category>Endive</category>
      <category>Koog</category>
      <category>Open JDK</category>
      <category>Hibernate ORM</category>
      <category>JDK 27</category>
      <category>Hazelcast</category>
      <category>Spring AI</category>
      <category>Quarkus</category>
      <category>Java</category>
      <category>JHipster</category>
      <category>Development</category>
      <category>Architecture &amp; Design</category>
      <category>news</category>
      <pubDate>Mon, 01 Jun 2026 21:30:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/06/java-news-roundup-may25-2026/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Development</guid>
      <dc:creator>Michael Redlich</dc:creator>
      <dc:date>2026-06-01T21:30:00Z</dc:date>
      <dc:identifier>/news/2026/06/java-news-roundup-may25-2026/en</dc:identifier>
    </item>
    <item>
      <title>Shopify Reports 15X Faster Graphql Execution with Breadth First Engine</title>
      <link>https://www.infoq.com/news/2026/06/shopify-graphql-cardinal-bfs/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Development</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/06/shopify-graphql-cardinal-bfs/en/headerimage/generatedHeaderImage-1779561076024.jpg"/&gt;&lt;p&gt;Shopify introduced GraphQL Cardinal, a new execution engine replacing depth-first traversal with breadth-first execution. The redesign improves large-scale GraphQL performance with up to 15x faster field execution, 6x lower GC overhead, and +4s P50 latency gains. It focuses on execution-layer efficiency and batched resolver processing for high-cardinality commerce queries.&lt;/p&gt; &lt;i&gt;By Leela Kumili&lt;/i&gt;</description>
      <category>Distributed Systems</category>
      <category>GraphQL</category>
      <category>API</category>
      <category>Low Latency</category>
      <category>Platform Engineering</category>
      <category>Optimization</category>
      <category>Search</category>
      <category>Performance</category>
      <category>Microservices</category>
      <category>Development</category>
      <category>Architecture &amp; Design</category>
      <category>news</category>
      <pubDate>Mon, 01 Jun 2026 14:25:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/06/shopify-graphql-cardinal-bfs/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Development</guid>
      <dc:creator>Leela Kumili</dc:creator>
      <dc:date>2026-06-01T14:25:00Z</dc:date>
      <dc:identifier>/news/2026/06/shopify-graphql-cardinal-bfs/en</dc:identifier>
    </item>
    <item>
      <title>BadHost Vulnerability Exposes AI Agents, Evaluators, and LLM Gateways</title>
      <link>https://www.infoq.com/news/2026/06/badhost-ai-systems-vulnerability/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Development</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/06/badhost-ai-systems-vulnerability/en/headerimage/badhost-ai-vulnerability-1780322270507.jpeg"/&gt;&lt;p&gt;BadHost is a high-severity authentication bypass vulnerability in the widely used Python web framework Starlette, with 325 million weekly downloads. The flaw allows attackers to use malformed HTTP Host headers to bypass path-based access controls and access sensitive AI agent infrastructure, among other systems.&lt;/p&gt; &lt;i&gt;By Sergio De Simone&lt;/i&gt;</description>
      <category>Python</category>
      <category>Open Source</category>
      <category>Agents</category>
      <category>Security Vulnerabilities</category>
      <category>DevOps</category>
      <category>AI, ML &amp; Data Engineering</category>
      <category>Development</category>
      <category>news</category>
      <pubDate>Mon, 01 Jun 2026 14:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/06/badhost-ai-systems-vulnerability/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Development</guid>
      <dc:creator>Sergio De Simone</dc:creator>
      <dc:date>2026-06-01T14:00:00Z</dc:date>
      <dc:identifier>/news/2026/06/badhost-ai-systems-vulnerability/en</dc:identifier>
    </item>
  </channel>
</rss>
