Is this package version vulnerable?
Look up an npm, PyPI, Go, Cargo, RubyGems, Packagist, Maven, NuGet, Pub, Hex or Swift package, or a language runtime (Java, Node.js, Python, PHP, Ruby, Go, .NET, Rust), to see which of its versions have known vulnerabilities, how severe they are and the version that fixes them. Data from OSV.dev and, for runtimes, the NVD, checked every day. Free, and no account needed.
Browse by ecosystem
npm
JavaScript · 1720 packages
PyPI
Python · 161 packages
Go
Go · 0 packages
Cargo
Rust · 0 packages
RubyGems
Ruby · 0 packages
Packagist
PHP · 0 packages
Maven
Java · 0 packages
NuGet
C# · 0 packages
Pub
Dart · 0 packages
Hex
Elixir · 0 packages
Swift
Swift · 0 packages
Runtimes and servers
Java, Node.js, Python… · 54 runtimes
Recently published advisories
-
Unknown
21 Nov 2026 · Hex
CVE-2026-128361: Unsanitized presence key crashes Presence tracker
-
Unknown
21 Nov 2026 · Hex
CVE-2026-129344: Client-selected V1 serializer crashes shared broadcast dispatch on binary payloads
-
High
20 Nov 2026 · npm
CVE-2026-122244: Budibase: Cross-privilege Stored XSS in the Budibase Builder via broken HTML-escaping in `jsonFormatter.format()` rendered through `{@html}` in the CSP-less Builder origin
-
Medium
20 Nov 2026 · PyPI
CVE-2026-132276: wcmatch: Polynomial-time ReDoS when matching untrusted names against multi-star patterns (default flags)
-
Medium
20 Nov 2026 · PyPI
CVE-2026-132277: Inscriptis: Quadratic memory growth from sibling <table> elements in get_text()
-
High
20 Nov 2026 · PyPI
CVE-2026-132275: svglib: Exponential resource consumption via nested <use> references in svg2rlg
-
Medium
20 Nov 2026 · Packagist
CVE-2026-104884: contao/core-bundle: Cross-site scripting in the frontend search results
-
High
20 Nov 2026 · Packagist
CVE-2026-104883: contao/core-bundle: Non-admin users can self-grant permissions that implicitly make them administrators
-
Medium
20 Nov 2026 · Packagist
CVE-2026-104882: contao/core-bundle: Improper access control in the CSV import wizard
-
Medium
20 Nov 2026 · Packagist
CVE-2026-104881: contao/newsletter-bundle: Contao newsletter custom actions bypass channel-scoped authorization
-
Low
20 Nov 2026 · PyPI
CVE-2026-77331: memtomem-stm: Concurrent LTM recovery can duplicate reconnects or reuse a cancelled transport session
-
Low
20 Nov 2026 · PyPI
CVE-2026-77332: memtomem-stm: Surfaced memory data can escape the Markdown compatibility boundary
How it works
- We track the packages people use. Every package version in the projects AIssue monitors, and in the free checks, goes into one shared catalog.
- Every day, each version is checked against OSV.dev. When a new advisory affects a version, its page changes the same day.
- Each advisory is read for its fix. We work out the version that fixes it for each affected version, and the command to upgrade with your package manager.
- Only public packages get a page. A version is shown once deps.dev knows it or an advisory names it, so private packages never appear.
CVE, GHSA, PYSEC: one vulnerability, several names
The same vulnerability is often published by several databases, each with its own id. A CVE id (CVE-2024-1234) is the global one, given by a CVE numbering authority. The GitHub Advisory Database uses GHSA ids and covers npm, PyPI, Go, Cargo, RubyGems and Packagist; the Python Packaging Advisory Database uses PYSEC; the Go team uses GO- ids and the Rust community RUSTSEC.
OSV.dev links them as aliases. We show each vulnerability once, under the GitHub id when there is one, and every
other id redirects to it: /tools/advisories/CVE-2024-1234/ opens the same page as its GHSA id.
An advisory lists ranges of affected versions, such as “>= 4.0.0, < 4.17.21”. The end of the range is the version that fixes it. A version page tells you which advisories cover that exact version and the one upgrade that fixes all of them.
Questions
Where does the data come from?
From OSV.dev, the open vulnerability database, which brings together the GitHub Advisory Database, the Python Packaging Advisory Database, the Go vulnerability database, RustSec and others. Licences and whether a version exists come from deps.dev. Each page says when its data was last checked.
Why is a package or version missing?
These pages cover the packages AIssue checks every day for the projects it monitors, so popular packages are here and the list grows every day. To check a package version that is not listed, run the free dependency check on your lockfile: it looks every version up in OSV.dev.
A version says "No known vulnerabilities". Is it safe?
It means no published advisory affects it today. New vulnerabilities are disclosed every day, and an advisory can be published for an old version years after its release. Check your project regularly, or let a free AIssue account do it every day for you.
What does "fixed in" mean?
It is the first version, in the same release line, that the advisory lists as no longer affected. Upgrading to it (or any later version) fixes that vulnerability. When a version has several advisories, the page gives the one upgrade that fixes all of them that have a fix.
How do I read the severity and CVSS score?
CVSS scores go from 0 to 10: 9.0 and above is critical, 7.0 to 8.9 high, 4.0 to 6.9 medium, below 4 low. Some databases rate the severity themselves; we show their rating when they give one. Severity says how bad an attack could be, not whether your code uses the vulnerable feature: read the advisory to see.
Do you show which projects use a package?
No. Pages only show public information about the package and its advisories, never who uses it or how many AIssue projects do. Private packages from our users' lockfiles never get a page.
Related free tools
Dependency vulnerability check
Check requirements.txt, package-lock.json, poetry.lock and more against OSV.dev. Free report by email with fix commands. No account needed.
GitHub repo vulnerability check
Paste a public GitHub repo URL. We find every lockfile, check each package version against OSV.dev and email you the fixes. Free, no account.
Last updated .