VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

agents: vulnerability history, versions and safety

agents is a package in the npm ecosystem. Vulert records 3 vulnerabilities for it across 44 releases, first recorded in Feb 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded M3
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
3 in the last 12 months

Most recent disclosure 13 Feb 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all agents vulnerabilities

Vulert verdict on agents 0.30.0 i

Updated on 23 Oct 2026

Good news: 0.30.0, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 3.

Package health score 88/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Active

What to do: Stay on 0.30.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 0.30.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 0.30.0 — unaffected i
  • Vulnerabilities on record 3 over 1 year · 3 in the last year i
  • Latest disclosure 13 Feb 2026 i
  • Highest CVSS 6.9 i
  • With no published fix 0 i
  • Stars 5,856 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for agents, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
0.30.0 22 Oct 2026 none MIT — Details →
0.29.0 20 Oct 2026 none MIT — Details →
0.28.1 13 Oct 2026 none MIT — Details →
0.28.0 09 Oct 2026 none MIT — Details →
0.27.0 07 Oct 2026 none MIT — Details →
0.26.0 02 Oct 2026 none MIT — Details →
0.25.0 02 Oct 2026 none MIT — Details →
0.24.0 18 Sep 2026 none MIT — Details →
0.23.0 11 Sep 2026 none MIT — Details →
0.22.0 27 Aug 2026 none MIT — Details →
0.21.0 18 Aug 2026 none MIT — Details →
0.20.1 28 Jul 2026 none MIT — Details →
0.20.0 27 Jul 2026 none MIT — Details →
0.19.0 23 Jul 2026 none MIT — Details →
0.18.0 22 Jul 2026 none MIT — Details →
0.0.0-d163561f 16 Jul 2026 M3 MIT Yes Details →
0.0.0-80a8fbd0 15 Jul 2026 M3 MIT Yes Details →
0.17.4 13 Jul 2026 none MIT — Details →
0.17.3 30 Jun 2026 none MIT — Details →
0.17.1 28 Jun 2026 none MIT — Details →
0.17.0 26 Jun 2026 none MIT — Details →
0.16.2 17 Jun 2026 none MIT — Details →
0.16.1 16 Jun 2026 none MIT — Details →
0.16.0 12 Jun 2026 none MIT — Details →
0.15.0 08 Jun 2026 none MIT — Details →
0.14.5 07 Jun 2026 none MIT — Details →
0.14.4 07 Jun 2026 none MIT — Details →
0.14.3 05 Jun 2026 none MIT — Details →
0.14.2 05 Jun 2026 none MIT — Details →
0.14.1 03 Jun 2026 none MIT — Details →
0.14.0 02 Jun 2026 none MIT — Details →
0.13.3 26 May 2026 none MIT — Details →
0.13.2 21 May 2026 none MIT — Details →
0.13.1 20 May 2026 none MIT — Details →
0.13.0 19 May 2026 none MIT — Details →
0.12.4 13 May 2026 none MIT — Details →
0.12.3 02 May 2026 none MIT — Details →
0.12.2 01 May 2026 none MIT — Details →
0.12.1 01 May 2026 none MIT — Details →
0.12.0 30 Apr 2026 none MIT — Details →
0.11.9 29 Apr 2026 none MIT — Details →
0.11.8 28 Apr 2026 none MIT — Details →
0.11.7 28 Apr 2026 none MIT — Details →
0.11.6 27 Apr 2026 none MIT — Details →
0.11.5 23 Apr 2026 none MIT — Details →
0.11.4 18 Apr 2026 none MIT — Details →
0.11.3 18 Apr 2026 none MIT — Details →
0.11.2 17 Apr 2026 none MIT — Details →
0.11.1 16 Apr 2026 none MIT — Details →
0.11.0 14 Apr 2026 none MIT — Details →
0.10.2 13 Apr 2026 none MIT — Details →
0.10.1 11 Apr 2026 none MIT — Details →
0.10.0 07 Apr 2026 none MIT — Details →
0.9.0 01 Apr 2026 none MIT — Details →
0.8.7 27 Mar 2026 none MIT — Details →
0.8.6 26 Mar 2026 none MIT — Details →
0.8.5 25 Mar 2026 none MIT — Details →
0.8.4 25 Mar 2026 none MIT — Details →
0.8.3 25 Mar 2026 none MIT — Details →
0.8.2 24 Mar 2026 none MIT — Details →
0.8.1 24 Mar 2026 none MIT — Details →
0.8.0 23 Mar 2026 none MIT — Details →
0.7.9 19 Mar 2026 none MIT — Details →
0.7.8 19 Mar 2026 none MIT — Details →
0.7.7 18 Mar 2026 none MIT — Details →
0.0.0-2203b301 12 Mar 2026 M3 MIT Yes Details →
0.7.6 11 Mar 2026 none MIT — Details →
0.7.5 05 Mar 2026 none MIT — Details →
0.7.4 04 Mar 2026 none MIT — Details →
0.7.3 04 Mar 2026 none MIT — Details →
0.7.2 02 Mar 2026 none MIT — Details →
0.7.1 02 Mar 2026 none MIT — Details →
0.7.0 02 Mar 2026 none MIT — Details →
0.6.0 25 Feb 2026 none MIT — Details →
0.5.1 20 Feb 2026 none MIT — Details →
0.5.0 17 Feb 2026 none MIT — Details →
0.4.1 12 Feb 2026 none MIT — Details →
0.4.0 09 Feb 2026 none MIT — Details →
0.3.10 04 Feb 2026 none MIT — Details →
0.3.9 04 Feb 2026 M2 MIT Yes Details →
0.3.8 03 Feb 2026 M2 MIT Yes Details →
0.3.7 03 Feb 2026 M2 MIT Yes Details →
0.3.6 17 Jan 2026 M3 MIT Yes Details →
0.3.5 13 Jan 2026 M3 MIT Yes Details →
0.3.4 09 Jan 2026 M3 MIT Yes Details →
0.3.3 29 Dec 2025 M3 MIT Yes Details →
0.3.2 29 Dec 2025 M3 MIT Yes Details →
0.3.1 29 Dec 2025 M3 MIT Yes Details →
0.3.0 22 Dec 2025 M3 MIT Yes Details →
0.0.0-9631b6d 22 Dec 2025 M3 MIT Yes Details →
0.2.35 22 Dec 2025 M3 MIT Yes Details →
0.0.0-17a0346 22 Dec 2025 M3 MIT Yes Details →
0.0.0-e6dd636 21 Dec 2025 M3 MIT Yes Details →
0.0.0-29938d4 21 Dec 2025 M3 MIT Yes Details →
0.0.0-1a3d226 21 Dec 2025 M3 MIT Yes Details →
0.2.34 21 Dec 2025 M3 MIT Yes Details →
0.0.0-087264c 21 Dec 2025 M3 MIT Yes Details →
0.0.0-e9b6bb7 21 Dec 2025 M3 MIT Yes Details →
0.0.0-6c17b00 21 Dec 2025 M3 MIT Yes Details →
0.0.0-57b7f2e 21 Dec 2025 M3 MIT Yes Details →
0.0.0-2e73791 21 Dec 2025 M3 — Yes Details →
0.0.0-b8c0595 21 Dec 2025 M3 — Yes Details →
0.0.0-9fbb1b6 21 Dec 2025 M3 — Yes Details →
0.0.0-d23a20c 18 Dec 2025 M3 — Yes Details →
0.0.0-eaeb1b3 12 Dec 2025 M3 — Yes Details →
0.2.32 12 Dec 2025 M3 — Yes Details →
0.0.0-79843bd 12 Dec 2025 M3 — Yes Details →
0.0.0-59ac254 11 Dec 2025 M3 — Yes Details →
0.0.0-58a4d8c 08 Dec 2025 M3 — Yes Details →
0.2.31 08 Dec 2025 M3 — Yes Details →
0.0.0-380c597 08 Dec 2025 M3 — Yes Details →
0.0.0-295f4dd 05 Dec 2025 M3 — Yes Details →
0.2.30 05 Dec 2025 M3 — Yes Details →
0.0.0-569e184 05 Dec 2025 M3 — Yes Details →
0.0.0-93d3975 05 Dec 2025 M3 — Yes Details →
0.0.0-8f03865 04 Dec 2025 M3 — Yes Details →
0.2.29 04 Dec 2025 M3 — Yes Details →
0.0.0-d08612f 04 Dec 2025 M3 — Yes Details →
0.0.0-b507395 04 Dec 2025 M3 — Yes Details →
0.0.0-cd8b7fd 04 Dec 2025 M3 — Yes Details →

The newest 120 of 656 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 3

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 3 of the 3 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for agents

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-1664: Cloudflare Agents SDK Insecure Direct Object Reference in Email Routing 6.9 medium 0.3.7 03 Feb 2026
CVE-2026-1721: agents Package Vulnerable to Reflected XSS in AI Playground OAuth Callback 6.2 medium 0.3.10 13 Feb 2026
Cloudflare Agents has a Reflected Cross-Site Scripting (XSS) vulnerability in AI Playground site 6.2 medium 0.3.10 13 Feb 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About agents

Is agents safe to use?

Vulert records 3 vulnerabilities for agents in npm: 0 critical, 0 high, 3 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is agents's Vulert package health score?

Vulert scores agents 88/100, which reads as healthy. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of agents affected?

No. 0.30.0, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

How many vulnerabilities does agents have?

3 vulnerabilities are recorded for agents in the npm ecosystem: 0 critical, 0 high, 3 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new agents vulnerabilities disclosed?

3 vulnerabilities were recorded for agents in the last 12 months, and the oldest entry in this database dates to 03 Feb 2026. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of agents are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor agents for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the agents version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.