# cves Published articles for cves. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Oracle September 2026 Critical Security Patch Update addresses 672 CVEs DevFeed: [Oracle September 2026 Critical Security Patch Update addresses 672 CVEs]() Original publisher: [Read original article]() Author: Research Special Operations Published: 2026-09-15T21:00:28Z Content type: article Language: en Sources: [Tenable Blog]() Topics: [Security](), [Vulnerabilities](), [Network]() Tags: [cves](), [network](), [security](), [september-2026](), [update](), [vulnerabilities]() ### AI overview Oracle's September 2026 Critical Security Patch Update fixes 672 unique CVEs through 673 security updates across 17 Oracle product families. It includes 104 critical patches, with Oracle E-Business Suite receiving the most patches. ### Source excerpt Oracle addresses 672 CVEs in its September 2026 Critical Security Patch Update with 673 patches, including 104 critical updates. Key Takeaways The September 2026 Critical Security Patch Update (CSPU) contains fixes for 672 unique CVEs in 673 security updates 104 issues (15.5% of all patches) were assigned a critical severity rating Oracle E-Business Suite received the highest number of patches at 159, accounting for 23.6% of all patches Background On September 15, Oracle released its Critical Security Patch Update (CSPU) for September 2026. Beginning in May 2026, Oracle introduced CSPUs as a monthly release cycle that sits between the larger quarterly Critical Patch Updates (CPUs), addressing a focused set of high-severity issues on a faster cadence. This CSPU contains fixes for 672 unique CVEs in 673 security updates across 17 Oracle product families. Out of the 673 security updates published, 15.5% of patches were assigned a critical severity. High severity patches accounted for the bulk of security patches at 74.7%, followed by critical severity patches at 15.5%. This month's update includes 104 critical patches across 104 CVEs. SeverityIssues PatchedCVEsCritical104104High503503Medium5958Low77Total673672 Analysis This month's update saw the Oracle E-Business Suite product family contain the highest number of patches at 159, accounting for 23.6% of the total patches, followed by Oracle Fusion Middleware at 153 patches, which accounted for 22.7% of the total patches. A full breakdown of the patches for this CSPU can be seen in the following table, which also includes a count of vulnerabilities that can be exploited over a network without authentication. Oracle Product FamilyNumber of PatchesRemote Exploit without AuthOracle E-Business Suite15919Oracle Fusion Middleware15378Oracle Hyperion10250Oracle Siebel CRM6326Oracle Analytics508Oracle Communications3123Oracle Commerce2716Oracle Supply Chain195Oracle Virtualization191Oracle PeopleSoft164Oracle Database Server115 ## curl 8.22.0 DevFeed: [curl 8.22.0]() Original publisher: [Read original article]() Author: Daniel Stenberg Published: 2026-09-02T05:52:46Z Content type: release Language: en Sources: [Daniel Stenberg]() Topics: [cURL](), [Security](), [HTTP](), [openssl](), [API](), [TLS (Transport Layer Security)](), [Command-line interface]() Tags: [bugfixes](), [command-line](), [curl](), [curl-and-libcurl](), [cve](), [cves](), [http](), [openssl](), [release](), [security](), [tls]() ### AI overview The curl 8.22.0 release includes six changes, 302 bug fixes, and nine curl/libcurl security fixes plus one wcurl fix. It adds Apple GSS Framework support, API guards, experimental HTTP Message Signatures support, and Apple fast UDP, while blocking NTLM fallback in SPNEGO and dropping TLS-SRP support. ### Source excerpt Welcome to this new release. Get it as always from https://curl.se. If you rather want a security-patched older release branch, stay tuned for the follow-up Rock-solid curl announcement within a few days. Release presentation Numbers the 276th release6 changes70 days (total: 10,887)302 bugfixes (total: 14,489)525 commits (total: 39,608)0 new public libcurl function (total: 100)4 new ... Continue reading curl 8.22.0 -> ## \[CVE\] \[URGENT\] Squid v19.2.6 and Tentacle v20.2.4 released DevFeed: [\[CVE\] \[URGENT\] Squid v19.2.6 and Tentacle v20.2.4 released]() Original publisher: [Read original article]() Author: Patrick Donnelly Published: 2026-08-19T00:00:00Z Content type: release Language: en Sources: [Ceph Blog]() Topics: [releases](), [Authentication](), [Linux](), [client](), [monitor]() Tags: [authentication](), [blog-post](), [cve](), [cves](), [en-article](), [en-blog-post](), [errors](), [linux](), [process](), [release](), [releases](), [rest](), [rgw](), [squid](), [tentacle](), [upgrade]() ### AI overview The Ceph project released Tentacle 20.2.4 and Squid 19.2.6 as hotfixes addressing four CVEs. The article urgently recommends upgrading and explains changes to CephX key types, daemon-key rotation, authentication controls, recovery procedures, and multisite RGW request signing. ### Source excerpt The Ceph project has released Tentacle 20.2.4 and Squid 19.2.6 hotfixes for four CVEs across several components. This is the sixth backport release in the Squid series. This is the fourth backport release in the Tentacle series. We strongly recommend that all Ceph operators upgrade to one of these releases as soon as possible. Release Date ¶ August 19, 2026 Critical Upgrade Steps ¶ The fix for CVE-2025-30156 introduces a new CephX key type, aes256k. This is the first time Ceph has introduced a new key type for CephX credentials. Therefore, a new procedure exists for upgrading and rotating Ceph daemon keys as part of this CVE. Before upgrading a Ceph cluster, the operator should familiarize themselves with the procedure to upgrade CephX keys. These steps are for package-based deployments of Ceph. In other sections, the document also includes new information about key rotation procedures, monitor authentication controls, and emergency recovery procedures. Deployments using cephadm will automate the process except for client keys. You may notice that Cephadm spends more time than normal on the upgrade after updating all daemon images. This is due to a new process rotating the OSD and MDS keys. Please be patient. There are plans to improve this in the future. Deployments using Rook will also automate rotation of some client keys with some exclusions. Look to the Rook project's announcement for more details. Client and kernel upgrades are recommended to support aes256k. Note that upstream Linux kernel client support began in kernel 7.0 and has been backported to CentOS Stream 9 and 10. Check with your distribution vendor for backported key support before rotating client keys used by the kernel. As part of upgrading a Ceph cluster, six new health warnings and errors will be generated. This is normal. As part of the process to upgrade/rotate entity keys, you will address the warnings and errors as you go. These are documented beginning here. The CephX documentation has bee ## Patching Vulnerabilities Without an Upstream Fix DevFeed: [Patching Vulnerabilities Without an Upstream Fix]() Original publisher: [Read original article]() Published: 2026-08-17T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [vulnerability](), [ai security](), [chainguard](), [Automation](), [Frontier AI]() Tags: [ai-security](), [automation](), [chainguard](), [cves](), [sandbox](), [software](), [vulnerability]() ### AI overview Chainguard describes how its Athena vulnerability clearinghouse addresses exploitable vulnerabilities when no upstream fix exists. The article explains that generating an AI-written patch is straightforward, while proving the patch is correct and safe requires extensive engineering and validation inside a microVM sandbox. ### Source excerpt Generating an AI security patch is easy. Trusting it is hard. Learn how Chainguard proves zero-day fixes are safe before they ship. ## Why zero CVEs matters in mobile airgapped deployments DevFeed: [Why zero CVEs matters in mobile airgapped deployments]() Original publisher: [Read original article]() Published: 2026-07-28T00:00:00Z Content type: opinion Language: en Sources: [Chainguard: Unchained]() Topics: [Containers](), [Vulnerabilities](), [Security](), [chainguard containers](), [chainguard]() Tags: [chainguard](), [chainguard-containers](), [containers](), [cves](), [security](), [vulnerabilities]() ### AI overview The article explains why disconnected mobile and air-gapped systems become increasingly exposed as vulnerabilities accumulate while patching and live feeds are unavailable. It argues that starting with low-CVE container images and refreshing them before departure can reduce the vulnerability backlog, citing Chainguard Containers' stated CVE reduction and daily rebuild practices. ### Source excerpt Disconnected systems can't patch. Learn how minimal, zero-CVE containers help reduce vulnerability accumulation in air-gapped environments. ## What are CVEs, and how to read them DevFeed: [What are CVEs, and how to read them]() Original publisher: [Read original article]() Author: Neil Carpenter Published: 2026-07-23T05:40:01Z Content type: tutorial Language: en Sources: [Platform Engineering Blog]() Topics: [Vulnerabilities](), [Cybersecurity](), [Software](), [configuration]() Tags: [cves](), [cybersecurity](), [how-to](), [learn](), [security](), [software](), [vulnerabilities]() ### AI overview This tutorial demystifies Common Vulnerabilities & Exposures (CVE) records and explains how practitioners can evaluate and respond to software vulnerabilities. It covers CVE identifiers, record enrichment, CVSS severity scores, and CPE applicability information, with discussion of the jargon and assumptions involved. ### Source excerpt A CVE record is dense with jargon and hidden assumptions. Demystify the Common Vulnerabilities & Exposures (CVE) system and learn how to read and respond effectively to new vulnerabilities, including understanding CVSS severity scores, CPEs for applicability, and CWEs for root cause analysis ## The true cost of Kubernetes release support for Platform Engineers DevFeed: [The true cost of Kubernetes release support for Platform Engineers]() Original publisher: [Read original article]() Author: Bruce Gain Published: 2026-07-23T05:40:01Z Content type: comparison Language: en Sources: [Platform Engineering Blog]() Topics: [Kubernetes](), [Platform Engineering](), [Cloud](), [Amazon Web Services](), [Amazon EKS](), [Azure](), [rancher]() Tags: [amazon-eks](), [aws](), [azure](), [cloud](), [comparison](), [cost](), [cves](), [kubernetes](), [operational](), [platform](), [platform-engineering](), [private-cloud](), [red-hat](), [releases](), [security](), [support](), [testing](), [upgrades](), [vmware-cloud-foundation](), [vulnerabilities]() ### AI overview This article compares the operational and financial trade-offs of Kubernetes release support models. It explains that the CNCF's 14-month support window requires frequent upgrades, creating testing, coordination, maintenance, and service-disruption risks. Hyperscalers such as Amazon EKS, Google GKE, and Azure AKS offer paid extended support, while VMware Cloud Foundation provides 24 months of standard support without incremental fees and Red Hat OpenShift offers a 36-month support window. ### Source excerpt Compare the true cost and operational trade-offs of Kubernetes extended support fees from hyperscalers (AWS, GCP, Azure) versus the longer, predictable maintenance cycles of VMware VCF and other enterprise distributions. ## Hydrate, Hack, Repeat: Security Summer Camp 2026 DevFeed: [Hydrate, Hack, Repeat: Security Summer Camp 2026]() Original publisher: [Read original article]() Author: jgamblin Published: 2026-07-22T21:34:54Z Content type: opinion Language: en Sources: [Jerry Gamblin]() Topics: [Security](), [vulnerability management](), [vulnerability](), [data](), [Artificial Intelligence]() Tags: [2026](), [ai](), [black-hat](), [bsides](), [cisa](), [con](), [cves](), [data](), [kev-catalog](), [management](), [models](), [research](), [security](), [talks](), [uncategorized](), [vulnerability](), [vulnerability-management]() ### AI overview A personal guide to the author's 2026 security conference schedule, new role as Head of Research at Empirical Security, and recommended CVE and vulnerability talks. It argues that effective vulnerability management requires granular, transparent, accurate data, citing the growth in CVEs and the limited share listed in CISA KEV. ### Source excerpt My schedule, a new role at Empirical Security, and the CVE and vulnerability talks worth your time. It is almost the first week of August, which means it is time to point myself at the desert one more time. BSides Las Vegas, Black Hat, and DEF CON all land back to back, and for me ... Read more ## CVE Mid-Year 2026 Check-In: Volume Vertical, Exploitation Rare DevFeed: [CVE Mid-Year 2026 Check-In: Volume Vertical, Exploitation Rare]() Original publisher: [Read original article]() Author: jgamblin Published: 2026-07-01T15:47:10Z Content type: article Language: en Sources: [Jerry Gamblin]() Topics: [Vulnerabilities](), [Security](), [Statistics](), [cisa]() Tags: [2026](), [comparison](), [cve](), [cves](), [report](), [security](), [statistics](), [uncategorized](), [vulnerabilities]() ### AI overview This mid-year review finds that 35,364 CVEs were published in the first half of 2026, up 49.5% from the same period in 2025, while only 85 had entered CISA's KEV list. The article argues that the main challenge is distinguishing exploitable vulnerabilities from the rapidly growing volume of disclosures. ### Source excerpt We are halfway through 2026, so it is time for the mid-year CVE check-in. The short version: the volume curve has gone vertical while exploitation has not. This review covers everything published in the first half of 2026 (Jan 1 - Jun 30, 2026), the volume, the severity, what is actually being exploited, and who ... Read more ## The State of Trusted Open Source: June 2026 DevFeed: [The State of Trusted Open Source: June 2026]() Original publisher: [Read original article]() Published: 2026-06-30T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [Open Source](), [supply-chain-security](), [vulnerability](), [Artificial Intelligence](), [Security]() Tags: [2026](), [ai](), [chainguard](), [chainguard-containers](), [chainguard-libraries](), [cve](), [cve-data](), [cves](), [data](), [dependency](), [java](), [javascript](), [nginx](), [node](), [open-source](), [python](), [report](), [security](), [software](), [software-supply-chain](), [software-supply-chain-security](), [state-of-trusted-open-source](), [trends](), [vulnerability]() ### AI overview Chainguard's June 2026 report analyzes vulnerability data from more than 2,400 container image projects and 18,016 vulnerability instances observed from March through May 2026. It reports 886 distinct CVEs, with 63.1% of observed instances classified as high severity, and examines how AI-assisted development and security research are affecting software supply-chain risk. ### Source excerpt AI is accelerating vulnerability discovery. Explore the latest trusted open source trends, dependency risks, and CVE insights from Chainguard's report. ## Fewer CVEs, more accurate findings: Wiz now scans Chainguard Libraries for Python and Java DevFeed: [Fewer CVEs, more accurate findings: Wiz now scans Chainguard Libraries for Python and Java]() Original publisher: [Read original article]() Published: 2026-06-25T00:00:00Z Content type: release Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard](), [chainguard libraries](), [chainguard libraries for python](), [Java](), [supply-chain-security](), [Security]() Tags: [chainguard](), [chainguard-libraries](), [chainguard-libraries-for-java](), [chainguard-libraries-for-python](), [cves](), [dependencies](), [java](), [provenance](), [python](), [security](), [software-supply-chain](), [supply-chain](), [wiz](), [wiz-chainguard-libraries](), [wiz-chainguard-scanner]() ### AI overview Wiz now scans Chainguard Libraries for Python and Java. The partnership combines source-built dependencies and backported fixes with Wiz's risk context and visibility, helping organizations assess vulnerabilities, prioritize remediation, and verify artifact provenance. ### Source excerpt Wiz now scans Chainguard Libraries for Python and Java, combining trusted, source-built dependencies with risk-based visibility and remediation. ## Harness May 2026 Product Updates: 60+ New Features DevFeed: [Harness May 2026 Product Updates: 60+ New Features]() Original publisher: [Read original article]() Author: Chinmay Gaikwad Published: 2026-06-03T00:00:00Z Content type: article Language: en Sources: [Harness Blog]() Topics: [MCP](), [MCP Server](), [Development](), [Artificial Intelligence](), [ai-coding](), [Security](), [Claude]() Tags: [2026](), [agentic](), [ai](), [ai-coding](), [ai-infrastructure](), [api](), [claude](), [claude-code](), [coding-assistant](), [connectors](), [cves](), [development](), [features](), [infrastructure](), [integration](), [mcp](), [mcp-server](), [product-updates](), [security](), [updates]() ### AI overview Harness reports more than 60 product updates shipped in May 2026 across AI-native development, software delivery, security, cost management, and engineering insights. Highlights include AI cost tracking, AI adoption metrics, Claude connector access, and expanded MCP Server capabilities. ### Source excerpt See 60+ Harness updates from May 2026 across AI-native development, software delivery, security, artifact management, cost visibility, and engineering insights. | Blog ## Building for the AI era: Chainguard partners with Endor Labs DevFeed: [Building for the AI era: Chainguard partners with Endor Labs]() Original publisher: [Read original article]() Published: 2026-05-19T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [supply-chain-security](), [Application Security](), [Artificial Intelligence](), [AI-assisted coding](), [chainguard containers](), [Containers](), [Library](), [Agent Skill](), [CI/CD]() Tags: [agent](), [ai](), [ai-coding-agents](), [application-security](), [chainguard](), [chainguard-containers](), [chainguard-libraries](), [containers](), [cves](), [endor](), [endor-labs](), [observability](), [provenance](), [sboms](), [software-supply-chain](), [vulnerabilities]() ### AI overview Chainguard partners with Endor Labs to help teams building with AI coding agents secure the software supply chain. Chainguard provides source-built artifacts, daily rebuilds, signed SBOMs, and SLSA Level 3 provenance, while Endor Labs analyzes application context to identify vulnerabilities that are genuinely reachable and exploitable. ### Source excerpt Chainguard and Endor Labs help teams build securely at AI speed with source-built artifacts, exploitability analysis, and fewer vulnerabilities to triage. ## Kubernetes User Namespaces Improve Pod Isolation but Do Not Isolate the Shared Kernel DevFeed: [Kubernetes User Namespaces Improve Pod Isolation but Do Not Isolate the Shared Kernel]() Original publisher: [Read original article]() Author: Kaylin Trychon Published: 2026-05-06T14:50:05Z Content type: opinion Language: en Sources: [Kubernetes Overview, News and Trends | The New Stack]() Topics: [Kubernetes](), [Security](), [Kernel](), [Cloud Native Ecosystem](), [Containers]() Tags: [cloud-native](), [cloud-native-ecosystem](), [containers](), [cves](), [edera](), [kubernetes](), [post-contributed](), [security](), [sponsor-edera](), [sponsored-post-contributed]() ### AI overview Kubernetes user namespaces can reduce the impact of some container escapes by remapping pod root identities to unprivileged host identities. The article argues that this improves isolation but does not address the security limitations of a shared kernel. ### Source excerpt Kubernetes shipped a long-awaited security feature last week: user namespace support for pods. It may sound like an obscure feature The post Kubernetes finally lands user namespace support, but shared kernel problem remains appeared first on The New Stack. ## Building the business case for a secure open source supply chain DevFeed: [Building the business case for a secure open source supply chain]() Original publisher: [Read original article]() Published: 2026-05-05T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [Open Source](), [open-source-security](), [vulnerability management](), [cloud-infrastructure](), [CI/CD](), [distributed-systems](), [container images](), [engineering-culture]() Tags: [chainguard-assemble](), [chainguard-containers](), [chainguard-customers](), [cloud-infrastructure](), [cloud-native](), [compliance](), [container-images](), [continuous-delivery](), [cves](), [dependencies](), [distributed-systems](), [kyndryl](), [kyndryl-open-source](), [open-source](), [productivity](), [resilience](), [secure-open-source](), [software-supply-chain-security](), [supply-chain](), [vulnerabilities]() ### AI overview The article explains how organizations can build a business case for a secure open source supply chain. It describes a shift from framing open source security solely around CVEs, scanner results, and patching toward presenting trusted open source as a driver of productivity, resilience, and delivery speed. It also explains why traditional vulnerability management struggles with continuous delivery, distributed systems, frequently rebuilt container images, changing dependencies, and global cloud infrastructure. ### Source excerpt Learn how Kyndryl reframed open source security as a business driver -- reducing risk, lowering costs, and accelerating developer productivity. ## Going beyond CVEs: Chainguard's one day KEV SLA DevFeed: [Going beyond CVEs: Chainguard's one day KEV SLA]() Original publisher: [Read original article]() Published: 2026-04-28T00:00:00Z Content type: release Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard](), [Vulnerabilities](), [chainguard containers](), [Security](), [cisa]() Tags: [chainguard](), [chainguard-containers](), [chainguard-cves](), [chainguard-images](), [chainguard-kevs](), [cisa](), [containers](), [cves](), [exploited-vulnerabilities](), [kevs](), [known-exploitable-vulnerabilities](), [security]() ### AI overview Chainguard announces a one-calendar-day SLA for remediating CVEs added to the CISA Known Exploited Vulnerabilities Catalog when they affect Chainguard container images. The article explains the SLA's relationship to exploited-vulnerability prioritization and Chainguard's continuous remediation processes. ### Source excerpt Chainguard introduces a 1-day KEV SLA, ensuring exploited vulnerabilities are fixed fast--aligned with how security teams prioritize real-world threats. ## AI is finding vulnerabilities faster than anyone can patch them. Now what? DevFeed: [AI is finding vulnerabilities faster than anyone can patch them. Now what?]() Original publisher: [Read original article]() Published: 2026-04-10T00:00:00Z Content type: opinion Language: en Sources: [Chainguard: Unchained]() Topics: [Vulnerabilities](), [Artificial Intelligence](), [supply-chain-security](), [Claude](), [anthropic](), [Maintainers](), [Open Source](), [Exploit](), [Operating system](), [browser]() Tags: [ai](), [anthropic](), [attacks](), [chainguard-for-ai](), [claude](), [claude-mythos-preview](), [cves](), [exploit](), [maintainers](), [open-source](), [project-glasswing](), [security](), [software-supply-chain](), [software-supply-chain-security](), [supply-chain-attacks](), [vulnerabilities]() ### AI overview The article argues that AI systems such as Claude Mythos Preview are discovering zero-day vulnerabilities faster than organizations and open-source maintainers can patch them. It describes the resulting risks for software supply chains, including faster exploitation, uneven vendor response, and increased pressure on maintainers, while presenting verifiable-source, secure-by-default artifacts as a defensive approach. ### Source excerpt Project Glasswing and Claude Mythos Preview reveal a surge in zero-days. Learn why reactive patching fails and how secure-by-default supply chains keep you safe. ## SecDB is the past, OSV is the future DevFeed: [SecDB is the past, OSV is the future]() Original publisher: [Read original article]() Published: 2026-04-09T00:00:00Z Content type: release Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard](), [chainguard containers](), [vulnerability](), [Vulnerabilities](), [chainguard packages](), [Security]() Tags: [chainguard](), [chainguard-containers](), [chainguard-scanners](), [cves](), [deprecated](), [open-source-vulnerabilities](), [osv](), [secdb](), [security](), [vulnerability](), [vulnerability-data](), [vulnerability-scanning]() ### AI overview Chainguard is deprecating its SecDB vulnerability feed and plans to sunset it at the end of 2026. The company is moving toward the OSV schema because it supports more precise vulnerability data, including unfixed vulnerabilities and component-level advisory details. ### Source excerpt Chainguard is deprecating SecDB in favor of OSV, delivering more accurate, granular vulnerability data and better visibility for modern software supply chains. ## Protect your AI workloads from supply chain attacks DevFeed: [Protect your AI workloads from supply chain attacks]() Original publisher: [Read original article]() Published: 2026-01-30T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [Artificial Intelligence](), [Containers](), [chainguard](), [Vulnerabilities](), [AI Strategy](), [Open Source](), [Security](), [PyTorch](), [Tensorflow](), [MLOps]() Tags: [ai](), [ai-containers](), [chainguard](), [chainguard-containers](), [chainguard-for-ai](), [chainguard-libraries](), [containers](), [cudnn](), [cves](), [data-processing](), [deployment](), [kserve](), [legacy](), [libraries](), [mlops](), [nemo](), [ollama](), [python](), [pytorch](), [security](), [security-vulnerabilities](), [supply-chain](), [supply-chain-attacks](), [zero-cve-containers]() ### AI overview The article discusses security and operational challenges in AI/ML workloads, including complex dependencies, bloated artifacts, infrastructure sprawl, and unremediated CVEs. It presents Chainguard Containers' minimal images for AI workloads as a way to reduce attack surface, storage needs, and deployment overhead, and cites a 50 MB gpu-operator image compared with a 170 MB upstream equivalent. ### Source excerpt Chainguard secures AI adoption with minimal, zero-CVE containers and source-built libraries that prevent supply chain malware while keeping developers fast. ## How Chainguard OS Uses Automated Package Garbage Collection to Reduce Security Risk DevFeed: [How Chainguard OS Uses Automated Package Garbage Collection to Reduce Security Risk]() Original publisher: [Read original article]() Published: 2025-12-05T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard os](), [open-source-security](), [Security](), [APK](), [container images](), [Process]() Tags: [apk](), [automated](), [chainguard-containers](), [chainguard-libraries](), [chainguard-operating-system](), [chainguard-os](), [chainguard-wolfi](), [container-images](), [cves](), [dependency](), [security](), [wolfi]() ### AI overview The article explains how Chainguard automates garbage collection for Chainguard OS and Wolfi APK repositories. It describes filtering older packages and checking dependencies and image usage before removal to keep repositories current and reduce potential attack surface while preserving image customization workflows. ### Source excerpt Learn how we keep Chainguard OS and Wolfi lean and secure with automated package garbage collection that cuts attack surface while preserving reproducibility. ## Three Ways to Make Your SDLC Secure-by-Default DevFeed: [Three Ways to Make Your SDLC Secure-by-Default]() Original publisher: [Read original article]() Published: 2025-10-20T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [sdlc](), [open-source-security](), [supply-chain-security](), [Open Source](), [chainguard]() Tags: [chainguard](), [chainguard-containers](), [chainguard-images](), [chainguard-security](), [ci-cd](), [cloud-native](), [cves](), [open-source-software](), [sdlc](), [secure-by-default](), [software-supply-chain]() ### AI overview This article presents secure-by-default software development lifecycle practices. It recommends embedding security throughout development, standardizing trusted foundations, securing dependencies and base images, and integrating security into developer tools, CI/CD workflows, and runtime artifacts. ### Source excerpt Build secure software faster with Chainguard. Learn how secure-by-default SDLC practices eliminate CVEs, automate compliance, and embed trust from code to cloud. ## Simplify Continuous Compliance: How to Stay Audit-Ready and Ship Software Faster DevFeed: [Simplify Continuous Compliance: How to Stay Audit-Ready and Ship Software Faster]() Original publisher: [Read original article]() Published: 2025-10-14T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [Application Security](), [open-source-security](), [Open Source](), [Software](), [chainguard]() Tags: [chainguard](), [chainguard-containers](), [chainguard-security](), [cmmc](), [compliance](), [cves](), [fedramp](), [iso-27001](), [open-source-software](), [pci-dss](), [security](), [soc-2](), [stateramp]() ### AI overview This article explains how organizations can treat software compliance as a continuous practice rather than a periodic audit exercise. It describes how open-source components, CVE remediation, provenance, SBOM coverage, and audit evidence affect platform engineering, application security, development velocity, and regulated-market access, while presenting Chainguard as a solution provider. ### Source excerpt Turn compliance into a growth driver with Chainguard. Eliminate CVEs, stay audit-ready, and meet FedRAMP, SOC 2, and ISO 27001 with secure images. ## Meeting the Zero-CVE Mandate: How Chainguard Helps Businesses Ship Secure Software That Customers Trust DevFeed: [Meeting the Zero-CVE Mandate: How Chainguard Helps Businesses Ship Secure Software That Customers Trust]() Original publisher: [Read original article]() Published: 2025-10-06T00:00:00Z Content type: opinion Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard](), [supply-chain-security](), [Containers](), [software bill of materials](), [Security]() Tags: [chainguard](), [chainguard-containers](), [chainguard-custom-assembly](), [chainguard-images](), [containers](), [cves](), [provenance](), [sboms](), [secure-software](), [security](), [software-supply-chain-security](), [zero-cves]() ### AI overview The article explains how Chainguard helps businesses meet stricter software security requirements for self-hosted, cloud, packaged-agent, and embedded software. It focuses on zero known CVEs at delivery, verifiable SBOMs, provenance attestations, compatibility with security tooling, and the challenges of open source dependencies and container images. ### Source excerpt Chainguard's zero-CVE containers come with broad compatibility, custom assembly, verifiable provenance and SBOMs, and more to help you ship secure software. ## Jerry Gamblin Announces Two CVE Ecosystem Talks at BSides Las Vegas and DEF CON DevFeed: [Jerry Gamblin Announces Two CVE Ecosystem Talks at BSides Las Vegas and DEF CON]() Original publisher: [Read original article]() Author: jgamblin Published: 2025-07-30T18:05:00Z Content type: opinion Language: en Sources: [Jerry Gamblin]() Topics: [Security](), [vulnerability management](), [Open Source]() Tags: [black-hat](), [bsides](), [cves](), [infosec](), [management](), [open-source](), [security](), [uncategorized]() ### AI overview Jerry Gamblin announces that he will give two talks on the CVE ecosystem during Security Summer Camp, including appearances at BSides Las Vegas and the AppSec Village at DEF CON. ### Source excerpt It's that time of year again! The first week of August means my annual trip to the desert for "Security Summer Camp"--the whirlwind of BSides Las Vegas, Black Hat, and DEF CON. It's always an exhausting but amazing week, and I can't wait to dive in, catch up with everyone, and talk about what I've ... Read more [Next page]()