Skip to content
Edition of Thursday, November 19, 2026
Daily CISO

The five-minute briefing for security leaders.

Guide

Open Source Security News: 2026's Package Compromises, Exploited Projects and Advisory Counts

The 2026 open source attacks that mattered: TeamPCP, TanStack, the npm worm waves and LiteLLM, plus the open source flaws CISA lists as exploited and GitHub's counts.

Published November 17, 2026Updated Daily CISO Desk16 sources

The biggest open source security story of 2026 is the attack on how packages get published. Attackers took over release pipelines and maintainer accounts at Trivy, Axios, TanStack, Red Hat's npm namespace, AsyncAPI and LiteLLM, and shipped malware under real project names. CISA now lists four such package compromises as actively exploited. Beside them, its catalog added nine Linux kernel flaws in 2026, and PHP and OpenSSH entries followed on October 26 and November 9.

The counts on this page are this site's own. We read every entry CISA added to its Known Exploited Vulnerabilities (KEV) catalog in 2026 and every advisory the GitHub Advisory Database published from January 1 to November 16. The methods note at the end sets out the rules.

Key facts

  • 12,597 reviewed advisories in the GitHub Advisory Database published January 1 to November 16, 2026. 1,356 are rated critical and 4,962 high.
  • 3,768 of them affect npm packages, 2,690 Python (pip) packages and 2,295 Go modules.
  • 2,965 malware advisories published from October 1 to November 16, 2026, 1,737 of them in November.
  • 297 entries added to CISA's KEV catalog in 2026 (version 2026.11.13). 4 are compromised open source packages or tools: eslint-config-prettier, Trivy, TanStack and Nx Console.
  • 9 Linux kernel entries added to KEV in 2026, the most for any open source project. WordPress, Langflow and GitLab have four each.
  • Newest: OpenSSH (CVE-2026-123158, added November 9) and UnrealIRCd (CVE-2026-114713, added November 13).

Which open source packages were compromised in 2026?

Six incidents set the pattern. In each one the code came from the real project, under its real name, not from a lookalike package.

Date (2026)ProjectRegistryWhat happened
March 19 to 27Trivy, then LiteLLM and Telnyx (TeamPCP campaign)GitHub Actions, Docker Hub, PyPI, npmStolen credentials used to publish malicious releases and rewrite Action tags
March 30AxiosnpmLead maintainer's npm account hijacked; versions 1.14.1 and 0.30.4 carried a remote access trojan
May 11TanStack (42 packages)npm84 malicious versions published through the project's own trusted-publisher pipeline
May 18Nx Console 18.95.0VS Code Marketplace, OpenVSXMalicious editor extension live for about 18 minutes on Microsoft's marketplace
June 1 to August 4@redhat-cloud-services, AsyncAPI, then keyv and cacheable (ChainDrop)npmShai-Hulud worm descendants spread through CI pipelines and maintainer accounts
October 21LiteLLM 1.107.0PyPI, Docker Hub, GHCRRelease pipeline used to publish a poisoned build for about two hours

TeamPCP: Trivy, LiteLLM and Telnyx

The year's longest campaign began with Trivy, Aqua Security's open source vulnerability scanner. Aqua's advisory (GHSA-69fq-xp46-6x23, CVE-2026-33634) says an attacker with compromised credentials published a malicious Trivy v0.69.4 on March 19 and followed with malicious v0.69.5 and v0.69.6 images on Docker Hub on March 22.

Datadog Security Labs traced the same campaign, which researchers call TeamPCP, onward to npm, to Checkmarx's KICS tooling, and then to PyPI. Two LiteLLM releases (1.82.7 and 1.82.8) carried malicious code on March 24, and two releases of the telnyx package (4.87.1 and 4.87.2) were backdoored on March 27.

Datadog's advice was to treat any host or build job that installed those versions as a full credential exposure, not as a package to remove.

CISA added Trivy to its catalog on March 26, 2026, describing the risk in terms of everything a CI/CD environment holds: tokens, SSH keys, cloud credentials and database passwords. The full Trivy timeline, with the exposure window for each artifact, is in this site's Kubernetes Security News guide, and the KEV entry sits on Aqua Security's vendor page.

Axios

Axios is a JavaScript HTTP client with over 100 million weekly npm downloads, according to TrendAI's analysis. On March 30, 2026, an attacker hijacked the lead maintainer's npm account and published versions 1.14.1 and 0.30.4. Both pulled in a new dependency, plain-crypto-js@4.2.1, whose install script dropped a remote access trojan on macOS, Windows and Linux.

Scanners flagged the dependency within minutes and npm removed the versions soon after. The case shows why a lockfile matters: a project that pinned an earlier Axios version never fetched the bad one.

TanStack and Nx Console

Unit 42 notes that every earlier Shai-Hulud wave began with a stolen or phished credential, and the TanStack attack needed neither. TanStack's advisory says 84 malicious versions across 42 @tanstack packages were published on May 11, between about 19:20 and 19:26 UTC, through the project's legitimate GitHub Actions trusted-publisher binding.

The attacker chained a pull_request_target workflow that ran a fork's code, cache poisoning across the fork and base repository, and extraction of the publishing token from the runner's memory. The payload went after cloud metadata services, Kubernetes service-account tokens, HashiCorp Vault tokens, npm and GitHub tokens, and SSH keys.

Unit 42 adds a detail that matters to anyone relying on signed builds. The TanStack packages carried valid SLSA Build Level 3 provenance, because the real pipeline did build them.

Provenance tells you which pipeline built a package. It does not tell you whether that pipeline had been tampered with.

A week later Nx Console, a VS Code extension, was hit; its advisory links the attack to the TanStack compromise and a GitHub CLI token. It says the malicious version 18.95.0 was published at 12:30 UTC and removed at 12:48 UTC from Microsoft's marketplace, and stayed on OpenVSX for about 36 minutes.

CISA added both TanStack (CVE-2026-45321) and Nx Console (CVE-2026-48027) to KEV on May 27, 2026, and marked both as known to be used in ransomware campaigns.

The Shai-Hulud worm waves

Shai-Hulud is the name researchers gave to self-spreading npm malware that steals a developer's tokens and uses them to publish infected versions of that developer's other packages. Unit 42's running record of the 2026 waves shows how fast it moved:

  • May 19: the npm account of a maintainer of the @antv charting libraries was taken over. In about an hour, 639 malicious versions went out across 323 packages, the largest single-hour count of any wave in Unit 42's record.
  • June 1: at least 32 packages under @redhat-cloud-services were compromised through a Red Hat employee's GitHub account, again with valid SLSA provenance.
  • July 14: attackers pushed commits to unprotected pre-release branches of four AsyncAPI repositories, which triggered the release workflows and published five trojanized packages.

On August 4, a variant Datadog calls ChainDrop compromised hundreds of npm packages, some with over 150 million weekly downloads. Singapore's Cyber Security Agency put the scale at over 1,300 package versions with a combined 2 billion monthly downloads, including the keyv, cacheable, flat-cache and file-entry-cache caching libraries.

The agency told organizations using Node.js to review their dependencies and treat credentials on affected systems as potentially compromised. Red Hat's KEV entries are on its vendor page.

LiteLLM, again, in October

LiteLLM is a widely used Python proxy for large language model APIs, and it was hit a second time. A malicious litellm 1.107.0 was live on PyPI for about two hours on October 21 (11:39 to 13:23 UTC), and four Docker image tags pointed at a compromised image until 14:20 UTC.

LiteLLM's own attack-chain record, which it calls the canonical account, traces the start to May 27. That day an administrative key for an internal service was committed to a public repository, deleted three hours later, and never revoked.

On October 10 the attacker used that key to reach a GitHub CLI token belonging to an organization owner, then collected two maintainers' tokens from CI secrets. A release safeguard that normally needed a device-locked approval account had been relaxed that week to allow faster bugfix releases. The record's own lesson is about key rotation: a key that might have leaked should be treated as leaked.

Which open source projects does CISA list as exploited in 2026?

CISA added 297 entries to KEV between January 1 and November 13, 2026. Many are in open source software. Four are not ordinary bugs but compromised releases, filed under the weakness CISA calls embedded malicious code:

AddedCVEProjectKEV ransomware flag
Jan 22CVE-2025-54313eslint-config-prettier (npm)Unknown
Mar 26CVE-2026-33634TrivyUnknown
May 27CVE-2026-45321TanStackKnown
May 27CVE-2026-48027Nx ConsoleKnown

The rest are flaws in widely deployed open source code:

  • Linux kernel: 9 entries. Six are 2025 or 2026 CVEs and three are older flaws CISA has now seen used, the oldest CVE-2018-14634. The latest, CVE-2026-46300, was added on October 28.
  • WordPress core: 4 entries, including a chained SQL injection pair added on July 21 and a race condition during upgrades added on November 3. GitLab has four too, on its vendor page.
  • AI, notebook and workflow tools: 13 entries. Langflow has four, LiteLLM three, and Marimo, MLflow, Ray, GPUStack, n8n and Kestra one each. The newest, GPUStack's CVE-2026-102895, allows unauthenticated admin access.
  • PHP: 2 entries. CISA's alert says the pair, CVE-2026-109618 and CVE-2026-109619 ("php2shell"), allow unauthenticated remote code execution in every PHP installation serving web requests.

CISA added both to KEV on October 26 with an October 29 deadline, and told organizations still on PHP 8.1 or earlier to take those systems offline until patched.

  • OpenSSH: 1 entry. CVE-2026-123158, added November 9 with a November 12 deadline, is an authentication bypass in OpenSSH on Linux. Alpine Linux's advisory of November 5 describes a password bypass that takes one connection, and says updating the package or disabling password logins closes it.

Artifact tools are on the list as well. JFrog Artifactory has four 2026 entries, three of them added in September; they are on JFrog's vendor page. The whole catalog, newest first, is on this site's KEV tracker, and the entries with the shortest deadlines are on the must-patch window.

How many open source advisories were published in 2026?

The GitHub Advisory Database is the largest free record of vulnerabilities in open source packages. Its reviewed advisories, the ones GitHub's curators have checked, numbered 12,597 from January 1 to November 16, 2026.

EcosystemReviewed advisories, 2026CriticalHigh
npm3,7684291,508
pip (Python)2,6902961,139
Go2,295286879
Composer (PHP)1,510122559
Maven (Java)1,062142432
Rust (crates.io)55453176
NuGet (.NET)46221191
RubyGems2441377
Erlang82543
GitHub Actions2683

The monthly count peaked in the spring: 1,640 in March, 1,585 in April, 1,705 in May and 1,651 in June, against 494 in January. October had 1,212.

GitHub also publishes malware advisories, one per malicious package version, and that feed changed shape in September 2026. The OpenSSF said on November 9 that GitHub had integrated the OpenSSF Malicious Packages data into its Advisory Database, extending malware alerts beyond npm to PyPI, Maven, RubyGems, NuGet, Go, crates.io and Composer.

The feed is not steady: it published 37,035 malware advisories from September 10 to 30 alone, then 1,228 in October. A year total would mislead, so the figure here is the recent one: 2,965 malware advisories from October 1 to November 16, 1,737 of them in the first 16 days of November.

What changed for open source maintainers in 2026?

Two things changed in 2026. Discovery got faster, and maintainers are releasing more often to keep up. The OpenSSH team wrote in its November 5 release notes that it has received a large number of security bug reports, many found by AI models. It added that bugs found by AI tools were then found again by other researchers, so it will ship fixes in more frequent releases instead of batching them.

The OpenSSF's November 9 announcement made the same point about shrinking windows between discovery and attack, and pointed to reporting deadlines under the EU Cyber Resilience Act. It released a free guide on finding and fixing vulnerabilities with AI and announced a Secure AI Associate certification for December 2026.

What should a security team do with this?

  • Pin and lock dependencies. Every compromise above reached builds that pulled the newest version or a moving tag. Lockfiles, digests and commit-pinned GitHub Actions kept other teams out.
  • Rotate after exposure, not only after confirmation. LiteLLM and Datadog both say an environment that installed a bad version should be treated as fully exposed. Rotate cloud keys, npm and GitHub tokens, and SSH keys it could reach.
  • Audit CI workflows. Check pull_request_target workflows, shared caches between forks and the base repository, and unprotected release branches. Those three gaps let attackers into TanStack and AsyncAPI.
  • Scope publishing tokens. Prefer short-lived, repository-scoped tokens over owner-level CLI tokens. Revoke any key that was ever committed.
  • Patch the exploited list first. PHP, OpenSSH, the Linux kernel and WordPress are in the 2026 KEV additions. Start with what CISA lists, then work through the rest by severity.
  • Keep an inventory. CISA's PHP alert warns that PHP is often inside other software. A software bill of materials is how you find it.

FAQ

What is the latest open source security news?

The newest items in CISA's catalog are an OpenSSH authentication bypass on Linux (CVE-2026-123158, added November 9, 2026) and an UnrealIRCd flaw that lets a user inject server-to-server commands (CVE-2026-114713, added November 13). The most recent package compromise was LiteLLM 1.107.0 on PyPI on October 21, live for about two hours.

What is an open source supply chain attack?

It is an attack that puts malicious code into software other people install, usually by taking over a maintainer account or a release pipeline. In 2026 this hit Trivy, Axios, TanStack, Nx Console, AsyncAPI and LiteLLM. CISA lists four such compromises as actively exploited.

What is the Shai-Hulud worm?

Shai-Hulud is self-spreading npm malware that steals a developer's tokens and republishes that developer's packages with the malware inside. Its 2026 descendants include Mini Shai-Hulud, Miasma and ChainDrop. Singapore's Cyber Security Agency said the August ChainDrop wave reached over 1,300 package versions.

How many open source vulnerabilities were reported in 2026?

The GitHub Advisory Database published 12,597 reviewed advisories from January 1 to November 16, 2026, by this site's count. npm had the most (3,768), then pip (2,690) and Go (2,295). 1,356 were rated critical.

Which open source projects are on the CISA KEV list in 2026?

Among the 297 entries CISA added in 2026 are nine Linux kernel flaws, four each for WordPress and Langflow, three for LiteLLM, two for PHP and one for OpenSSH. Four entries are compromised packages: eslint-config-prettier, Trivy, TanStack and Nx Console.

Methods note

The KEV figures come from CISA's KEV JSON feed, catalog version 2026.11.13 (released November 13, 2026, 1,781 entries), read on November 17, 2026. "Added in 2026" means a dateAdded from January 1, 2026. Project counts use CISA's vendorProject and product fields as written. The four package compromises are the 2026 entries whose name or description says a malicious version was published or embedded. The AI, notebook and workflow group is our own grouping of eight named projects, listed in full above.

The GitHub figures come from the GitHub Advisory Database REST API, read on November 17, 2026, for advisories with a published date from January 1 to November 16, 2026. For the total, each reviewed advisory was counted once. Each table row filters by package registry, so an advisory that covers packages in two registries appears in both rows. Severity is GitHub's stated severity. Malware advisories were counted by month of publication. We report October and November only, because the feed published 37,035 malware advisories between September 10 and 30, far above any later month. The counts will change as both sources grow, and this page will be reviewed against them.

See also: the KEV glossary entry, CVE, CVSS, exploit, the patch and vulnerability management hub, Kubernetes Security News and Ransomware News.

Sources

  1. CISA, published November 13, 2026 · primary source
  2. GitHub Advisory Database (REST API), published November 17, 2026 · primary source
  3. Aqua Security (GitHub security advisory for aquasecurity/trivy), published March 24, 2026 · primary source
  4. Datadog Security Labs, published March 27, 2026
  5. TrendAI, published March 31, 2026
  6. TanStack (GitHub security advisory for TanStack/router), published May 12, 2026 · primary source
  7. Nx (GitHub security advisory for nrwl/nx-console), published May 18, 2026 · primary source
  8. Unit 42, Palo Alto Networks, published July 15, 2026
  9. Datadog Security Labs, published August 4, 2026
  10. Cyber Security Agency of Singapore, published August 6, 2026 · primary source
  11. LiteLLM (BerriAI), published October 23, 2026 · primary source
  12. LiteLLM (BerriAI), published October 21, 2026 · primary source
  13. CISA, published October 26, 2026 · primary source
  14. Alpine Linux, published November 5, 2026 · primary source
  15. OpenSSH project, published November 5, 2026 · primary source
  16. Open Source Security Foundation (OpenSSF), published November 9, 2026 · primary source

By email, once a week

Get the week’s briefings on Friday

The week’s briefings and the new entries in CISA’s exploited-vulnerabilities catalog, in one email.

Unsubscribe any time.