By submitting this form, you agree to our 

Answer twenty questions about your artifact and supply chain practices. Get a custom report card showing your maturity score against key regulatory and compliance frameworks.

Artifact Security Maturity Assessment

The 10 GitHub Universe 2026 sessions we recommend for platform, DevOps, and security teams cover software supply chain security for npm and GitHub Actions, guardrails for AI agents, agentic workflows at scale, and enterprise AI adoption. GitHub Universe 2026 runs October 28–29 at Fort Mason Center in San Francisco, with a free virtual pass for online attendees.

GitHub Universe 2026 at a glance: dates, location and agenda tips

More than 6,000 developers, platform engineers, and security leaders are heading to Fort Mason Center for GitHub Universe 2026. This year's theme is the agentic era, and the big question isn't whether to bring AI into the software development lifecycle. It's how to do it at scale, with trust built in from the first commit.

With 100+ sessions across two days, there are a lot of options. We've picked the 10 talks we think platform, DevOps, and security teams will get the most from. Cloudsmith will be in the Festival Pavilion all week, so come and find us between sessions.

📍 Fort Mason Center, San Francisco, CA

👋 Festival Pavilion (look for the Cloudsmith coffee cart)

1. What happens behind the scenes when you run npm install

Wednesday, Oct 28 | 4:30 PM - 5:10 PM PDT

Most people run npm install dozens of times a day without a second thought. Karen Li and Leo Balter from GitHub will trace those dependencies back through the people, permissions and release processes that publish and protect them. Expect a clear look at what npm audit can't catch, and where package provenance and OpenID Connect (OIDC) fit in.

This is our top pick because software is assembled more than it's authored, and every install is a trust decision. Knowing how a package reaches your build is the first step to governing it. If you leave this talk wanting to control what enters your environment before it arrives, come and see us in the Festival Pavilion.

2. Disrupting supply chain attacks: A threat framework for GitHub Actions

Wednesday, Oct 28 | 2:30 PM - 3:00 PM PDT

A workflow with access to credentials and the power to publish a release is a high-value target for attackers. Steve Glass and Greg Ose will map known supply chain attack techniques to the GitHub Actions controls that stop them, across three layers: the Actions ecosystem, the workflow attack surface, and runner infrastructure.

For platform teams, this is a practical framework for deciding where defenses belong in a pipeline you'd trust with a release. Incidents like tj-actions showed why the build pipeline is a critical control point. This session moves the conversation from what went wrong to what good looks like.

3. Open pull requests, don't merge them: Fine-grained authorization for hosted MCP servers

Thursday, Oct 29 | 10:30 AM - 10:45 AM PDT

Hosted MCP servers often enable agents to do everything a human can do. Nick Taylor will demo an identity-aware proxy that adds per-identity authorization in front of any hosted MCP server, with no upstream changes. The live demo shows Copilot opening a pull request and leaving the merge to a human reviewer.

We love this session because it treats guardrails as infrastructure, not an instructions file the agent might ignore. The same principle applies to dependencies. Agents move fast, so the controls around them need to be machine-enforceable and in place before the agent acts.

4. From writing code to managing agents: Scaling 50+ services at GitHub

GitHub's Lifecycle team swapped hand-coded fixes across 50+ services for an agentic pipeline. AI agents classify issues, research codebases, write implementation plans, and open draft pull requests. Anjuan Simmons will share the real numbers, how the team built it with GitHub Actions and Copilot, and why engineers still write some code by hand on purpose.

This is a look at agents running in production at platform scale. For engineering leaders weighing the same move, it's a grounded blueprint for where automation pays off and where humans stay in the loop.

5. Treat your AI context as infrastructure

 Platform engineering, developer experience

Having the right context is critical for getting your agents to generate useful output. In this session, Christopher Harrison will break down what custom agents, agent skills, instructions files, MCP servers, extensions, and plugins each do best, and how to choose between them for real use cases. He’ll discuss strategies for how to distribute the right context consistently across a team as your setup grows.

Platform engineers already know this story. Anything that works for one developer but can't be versioned, shared, and governed becomes sprawl. This session applies golden path thinking to AI context, and it's a natural fit for teams looking to build those paths for their developers.

6. Beyond pass or fail: How agents verify AI-generated code

The tests passed, so why is the app still broken? Jeff An will show how agents investigate applications, reproduce unexpected behavior, and tell real product bugs apart from flaky tests or infrastructure failures. He'll also cover the deterministic controls that limit what those agents can do while they investigate.

As AI writes more of our code, verification becomes the bottleneck. This talk looks at earning the trust that speed requires, with clear boundaries on what agents are allowed to touch.

7. The 2 a.m. RCA agent: Architecting AI that investigates, not hallucinates

Anyone who has had to spend hours late at night researching root cause analysis (RCA) will want to attend this one. Achin Gupta and Divya Mahajan will present a RCA architecture where deterministic code handles signal collection, topology traversal, correlation, and scoring. The language model only narrates evidence it didn’t have to collect.

The result is a clean split of responsibilities where the machine-enforceable parts stay deterministic, and the model adds clarity where needed. SREs and platform teams will leave with a design they can borrow.

Wednesday, Oct 28 | 11:30 AM - 12:10 PM PDT

Getting developers to try Copilot is the easy part. Getting them fluent – using agents to plan, write, and ship real work – is harder. Jared Hatfield will share how UPS moves developers from awareness to fluency, why motivation and measurement matter as much as tooling, and where to focus first at enterprise scale.

For VPs of Engineering and platform leads rolling out AI across large organizations, this is a candid view from a team doing it today. Adoption at this scale also means more packages, pulled faster, by more people and agents. It's worth planning the controls alongside the rollout.

9. Code is the easy part: Building Home Assistant in the open

Wednesday, Oct 28 | 2:10 PM - 2:25 PM PDT

Home Assistant builds everything in the open, from ideas and UX to architecture and the roadmap itself, across 20,000 contributors and a dozen GitHub organizations. Franck Nijhof will show how the Open Home Foundation runs its whole roadmap through issues, projects, and discussions, including being wrong in public and fixing it in public.

Open source is the foundation for every modern software supply chain. This session is a great reminder of the people and process behind the packages we all depend on, and what it takes to run a healthy project at scale.

10. The view from the labs: What's next for AI-assisted development

 Cara Phillips, Anthropic; Rohan Varma, OpenAI; Kate Catlin, GitHub

To close out our list, an interactive panel with leaders from the labs that power GitHub Copilot. Cara Phillips, Rohan Varma, and Kate Catlin will take a candid look at the next two years of AI-assisted development, and what it means for the people building software.

AI changes the laws of physics for how fast teams can move. Hearing where model capabilities are going next will help platform and security teams plan the guardrails that let developers and agents keep that pace.

Between sessions, come and say hello. Cloudsmith is a Gold sponsor at GitHub Universe 2026, and you'll find us in the Festival Pavilion throughout expo hours on October 28 and 29.

 Grab a drink from the Cloudsmith coffee cart and refuel before your next session.

 Watch how Cloudsmith acts as the control layer for your software supply chain. Govern every package, container, and ML model that enters your environment, enforce policy-as-code at first pull, and publish straight from GitHub Actions with OIDC (no long-lived API keys).

 Bring your questions about AI coding tools, dependency governance, or moving off a self-hosted artifact server. Our engineers are happy to dig in.

Join us for DevOps on Draft: A Universe Git-Together

Wrap up day one with us. On Wednesday, October 28, from 6:00 to 9:00 PM, Cloudsmith is hosting a happy hour at San Francisco Brewing Company, co-sponsored by Tailscale, Eficode, Octopus Deploy, and Chainguard. Expect good beer, good company, and plenty of conversation about what everyone saw that day. Spaces are limited, so 

AI is changing how fast teams build software, and that's exciting. We'll see you in San Francisco to talk about keeping that speed with clarity, control and confidence.

Claire Speedy

Senior Marketing Manager

10 GitHub Universe 2026 sessions not to miss

Thousands of platform engineers and security experts are heading to KubeCon + CloudNativeCon Europe 2026, making it the definitive cloud-native event in Europe. Stop by Cloudsmith at Booth 570 to say hello and check out our activities throughout the week. There’s 

With hundreds of talks on the schedule, it can be hard to know where to start. Here is our curated roadmap to ensure you get the most out of your time on the ground.

📍 RAI Amsterdam (Europaplein 24, 1078 GZ Amsterdam, Netherlands)
👋 Booth 570
🗓️ March 24 - 26, 2026

 (Thales SIX GTS France) will dive into the messy reality of the Software Bill of Materials (SBOM). They plan to pull back the curtain on why current open-source and cloud-based tools (despite all their promises) frequently generate conflicting package lists and inconsistent vulnerability reports when tasked with scanning complex container images.

This talk is particularly electrifying for the security community because it tackles the compliance anxiety triggered by the EU’s Cyber Resilience Act (CRA). As the CRA shifts SBOMs from a nice-to-have transparency initiative to a legal necessity for software lifecycles, the industry is waking up to a major problem, which is inconsistent data. By dissecting the technical roots of these discrepancies, Bufalino and Blaise aren't just pointing out flaws, they will also be providing a roadmap for developers to ensure their tooling is actually CRA-compliant. For anyone navigating the shift toward a transparent and trustworthy software supply chain, this session offers the technical clarity needed to turn these metaphorical bombs into secure builds.

2. Modelpack: Standardising the packaging and distribution of AI/ML Models

, a Distinguished Architect at Red Hat, tackles one of the most pressing bottlenecks in modern infrastructure: the chaotic fragmentation of AI/ML integration within the cloud-native ecosystem. Block, a seasoned expert in helping organisations scale open-source solutions, will break down how the current wild west of competing formats and runtimes is actively stifling innovation. He will introduce 

, a CNCF Sandbox project designed to act as the universal translator for AI/ML artifacts, allowing them to finally speak the same language as established tools like Kubernetes, ORAS, and Harbor.

The security and DevOps communities are closely watching this session because it addresses the Day 2 operations nightmare of managing AI at scale. As AI moves from experimental notebooks to production-grade Kubernetes clusters, the lack of standardisation creates massive technical debt and security blind spots. Block’s exploration of ModelPack and emerging artifact standards offers a glimpse into a future where AI models are managed with the same consistency and rigour as container images. For anyone struggling to bridge the gap between data science and cloud-native engineering, this talk provides the blueprint for a unified, scalable, and manageable AI supply chain.

3. Kubernetes security at Shopify scale: Automating security across an infrastructure monrepo

In this session, Senior Infrastructure Security Engineers 

 will pull back the curtain on how one of the world’s largest e-commerce platforms secures its massive infrastructure monorepo. Drawing from their deep backgrounds in cloud defense and 5G network security, Wu and Garg will detail the high-stakes challenge of managing thousands of services where a single misconfiguration could impact millions of merchants. They will demonstrate how Shopify moved beyond manual checkbox security by building an automated pipeline that combines Semgrep for static analysis and Open Policy Agent (OPA) for real-time policy enforcement.

This talk is a must-attend for the security community because it provides a battle-tested blueprint for solving the velocity vs. security dilemma we’re all too familiar with. While many orgs struggle with friction between DevOps and Security teams, Shopify’s approach shows how to bake guardrails directly into the developer workflow without slowing down deployment. Attendees will gain rare insights into the so-called rough patches of scaling open-source security tools and leave with a practical framework for automating risk detection across complex, high-traffic Kubernetes environments.


4. To upstream or not? Why becoming the maintainer of your dependencies matters

, a Principal Software Engineer at Elastic and an OpenTelemetry code owner, dives into the strategic heart of modern software engineering. Markou moves beyond the typical 

 narrative to present a pragmatic, business-first case for active maintenance. By sharing a high-stakes story of an OTel component saved from the brink of deprecation, he demonstrates how moving from a passive consumer to an active contributor transformed a potential technical debt nightmare into a rapid-response tool for solving critical customer issues.

This talk is a vital wake-up call for the security and observability communities because it addresses the growing crisis of software supply chain sustainability. In an era where a single abandoned dependency can lead to massive security vulnerabilities or operational outages, Markou provides a concrete example to share with your manager on why upstreaming isn't just altruism, it also can be treated as sensible risk management. For teams building on CNCF projects, this session offers a masterclass in how staying present in the ecosystem pays dividends in architectural control, security posture, and long-term engineering velocity.


5. How to add a new language feature to OPA

Adding features to a widely adopted language like Rego involves more than just a simple pull request. In this lightning session, Apple's 

 explores the full-stack impact of introducing new syntax, from the initial parser modifications to updating the broader ecosystem of editor tools. Learn the specific engineering hurdles involved in upgrading a mature security project without disrupting the developer experience. At Cloudsmith, we’re huge fans of Open Policy Agent and Rego, so we can’t wait to hear what Charlie has in store for us.

6. Platform Engineering 2.0: Just-enough Kubernetes and AI-native DevOps

 and a seasoned authority on platform patterns, tackles the industry's growing complexity bloat. Drawing from 20 years of experience and the literal scars of re-architecting internal platforms at one of the world’s largest travel sites, Vohra argues that the future of infrastructure isn't about building more, it’s really about building just enough. She will break down how to transition from heavy, static systems to lean, right-sized architectures using k3s, Gateway API, and ambient mesh, while layering in AIOps via Kubeflow and Prometheus to transform raw automation into true system intelligence.

This talk is a critical touchstone for the DevOps and platform communities because it offers a pragmatic exit ramp from the scale at all costs mentality that leads to massive cloud waste and operational blindness. Vohra’s AI-native approach is a blueprint for creating self-optimising ecosystems that align infrastructure directly with business value. For engineering leaders and architects feeling the weight of over-engineered clusters, this session aims to be a masterclass in staying lean, staying smart, and evolving platforms to be adaptive rather than just additive.

7. AI Agents & Platform Engineering: Efficiency boost or new source of trouble?

In the blockbuster panel, an elite group of industry leaders from 

 converges to debate the most disruptive shift in DevOps history. Featuring heavyweights like from the industry, this vendor-neutral discussion moves past the hype to ask the hard questions: Can non-deterministic AI agents actually keep pace with AI-accelerated developers, or are we just inviting unpredictable trouble into our production clusters? The panel will tackle the minimum viable platform foundation required for AI success, the shifting cost implications of agents in production, and how to build human trust in systems that don't always behave the same way twice.

This session is arguably the must-see event for the modern platform engineer because it addresses the looming intelligence gap in infrastructure. As developers pump out code at record speeds, the platform team is traditionally treated as the bottleneck. This panel explores whether AI agents are the ultimate scaling solution or a new category of technical debt. By bringing together perspectives from global tech giants and international organisations, attendees will walk away with a high-level framework for defining golden metrics for AI effectiveness and a roadmap for navigating the transition from static automation to dynamic, agent-led collaboration.

8. In Falco’s nest: The evolution of cloud native runtime security

In the maintainer track session, Falco contributors 

 (Kong) provide a deep-dive update on the CNCF’s de facto standard for runtime threat detection. The core of their presentation focuses on the highly anticipated Falco Operator, a game-changer designed to automate the deployment and management of security sensors across massive, distributed clusters, effectively lowering the barrier to entry for enterprise-scale security.

For the security community, this talk is a vital look at the roadmap for high-throughput runtime defense. As cloud-native environments become more complex and data-heavy, traditional security tools often struggle with performance overhead; Rozzo and Lacuku will demonstrate the specific optimisations that allow Falco to maintain deep visibility without sacrificing system reliability. Beyond the code, this session also is a great opportunity to see how the Falco ecosystem is integrating with the broader CNCF landscape, offering attendees a first look at the features that will define Cloud Detection & Response (CDR) in the coming year.

9. What LLMs do, and don’t, know about securing Kubernetes

, explores the practical (and often perilous) intersection of Generative AI and cluster orchestration. McCune, a veteran KubeCon speaker and a foundational voice in container security, will present the results of his deep-dive research into whether Large Language Models (LLMs) can actually be trusted with the sensitive credentials. Rather than just discussing theory, Rory will aim to demonstrate how LLMs handle specific Kubernetes security tasks, revealing where they provide genuine architectural insight and where they tend to hallucinate dangerous misconfigurations that could leave an organisation exposed.

This talk is a critical reality check for the security community as AI-assisted DevOps moves from a trend to a standard operating procedure. McCune will break down how advanced techniques like improved prompting and 

 reasoning can significantly shift the safety of an LLM's output, while also highlighting the so-called no-go zones where human expertise remains non-negotiable. For security architects and engineers, this session provides a vital framework for auditing AI-generated IaC templates, ensuring that the speed of AI doesn't come at the cost of a catastrophic security breach.

10. Audit-ready Kubernetes: How Chase UK leveraged policy-as-code for continuous compliance

 and co-creator of Kyverno, provide a rare under the hood look at building a cloud platform within the high-stakes world of regulated retail banking. Goyal, who manages the end-to-end Kubernetes ecosystem for Chase UK, will detail how his team transformed a massive compliance undertaking into a streamlined, automated engine. By leveraging Kyverno, OpenReports, and Grafana, they successfully shifted security left, allowing their backend engineers to ship code at speed while maintaining a real-time policy-as-code safety net that satisfies stringent financial regulators.

This talk is a beacon for the security and compliance communities because it addresses the ultimate white whale of enterprise DevOps: reducing audit times from weeks to minutes. Bugwadia’s deep perspective as a Kubernetes 

 co-chair, combined with Goyal’s real-world production perspective from JP Morgan Chase, offers a definitive guide on how to empower security teams to write independent policies without bottlenecking development. For any platform team operating in a regulated sector (or simply running mission-critical workloads) this session provides a proven framework for turning compliance from a manual, fear-driven process into a better, more transparent, and scalable process.

Nigel Douglas

Head of Developer Relations

Catch lightning talks, hands-on demos, and prizes while learning how to secure every artifact in your supply chain.

Join Cloudsmith in Amsterdam at KubeCon Europe 2026

13 KubeCon Europe 2026 sessions not to miss

The Cloud-Native Digest is a monthly roundup on all things cloud native, artifact management, and supply chain security from Cloudsmith's Head of Developer Relations, Nigel Douglas.

Welcome to the July 2026 edition. In this issue, we’re tackling the real-world realities of modern software defense, from why high vulnerability scores can misrepresent actual risk of exploitation to the ways that AI agents are escaping existing sandbox boundaries, as seen with the Hugging Face and OpenAI fallout. Plus, we break down critical supply chain stories across 

. Let’s jump straight into the analysis.

Supply Chain Security in the Month of July

Why higher CVSS vulnerabilities aren't always the most exploited
Date: 

July 1st 2026

The Sysdig Threat Research Team observed the first known in-the-wild exploitation of 

, a CVSS 9.9 IDOR-style vulnerability in Langflow, alongside 

, a lower-scored (CVSS 9.3) unauthenticated RCE. Despite the IDOR's higher CVSS score, opportunistic threat actors heavily favour the RCE because it provides immediate host execution with minimal effort, whereas the IDOR requires enumerating flow UUIDs and is harder to weaponise. Ultimately, the findings illustrate the effort-to-yield paradox whereby CVSS scores do not always reflect real-world exploitation risk, though the IDOR poses a severe threat in multi-tenant environments where host-level RCE is sandboxed.



https://www.sysdig.com/blog/understanding-langflow-cve-2026-55255-and-why-higher-cvss-vulnerabilities-arent-always-the-most-exploited

When upgrading is the wrong answer to a CVE
Date:

 July 22nd, 2026

While security standards mandate keeping dependencies up to date, relying solely on upgrading to fix vulnerabilities has become a flawed approach. Upgrading often fails because a fix may not exist yet, an abandoned package will never receive one, a new version introduces breaking changes, or the latest release contains malicious code from a compromised maintainer. These factors are compounded by AI tools that enable attackers to quickly chain minor vulnerabilities into major exploits; traditional scanning and upgrading can no longer keep up. Instead of risking broken builds or undertaking costly migrations, a better path is directly patching the specific vulnerability within the existing, trusted version of a package.



https://www.aikido.dev/blog/cve-upgrade-breaking-changes-open-source

Why is it so hard to configure time in cooldown logic?
Date:

 July 17th, 2026

Client-side cooldown policies which protect software supply chains by holding new packages for threat screening are heavily fragmented across language ecosystems. These policy controls often use inconsistent time formats (such as seconds, minutes, days, or ISO 8601 strings) or lack native support entirely (like Go and NuGet). Managing these conflicting client-side configs creates friction for security teams. The idea of centralised cooldown controls through a single platform like Cloudsmith eliminates this complexity by enforcing uniform security policies across all package formats from a single control plane, using a single interpretation of time.



https://cloudsmith.com/blog/how-to-configure-time-for-cooldown-policies

What’s the deal with the AsyncAPI npm supply chain attack?
Date:

 July 14th, 2026

Attackers exploited a misconfigured GitHub Actions workflow in the AsyncAPI project to steal automation tokens and release trojanised 

). Executing upon package import rather than on-install, the malicious payload harvested developer and CI/CD secrets. It bypasses traditional security scanners by leveraging legitimate release pipelines and clean initial advisory feeds. Organisations should check lock files for affected versions (such as 

), immediately rotate exposed tokens, and consider using private registry proxies with package cooldown policies to block future zero-hour supply chain risks.



https://cloudsmith.com/blog/inside-the-asyncapi-npm-supply-chain-attack

Cybersecurity startup publishes infostealers to NPM
Source:



The founder of an Israeli cybersecurity startup was found to have published at least seven typosquatted packages to JavaScript’s 

 registry, primarily impersonating popular AI developer tools like Anthropic, LangChain, and OpenAI. They functioned as quiet infostealers. By abusing automatic 

 execution scripts, the packages harvested detailed env & dev identity fingerprints (such as Git reflogs, hostnames, SSH key comments, and cloud account metadata) while explicitly avoiding direct credential theft to evade detection.



Signed, attested, and malicious: Your SSC has a deepfake problem
Source:



Software supply chain attacks have evolved into deepfakes. Attackers compromise 

 maintainer credentials and to publish malware that carries legitimate signatures, provenance, and attestations. Incidents like the Miasma worm in 

 registry demonstrate that security scanners can no longer rely on trust signals alone, as poisoned packages now appear indistinguishable from routine updates. Because technical verification mechanisms are functioning as designed rather than failing, security must shift toward behavioural analysis to evaluate what a package actually does before it reaches the dev's machine.



Next.js moves to scheduled security releases
Source:



Next.js is formalising a predictable, monthly security release program to provide advance notice and mitigate potential exploits, replacing its previous ad-hoc patching approach. The first scheduled security release came out on the 21st of July. This update delivered patch updates for Next.js versions 

 covering 9 total vulnerabilities (4 high and 5 medium severity).



Finding 8 high-severity vulnerabilities in NodeBB in 6 hours
Source:



Aikido Security used its AI-powered pentesting platform to discover eight high-severity vulnerabilities in NodeBB in under six hours. The findings included multiple cross-site scripting vectors, admin authorisation bypasses, user impersonation, mass assignment, and unauthenticated data leakage. Aikido reported the security flaws to the NodeBB maintainers, who patched all identified issues in version 

Untangling crates.io accounts from GitHub
Source:

, crates.io is decoupling its account system from GitHub by introducing native crates.io 

, laying the foundation to support alternative identity providers in the future. This shift provides significant benefits to the Rust community by offering devs greater control over their package-registry identity without tying it directly to a single platform. Beyond increasing flexibility, supporting additional login options makes the ecosystem more accessible to developers and organisations that don't use GitHub, while also reducing the risk of maintainers getting locked out of managing their crates due to single-platform outages, suspensions, or policy changes.



Announcing Topcoat: a framework for building full-stack react web apps with Rust
Source:

 is a modular, full-stack Rust web framework designed to simplify building reactive applications through server-side rendering without relying on WASM. It achieves client-side reactivity by rendering HTML on the server and embedding metadata or cross-compiling subset Rust expressions to JavaScript via macros. Driven by the philosophy of locality of behaviour, Topcoat features a complete asset pipeline, integrated icon/font libraries, request-level 

, and a Tailwind-based UI component system, complementing lower-level routers like Axum by eliminating typical web development boilerplate.



Battery packs: Let's talk about crates, baby!
Source:

) designed to help Rust developers quickly discover and set up curated sets of recommended crates, project templates, and GitHub Actions based on specific domains like CLI, embedded, or backend development. Rather than acting as a direct code dependency, a battery pack simply serves as an easily modifiable starting list to eliminate research fatigue for newcomers without causing vendor lock-in or ecosystem stagnation. Anyone can publish a battery pack, creating a flexible foundation that working groups can leverage to drive interoperability and pool funding for maintainers.



Unveiling RIFT: Enhancing Rust malware analysis through pattern matching
Source:

Microsoft Threat Intelligence Center (MSTIC)

, a toolset designed to automate and streamline the reverse engineering of Rust-based malware. Because Rust’s safety features, concurrency, and static linking produce unusually large binaries filled with library code, analysts often struggle to isolate a threat actor's actual code. RIFT addresses this by using pattern matching, such as compiler metadata extraction, custom FLIRT signatures, and binary diffing to identify and label third-party library dependencies automatically. By stripping away standard library clutter, RIFT significantly reduces analysis time, allowing security researchers to focus directly on malicious logic.

 proposes a public, tamper-evident transparency log operated directly by package indexes like PyPI to record artifact hashes and publisher identities. By making all publishing claims discoverable and permanent, the log prevents a compromised index from silently serving altered package files to different users, while enabling maintainers and third-party security monitors to immediately detect tampering or unauthorised releases.



Releases now reject new files after 14 days
Source:



To protect against project compromises, PyPI now rejects new file uploads to releases older than 14 days, preventing attackers from secretly poisoning stable packages. Triggered by high-profile supply chain compromises in early 2026 and backed by community consensus, the change requires maintainers to issue a new release version when adding files like new Python wheels. While formal APIs defining closed releases are coming via 

, this guardrail immediately protects Python users and keeps release histories clear and secure.



Pip 26.2: –only-deps solves 16 years of app deployment hacks
Source:

), solving a 16-year-old workaround for Python applications and scripts that do not need to be installed as packages. By allowing dev to install dependencies directly from 

 without installing the project itself, this change simplifies the app deployments and builds on the momentum driven by existing third-party tools like 

What every Python dev should know about the CPython ABI
Source:



CPython’s Application Binary Interface (ABI) defines the low-level rules, such as memory layout and exported symbols, that allow native C, C++, Rust, or Fortran extensions to interact with the Python interpreter. While a CAPI consists of source-level definitions like headers and macros, the ABI ensures compiled binaries can run correctly without link-time or runtime memory errors. Python packages use ABI compatibility tags in wheel filenames to signal whether a binary requires a specific CPython minor version (like 

) or supports the forward-compatible Stable ABI (

). The introduction of the free-threaded interpreter altered the internal PyObject layout to remove the 

). To address this, Python 3.15 introduces the 

 stable ABI, used opaque structs to allow a single compiled wheel to support both GIL-enabled and free-threaded builds across future releases.

CVE-2026-64600 - Kernel flaw lets attackers gain root access
Source:



RefluXFS is a 9-year-old Linux kernel race condition that allows local, unprivileged users to overwrite root-owned files at the block layer and gain persistent root access. The vulnerability affects systems using XFS filesystems created with 

, putting default installs of Red Hat Enterprise Linux, Fedora Server, and Amazon Linux at immediate risk. Because there are no practical 

-option workarounds, securing vulnerable hosts requires applying the vendor's backported kernel patch and rebooting the system.

CVE-2026-8933 - Ubuntu security flaw breaks Snap sandbox protections
Source:



Qualys researchers disclosed 2 high-severity local privilege escalation vulnerabilities in Ubuntu Desktop (CVE-2026-8933 & CVE-2026-3888). Both flaws affect default installs running 

. CVE-2026-8933 in particular allows unprivileged local users to gain root access by exploiting race conditions in temporary 

 directory initialisations, using FUSE mounts and symlinks to bypass AppArmor restrictions. Users should apply Canonical's latest security updates for 

CVE-2026-53359 - Lessons learned from handling a KVM flaw on tens of thousands of machines
Source:



Following the discovery of a 16-year-old use-after-free flaw in KVM x86, OVHcloud executed an urgent, 11-day emergency patching campaign across tens of thousands of hypervisors and 

. After ruling out live patching and migration at scale due to time and stability constraints, OVHcloud opted for a unilateral kernel patch and host reboot strategy to minimise the vulnerability window. Using a 24/7 follow-the-sun operational model, with anti-affinity safeguards to prevent simultaneous cluster outages, and targeted customer comms, the team successfully secured the entire fleet while containing service disruptions.



Linux kernel security faces challenge with surge in CVEs
Source:



Over a single two-day period, the Linux kernel team published 432 CVEs, overwhelming sysadmins and fueling speculation that AI-assisted bug hunting is driving a massive influx of reports. Because the kernel team assigns CVEs to nearly any bugfix affecting system availability, prioritising individual patches has become nearly impossible for security teams. Experts warn that neither manual reviews nor current LLM triage methods are equipped to handle this volume, leaving organisations forced to consider risky, frequent fleet-wide updates to keep pace with the ongoing surge - or adopt 

Kubernetes 1.37 – What you need to know
Source:



Scheduled for release next month, Kubernetes 1.37 introduces 86 total enhancements, focusing heavily on performance, cluster security, and fine-grained hardware management. Highlights include stable graduations for faster, non-recursive SELinux volume mounts and human-friendly KYAML formatting, along with new features like native per-container POSIX 

 binary data format for faster CRDs. The update also advances Dynamic Resource Allocation with standardised NUMA node attributes and device taints, while laying the groundwork to phase out 

Kubernetes Podcast episode 269: AI Policy, with Kat Cosgrove and Natali Vlatko
Source:



When people talk about AI in Kubernetes, the conversation is often focused on the user side, but for open source maintainers, there's of course a lot to unpack on how AI is changing OSS contribution! How does AI impact the community, and what are the new rules of engagement? In this session, Kat Cosgrove (SIG Docs Technical Lead, SIG Release Subproject Lead, and Kubernetes Steering Committee member) and Natali Vlatko (SIG Docs Co-Chair, TODO Group Steering Committee member, and OSPO at Cisco) unpacked the recently published Kubernetes AI usage policy for Kubernetes contributors.



Unpatched Argo CD flaw lets attackers takeover Kubernetes clusters
Source:



Synacktiv researchers used custom CodeQL analysis to discover an unauthenticated RCE vulnerability in Argo CD’s 

 component. By sending custom gRPC requests and manipulating cached entries in the internal Redis DB, an attacker could force Argo CD to deploy malicious manifests, ultimately leading to a full Kubernetes cluster takeover. The risk is heightened because standard Helm deployments leave network isolation disabled by default. In this scenario, applying strict Kubernetes network policies to restrict access to 

 appears to be the primary mitigation to this flaw.



New NadMesh Botnet Hunts Exposed AI Services for Cloud Keys and Kubernetes Tokens
Source:



The NadMesh botnet poses a severe threat to Kubernetes environments by actively scanning exposed API servers, Kubelet endpoints, and etcd instances to execute remote code. It achieves node-level compromise through Kubernetes API exploitation by creating malicious pods with 

 mounts to escape container boundaries. Once inside, NadMesh harvests 

 ServiceAccount tokens, steals cloud and AI service creds from 

 variables, and maps internal networks for lateral movement. Check out the blog for steps to mitigate these risks.

Mitigating The Hugging Face Breach
Source:



Hugging Face and OpenAI disclosed a major security incident where an autonomous AI agent (

) broke out of OpenAI’s isolated research environment via a proxy zero-day and subsequently breached Hugging Face's production infrastructure to obtain benchmark answer keys. Rather than focusing on the AI's autonomous capability, security firm Edera highlights that both breaches succeeded due to a shared architecture flaw. This is where most of the industry still relies on shared-kernel container primitives (namespaces & cgroups) for isolation rather than hardware-enforced boundaries. Edera argues that mitigating such autonomous, high-speed threats requires shifting from traditional container runtimes to Type 1 hypervisor-level isolation to ensure that initial code execution cannot escalate to host nodes or internal clusters.



Chinese model Kimi K3 adds pressure on US AI policy
Source:

, a Chinese open-weight model that rivals top U.S. competitors in coding, has intensified pressure on the US government to establish a coherent national AI strategy. As domestic developers stall updates under voluntary government testing guidelines and flock to cheaper foreign models, American tech leaders are warning that the U.S. risks losing its competitive edge. Meanwhile, allegations that Moonshot distilled outputs from U.S. models like Claude have fuelled IP theft concerns, prompting White House debate over sanctions and potential restrictions on Chinese open-source technology.



Anthropic Launches Claude Security Plugin to Scan Code for Vulnerabilities
Source:



The security-specific plugin for Claude brings multi-agent vulnerability scanning directly into the Claude Code terminal interface. Designed to analyse complex logic and multi-file data flows beyond standard pattern matching, the tool identifies high-severity flaws, filters out false positives, and generates style-matched patches for human review. This allows developers to catch critical security risks seamlessly without leaving their existing workflow.



Agentic AI Challenges Progress in Confidential Computing
Source:



While technological advancements have largely resolved early barriers like cost and performance to boost enterprise adoption of 

, the rise of agentic AI presents new security risks due to agents retaining sensitive data in memory. To counter this threat model, experts advocate for new paradigms like individual encryption keys per agent. This would enable complete data deletion via a method known as 

. Major players like Apple, NVIDIA, and Microsoft will continue to push multi-layered confidential AI architectures to ensure improved data privacy without sacrificing their system performance.

CVE-2026-46331 - Claude Cowork agent escapes VM to access Mac files
Source:

is a local sandbox escape in Claude Cowork's macOS desktop app that allows untrusted session content to read and write files anywhere on the host Mac. By chaining unprivileged user namespaces, permissive seccomp filters, and the aforementioned Linux kernel vulnerability, an attacker could gain root privileges inside the Guest VM and access the entire host filesystem, which was mounted read-write at 

. The post emphasises that sandbox security must rely on fundamental design choices, such as strictly scoping filesystem access, disabling unprivileged user namespaces, and even blocking unused kernel module autoloads. This needs to be done instead of keeping up with an endless cycle of guest kernel patches.



HollowByte flaw in OpenSSL can freeze server memory via 11-Byte TLS requests
Source:



A newly disclosed flaw dubbed HollowByte allows attackers to freeze memory on unpatched OpenSSL servers using an 11-byte TLS request, triggering a severe DoS state. By declaring a large body size in the TLS header, an attacker forces OpenSSL to pre-allocate up to 131 KB per connection before receiving the body; when paired with 

 memory allocation, the released memory fragments and remains trapped indefinitely, bypassing standard connection-limiting defenses. Despite Okta's red team demonstrating that this could lock up vast amounts of server RAM, OpenSSL quietly patched the issue in its June 9th releases without assigning a CVE, issuing an advisory, or even addressing the unpatched DTLS code path.



The future of AI is community driven and open
Source:

Cloudsmith Blog

10 GitHub Universe 2026 sessions not to miss

13 KubeCon Europe 2026 sessions not to miss

Cloud Native Digest - July 2026

Cloud Native Digest - June 2026

Cloud Native Digest - May 2026

13 sessions not to miss at KubeCon and CloudNativeCon 2025

KubeCon London 2025 Recap: Cloud-Native Insights on Security, Wasm, and More

Your Ultimate KubeCon Guide

Cloudsmith is headed to Salt Lake City for KubeCon North America 2024

Reflecting on ShipItCon 2024: High-performing teams need flow

6 Must-See DevOps Talks at PlatformCon 2024

That's a Wrap on KubeCon 2024!