tunz/js-vuln-db resource
A collection of JavaScript engine CVEs with PoCs observed · 2026-08-28
Health v2 · maintenance only
32/100
- Activity 0
- Release rhythm 35
- Longevity 100
Flags: no_releases no_license
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.
- gap_med: n/a
- age_days: 3680
- days_rel: n/a
- days_push: 2556
- n_releases_24m: 0
Adoption not part of the score
2318 stars · 404 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded
A curated database of JavaScript engine vulnerabilities (CVEs) with proof-of-concept exploits, covering engines like V8, SpiderMonkey, JavaScriptCore, and Chakra. Each entry documents the affected feature, vulnerability keywords, and credits the discoverer.
Use cases
- study javascript engine cve exploits
- find poc for a v8 vulnerability
- learn about oob and type confusion bugs in js engines
- research historical javascriptcore vulnerabilities
- prepare for browser exploitation research
- find examples of integer overflow bugs in spidermonkey
When to choose
- researching javascript engine exploitation techniques
- learning how memory corruption bugs manifest in js engines
- looking for reference PoCs for known CVEs
When to avoid
- scanning your own code for vulnerabilities
- needing an up-to-date CVE feed
- production security tooling
Facets
dataset · maturity maintenance
security vulnerability-scanning reverse-engineering security developer-tools tutorials cross-platform cve poc javascript-engines v8 spidermonkey javascriptcore chakra security-research exploit-development javascript
1 source
- readme: https://github.com/tunz/js-vuln-db · fetched 2026-08-28 · 44c21e58d8f2
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| tunz/js-vuln-db | main | 32 |
For agents
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem