Newsdesk
Engineering
Data & AI
Industries
Enterprise Systems
Go-to-Market
Longform
DesignIndiaAll stories

Open Source

02 October 2026

AI Agent Exploits Zammad Zero-Days as Supply Chain Risks Resurface and EU CRA Reporting Commences

One week of Open Source, 7 stories, as published.

Security

[$] Coping with the onslaught of kernel security bugs

Greg Kroah-Hartman discusses how the Linux kernel security team is managing a massive influx of security bug reports generated by LLMs. He shares strategies for handling this deluge without overwhelming the project's maintainers.

Why it matters — The ease of using LLMs to find bugs has created a high-volume triage burden for open-source maintainers, requiring new strategies to filter noise from actionable security issues.

LWN · 02 October 2026 · Read the original →

Governance

[$] Comparing Chromium development at Google and Igalia

Chromium developer Sharon Yang compares the development processes and operational differences of working on the browser engine at Google versus at the open-source consultancy Igalia. The post highlights how different organizational models affect contributions to the same codebase.

Why it matters — Understanding how different corporate contributors operate helps engineering leaders navigate the governance and development velocity of major shared open-source projects.

LWN · 02 October 2026 · Read the original →

Reading

[$] The kernel from a PostgreSQL point of view

PostgreSQL developer Andres Freund details his experiences working with and around Linux kernel features to optimize database performance. He discusses the friction and collaboration opportunities between the database and operating system development communities.

Why it matters — Downstream projects must actively engage with upstream platform maintainers to resolve deep architectural and performance mismatches rather than just building workarounds.

LWN · 02 October 2026 · Read the original →

Security

CISA Flags Linux Kernel Vulnerabilities

CISA added three Linux kernel flaws (CVE-2025-39682, CVE-2026-53266, CVE-2025-39964) to its Known Exploited Vulnerabilities catalog on September 19, 2026, with Red Hat confirming active exploitation. These critical and high-severity bugs, already patched, could lead to denial-of-service, privilege escalation, or data corruption. Federal agencies were given a three-day deadline to patch by September 21, 2026.

Why it matters — Organizations using affected Linux kernel versions must immediately apply patches to prevent potential remote code execution, privilege escalation, or denial-of-service attacks.

The Hacker News · 02 October 2026 · Read the original →

Regulation

EU CRA Reporting Begins for Manufacturers

The EU Cyber Resilience Act's reporting obligations for manufacturers of products with digital elements went live on September 11, 2026, requiring them to report actively exploited vulnerabilities and severe incidents. A key clarification from the European Commission and ENISA confirms that open-source software stewards have a later compliance deadline of December 11, 2027.

Why it matters — Manufacturers must now implement processes for rapid vulnerability and incident reporting to ENISA, while open-source stewards gain an additional year to prepare for their obligations.

openssf.org · 02 October 2026 · Read the original →

Security

AI Agent Exploits Zammad Zero-Days

Two zero-day vulnerabilities (CVE-2026-102489 and CVE-2026-102490) in the open-source Zammad ticketing system were chained by an autonomous AI agent to breach the Dutch Institute for Vulnerability Disclosure (DIVD). This allowed session hijacking, remote code execution, and privilege escalation to root, leading to data exfiltration.

Why it matters — Organizations using Zammad must immediately upgrade to version 7 or take instances offline to prevent AI-driven attacks that can lead to root compromise and data theft.

bleepingcomputer.com · 02 October 2026 · Read the original →

Supply Chain

Re-enabled GitHub Actions Pose Risk

Two GitHub Actions from the `actions-cool` organization, previously disabled in May 2026 due to the Mini Shai-Hulud campaign, were re-enabled on September 16, 2026, without their malicious code being cleaned up. This reactivated credential-stealing malware in CI/CD workflows referencing these actions by version tag, exposing thousands of downstream projects.

Why it matters — Developers must pin GitHub Actions to specific commit SHAs, not mutable tags, and audit workflows to prevent re-enabled compromised actions from executing malicious payloads.

thehackernews.com · 02 October 2026 · Read the original →

The distinction between a feature set and a threat model continues to blur.

7 stories, every Friday

Published here every week. Follow by RSS to get it as it lands.

← Previous issue Next issue →