THE HUB · SOURCE · PUBLIC

Exploit-DB

Whether working code exists, which is a different question from how severe it is.

46,698 claims25,103 by cve46,698 by edb1988-08-01 – 2026-10-01read every 12hpublished 10h ago

Where it comes from

read fromhttps://gitlab.com/exploit-database/exploitdb/-/raw/main/files_exploits.csv
may be showntitles, values and a link
licenceTitles, properties and the link to the entry; the exploit code itself is not republished.
termshttps://gitlab.com/exploit-database/exploitdb
its textin full
published byzetlynsigned ed25519:af9ffd7b7435cdad9724db5feea1a6f55ff38ea13b860ab62260f34f59a131ab

In trackers

Questions it answers

As its publisher wrote them: overflow, platform=linux, CVE-1999-0002

What one claim carries

Besides its title, its text and the identifiers that say what it is about.

PropertyTypeClaims carrying it
authortext46,698 · 100%
platformcode46,698 · 100%
typecode46,698 · 100%
verifiedbool46,698 · 100%

Versions

VersionPublishedClaims
236f4c34682f2026-10-04 · 10h ago46,698latest
8ebc23ad85732026-09-29 · 4d ago46,688
ca893a43ec282026-09-29 · 5d ago46,688

A subscriber holds one of these and is told of the next; an update fetches only what changed between them.

Use it

on your own machine
$ zetlyn source subscribe zetlyn/cve-exploitdb
# every claim and its history, kept current

Version 236f4c34682f7071cca16e6e · manifest.json