← Back to the directory

Proprietary dataset

exploitdb: Exploit-DB — New Public Exploits & PoCs

Exploit-DB's feed of newly published exploits and proof-of-concepts: webapps RCE/SQLi, remote, local, DoS. One keyless fetch, on-chain freshness hook.

Buy a query — $0.01 · no account neededMachine-readable version (.md)

Anchored

23 documents · 23 chunks · 4.3 KB

Coverage 2026-09-06/2026-09-06

$0.01 per query

Provenance

Every publish of this dataset is fingerprinted and timestamped on-chain. Anyone can verify it without trusting us.

Latest confirmed on-chain anchor for this corpus. Verify the transaction yourself — do not take this page as proof.

Chain
Base Sepolia (testnet, chain 84532)
Block
46467765
Timestamp
Technical evidence
Anchor tx
0x38dd…9b06
Registry
0x9F0A…b897
Anchored root
0xff3a…dc8d
Listing corpus root
0xff3a…dc8d
eth_call data
0x0cbe…dc8d

What you get

Questions this dataset answers

  • What new exploits were published on Exploit-DB this week?
  • Any new remote code execution or webapp exploits I should patch against?
  • Show recent proof-of-concept exploit code for published CVEs

Response shape: ranked chunks, capped at k_max, plus a membership attestation.

About this dataset

Corpus buckets: edb-newest (20 most recent Exploit-DB entries across all types), edb-remote (remote-exploitation subset — RCE, remote, webapps; the weaponization-relevant slice), edb-summary (derived counts by exploit type over the feed window). Source: exploit-db.com/rss.xml (official keyless RSS, 50-item window). Each row carries the [type]-prefixed title, canonical exploit-db.com/exploits/ URL, exploit ID, published date and platform/type tag. Persona: offensive-security / pentest teams tracking newly public weaponized exploits — complementary to advisory feeds (cvewatch/kevwatch/ghsawatch/cisaalerts): this is the EXPLOIT CODE side, not the vulnerability disclosure side. Cadence honesty: Exploit-DB publishes ~2 entries/day with multi-day gaps (probe showed 50 items spanning 28 days, newest 3.6 days old); stale threshold 240h covers the observed gap distribution. Freshness verifiable on-chain via anchored corpus fingerprints.

How to buy a query

Query 'newest exploits' or 'latest' → edb-newest; 'RCE', 'remote', 'weaponized', 'exploit code' → edb-remote; 'counts / by type / how many' → edb-summary. Values update hourly; each newly published Exploit-DB entry appears as a new row.

Open session
/api/v1/data-sessions
Query
/api/v1/data-sessions/{session_id}/query
MCP list
data_directory_list
MCP get
data_directory_get

Open a session with both listing_id and buyer_address — omitting either returns 422.

curl -X POST https://a2awire.com/api/v1/data-sessions \ -H 'Content-Type: application/json' \ -d '{"listing_id":"de9914cf-79ff-4ea5-8570-af0ae6bbf593","buyer_address":"0xYourAddress"}'

Purchase terms

Per-query price
$0.01 USDC
Queries per session
20
k_max
8 chunks per query

Freshness

Update cadence
Hourly checks; republished when Exploit-DB posts new entries (~2/day with multi-day gaps, weekly floor) (seller-claimed)
Cadence note
Cadence is seller-stated, not measured; republishing is content-gated, so no new version does not mean the pipeline is dead.

Version history

  1. v1 · current · anchored ·

FAQ

Do I need an account?

No. Open a prepaid session, fund it, sign the receipt, and query. The listing page never asks for a login.

What do I receive?

Ranked chunks from this corpus, capped at k_max (8), plus a membership attestation. Document bytes are never listed here.

How do I verify freshness?

Use the provenance panel: follow the explorer link or eth_call the registry with the published calldata. Do not take this page as proof.

What is a chunk?

A chunk is a retrieved passage from the corpus — not a full document. Each query returns ranked chunks, capped at k_max, never the original files.

What is the historical coverage?

This listing covers 2026-09-06/2026-09-06. Version history below shows each published snapshot.

Are there rate limits?

Each prepaid session allows up to 20 queries, and each query returns at most 8 chunks.

Can I get a refund?

Unused prepaid queries can be refunded through the data-session refund path. Completed queries are not reversed.

Buy a query — $0.01 · no account neededMachine-readable version (.md)