Exploited Vulnerabilities
by Vextorium in Security & trust
Vulnerabilities being actively exploited according to CISA's KEV catalog: CVE, vendor, product, name, description, date added, remediation due date and ransomware use; the latest N days or search by vendor/product (Microsoft, Cisco, Fortinet...).
https://api.vextorium.com/v1/exploited-vulnerabilities- Price
- $0.003
- per call in USDC
- Uptime
- 0.0%
- last 30 days
- Response time
- -
- no timed checks yet
- Last check
- Failed
- 3 h ago, next any minute now
Reliability
Latest check failed 3 h ago: Amount "0.003" is not in atomic token units
How to call it
POST https://api.vextorium.com/v1/exploited-vulnerabilities
Each call costs $0.003 in USDC on Base, paid with the request over x402.
Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.
Example request
From the listing.
POST https://api.vextorium.com/v1/exploited-vulnerabilities
content-type: application/json
{
"days": 14,
"limit": 2
}Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
days | integer | No | |
limit | integer | No | |
ransomware | boolean | No | |
search | string | No |
Example response
The provider's example. We can't check it without paying.
Example response, 36 lines
{
"catalog": "2026.10.02",
"matches": 17,
"source": "CISA Known Exploited Vulnerabilities (US public domain)",
"total_catalog": 1733,
"vulnerabilities": [
{
"action": "Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discon…",
"correction_term": "2026-10-05",
"cve": "CVE-2026-102490",
"cwe": [
"CWE-269"
],
"description": "Zammad GmbH Zammad contains an improper privilege management vulnerability that can allow the local zammad user to escalate privileges to root. This vulnerability can be chained with CVE-2026-102489.",
"high": "2026-10-02",
"manufacturer": "Zammad GmbH",
"name": "Zammad GmbH Zammad Improper Privilege Management Vulnerability",
"product": "Zammad",
"ransomware": "Unknown"
},
{
"action": "Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discon…",
"correction_term": "2026-10-05",
"cve": "CVE-2026-102489",
"cwe": [
"CWE-384"
],
"description": "Zammad GmbH Zammad contains a session fixation vulnerability that can lead to remote code execution as the zammad user. This vulnerability can be chained with CVE-2026-102490.",
"high": "2026-10-02",
"manufacturer": "Zammad GmbH",
"name": "Zammad GmbH Zammad Session Fixation Vulnerability",
"product": "Zammad",
"ransomware": "Unknown"
}
]
}Call it from code
The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.003.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://api.vextorium.com/v1/exploited-vulnerabilities' \
-H 'content-type: application/json' \
--data-raw '{"days":14,"limit":2}'
# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - -X POST 'https://api.vextorium.com/v1/exploited-vulnerabilities' \
-H 'content-type: application/json' \
--data-raw '{"days":14,"limit":2}' \
| grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decodeJavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";
// Pays at most $0.003 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.003" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);
// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.003 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fapi.vextorium.com%2Fv1%2Fexploited-vulnerabilities&method=POST
const res = await pay("https://api.vextorium.com/v1/exploited-vulnerabilities", {
method: "POST",
headers: { "content-type": "application/json" },
body: JSON.stringify({
"days": 14,
"limit": 2
}),
});
console.log(res.status, await res.text());Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client
# Pays at most $0.003 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.003"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))
with x402_requests(client) as session:
res = session.post(
"https://api.vextorium.com/v1/exploited-vulnerabilities",
json={
"days": 14,
"limit": 2,
},
)
print(res.status_code, res.text)Security scan
No findings
We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 3 h ago | Amount "0.003" is not in atomic token units | 402 | 103 ms | $0.003 |
| 7 h ago | Amount "0.003" is not in atomic token units | 402 | 114 ms | $0.003 |
| 12 h ago | Amount "0.003" is not in atomic token units | 402 | 94 ms | $0.003 |
| 17 h ago | Amount "0.003" is not in atomic token units | 402 | 303 ms | $0.003 |
| 22 h ago | Amount "0.003" is not in atomic token units | 402 | 94 ms | $0.003 |
Show 10 older checks
| 26 h ago | Amount "0.003" is not in atomic token units | 402 | 161 ms | $0.003 |
| 31 h ago | Amount "0.003" is not in atomic token units | 402 | 90 ms | $0.003 |
| 35 h ago | Amount "0.003" is not in atomic token units | 402 | 84 ms | $0.003 |
| 40 h ago | Amount "0.003" is not in atomic token units | 402 | 76 ms | $0.003 |
| 44 h ago | Amount "0.003" is not in atomic token units | 402 | 91 ms | $0.003 |
| 2 days ago | Amount "0.003" is not in atomic token units | 402 | 168 ms | $0.003 |
| 2 days ago | Amount "0.003" is not in atomic token units | 402 | 86 ms | $0.003 |
| 2 days ago | Amount "0.003" is not in atomic token units | 402 | 80 ms | $0.003 |
| 3 days ago | Amount "0.003" is not in atomic token units | 402 | 86 ms | $0.003 |
| 3 days ago | Amount "0.003" is not in atomic token units | 402 | 92 ms | $0.003 |