OSV Vulnerability Details API
Use the OSV Vulnerability Details API to retrieve a known vulnerability record by its database identifier. Provide the exact OSV, GHSA, CVE, or other supported record ID and receive the available advisory text, affected packages and ranges, publication and modification dates, severity information, and reference links. Use the record to investigate a batch-query match, document remediation evidence, or refresh a vulnerability knowledge base. Alias identifiers are included when supplied by the source, and withdrawn records must be interpreted using their withdrawal timestamp. The detail page includes complete request and response examples, the identifier parameter, and per-request pricing.
- Selected price
- $0.005 / callPublished pricing
- Sellers / implementations
- 1 / 1
- Requests · 30d
- —Loading...
- Success rate · 30d
- —Loading...
| Seller | Pricing | Requests · 30d | Performance | Access |
|---|---|---|---|---|
osvCurrent OSV Vulnerability Details API · GET · View API reference | $0.005 / call | — | —successP50— |
Run sends a real API request. Charges follow the published API contract.
Response structure
affectedobject[]database_specificobjectsourcestring
ecosystem_specificobjectseveritystring
packageobjectecosystemstringnamestringpurlstring
rangesobject[]eventsobject[]introducedstringfixedstring
repostringtypestring
versionsstring[]
detailsstringidstringmodifiedstringpublishedstringreferencesobject[]typestringurlstring
schema_versionstringsummarystringaliasesstring[]database_specificobjectcwe_idsstring[]github_reviewedbooleangithub_reviewed_atstringnvd_published_atstringseveritystring
severityobject[]scorestringtypestring
// Inferred from response examples. Fields are optional and other fields may be returned.
export type ApiResponse = {
affected?: Array<{
database_specific?: {
source?: string;
};
ecosystem_specific?: {
severity?: string;
};
package?: {
ecosystem?: string;
name?: string;
purl?: string;
};
ranges?: Array<{
events?: Array<{
introduced?: string;
fixed?: string;
}>;
repo?: string;
type?: string;
}>;
versions?: Array<string>;
}>;
details?: string;
id?: string;
modified?: string;
published?: string;
references?: Array<{
type?: string;
url?: string;
}>;
schema_version?: string;
summary?: string;
aliases?: Array<string>;
database_specific?: {
cwe_ids?: Array<string>;
github_reviewed?: boolean;
github_reviewed_at?: string;
nvd_published_at?: string;
severity?: string;
};
severity?: Array<{
score?: string;
type?: string;
}>;
};- Method
- GET
- Endpoint
https://api.openany.si/v1/agent-apis/osv/v1/vulns/{id}- Content type
- application/json
- Authentication
Authorization: Bearer $OPENANY_API_KEY
curl \
'https://api.openany.si/v1/agent-apis/osv/v1/vulns/OSV-2020-111' \
-X GET \
-H "Authorization: Bearer $OPENANY_API_KEY" \
-H 'Content-Type: application/json'Input parameters
Fields in this listing; additional options and input encoding can vary by provider.
| Parameter | Location | Type | Required | Description |
|---|---|---|---|---|
id | URL path parameterspath | string | Yes | Exact case-sensitive identifier of an indexed vulnerability record, e.g. OSV-2020-111. An alias does not guarantee a standalone record. |
Required markers inside a nested object or variant apply when that object or variant is used.
Sample response
Sample response · Documented HTTP 200 Example from the provider's documentation. Field values in your results will differ.
{
"affected": [
{
"database_specific": {
"source": "https://github.com/google/oss-fuzz-vulns/blob/main/vulns/poppler/OSV-2020-111.yaml"
},
"ecosystem_specific": {
"severity": "HIGH"
},
"package": {
"ecosystem": "OSS-Fuzz",
"name": "poppler",
"purl": "pkg:generic/poppler"
},
"ranges": [
{
"events": [
{
"introduced": "e4badf4d745b8e8f9a0a25b6c3cc97fbadbbb499"
},
{
"fixed": "155f73bdd261622323491df4aebb840cde8bfee1"
}
],
"repo": "https://anongit.freedesktop.org/git/poppler/poppler.git",
"type": "GIT"
}
]
}
],
"details": "OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=21604\n\n```\nCrash type: Heap-use-after-free WRITE 4\nCrash state:\nint std::__1::__cxx_atomic_fetch_sub<int>\nstd::__1::__atomic_base<int, true>::operator--\nObject::free\n```\n",
"id": "OSV-2020-111",
"modified": "2022-04-13T03:04:37.331327Z",
"published": "2020-06-24T01:51:14.570467Z",
"references": [
{
"type": "REPORT",
"url": "https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=21604"
}
],
"schema_version": "1.7.3",
"summary": "Heap-use-after-free in int std::__1::__cxx_atomic_fetch_sub<int>"
}Agent integration
Copy the resource contract without sharing an API key.
View API Markdown
# OSV Vulnerability Details API
Use the OSV Vulnerability Details API to retrieve a known vulnerability record by its database identifier. Provide the exact OSV, GHSA, CVE, or other supported record ID and receive the available advisory text, affected packages and ranges, publication and modification dates, severity information, and reference links. Use the record to investigate a batch-query match, document remediation evidence, or refresh a vulnerability knowledge base. Alias identifiers are included when supplied by the source, and withdrawn records must be interpreted using their withdrawal timestamp. The detail page includes complete request and response examples, the identifier parameter, and per-request pricing.
## Available implementations
osv · OSV Vulnerability Details API: https://openany.si/markets/apis/capabilities/osv-vulnerability-details-api?offering=51b5203c-b8fa-4043-a297-95d1a1f536d4 · $0.005 / call
## Selected API contract
Documentation: https://openany.si/markets/apis/capabilities/osv-vulnerability-details-api
Method: GET
Endpoint: https://api.openany.si/v1/agent-apis/osv/v1/vulns/{id}
Price: $0.005 / call
Provider: osv
Contract revision: 1
Price source: OpenAny public API contract and documented provider unit rates. Price update time: not supplied.
Use OPENANY_API_KEY from the environment. API Key calls use your shared balance.
## Prepared request
```bash
curl \
'https://api.openany.si/v1/agent-apis/osv/v1/vulns/OSV-2020-111' \
-X GET \
-H "Authorization: Bearer $OPENANY_API_KEY" \
-H 'Content-Type: application/json'
```
## API contract
```json
{
"resource_type": "api",
"name": "OSV Vulnerability Details API",
"endpoint": "https://api.openany.si/v1/agent-apis/osv/v1/vulns/{id}",
"method": "GET",
"content_type": "none",
"execution_mode": "sync",
"authentication": {
"type": "bearer",
"environment_variable": "OPENANY_API_KEY"
},
"inputs": [
{
"description": "Exact case-sensitive identifier of an indexed vulnerability record, e.g. OSV-2020-111. An alias does not guarantee a standalone record.",
"location": "path",
"name": "id",
"nullable": false,
"required": true,
"type": "string"
}
],
"billing": {
"currency": "USD",
"mode": "fixed",
"priceMicroUsd": "5000",
"rounding": null,
"unit": "call",
"unitQuantity": null
},
"examples": [
{
"http_status": 200,
"name": "Official example · Live OSV paired capture - 2026-11-19",
"request": {
"body": null,
"headers": {},
"path": {
"id": "OSV-2020-111"
},
"query": {}
},
"response_body": {
"affected": [
{
"database_specific": {
"source": "https://github.com/google/oss-fuzz-vulns/blob/main/vulns/poppler/OSV-2020-111.yaml"
},
"ecosystem_specific": {
"severity": "HIGH"
},
"package": {
"ecosystem": "OSS-Fuzz",
"name": "poppler",
"purl": "pkg:generic/poppler"
},
"ranges": [
{
"events": [
{
"introduced": "e4badf4d745b8e8f9a0a25b6c3cc97fbadbbb499"
},
{
"fixed": "155f73bdd261622323491df4aebb840cde8bfee1"
}
],
"repo": "https://anongit.freedesktop.org/git/poppler/poppler.git",
"type": "GIT"
}
]
}
],
"details": "OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=21604\n\n```\nCrash type: Heap-use-after-free WRITE 4\nCrash state:\nint std::__1::__cxx_atomic_fetch_sub<int>\nstd::__1::__atomic_base<int, true>::operator--\nObject::free\n```\n",
"id": "OSV-2020-111",
"modified": "2022-04-13T03:04:37.331327Z",
"published": "2020-06-24T01:51:14.570467Z",
"references": [
{
"type": "REPORT",
"url": "https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=21604"
}
],
"schema_version": "1.7.3",
"summary": "Heap-use-after-free in int std::__1::__cxx_atomic_fetch_sub<int>"
}
},
{
"http_status": 200,
"name": "Official example · Live details for an actual batch match",
"request": {
"body": null,
"headers": {},
"path": {
"id": "GHSA-3v79-q7ph-j75h"
},
"query": {}
},
"response_body": {
"affected": [
{
"database_specific": {
"source": "https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2024/02/GHSA-3v79-q7ph-j75h/GHSA-3v79-q7ph-j75h.json"
},
"package": {
"ecosystem": "PyPI",
"name": "mlflow",
"purl": "pkg:pypi/mlflow"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "2.10.0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.0.1",
"0.1.0",
"0.2.0",
"0.2.1",
"0.3.0",
"0.4.0",
"0.4.1",
"0.4.2",
"0.5.0",
"0.5.1",
"0.5.2",
"0.6.0",
"0.7.0",
"0.8.0",
"0.8.1",
"0.8.2",
"0.9.0",
"0.9.0.1",
"0.9.1",
"1.0.0",
"1.1.0",
"1.1.1.dev0",
"1.10.0",
"1.11.0",
"1.12.0",
"1.12.1",
"1.13",
"1.13.1",
"1.14.0",
"1.14.1",
"1.15.0",
"1.16.0",
"1.17.0",
"1.18.0",
"1.19.0",
"1.2.0",
"1.20.0",
"1.20.1",
"1.20.2",
"1.21.0",
"1.22.0",
"1.23.0",
"1.23.1",
"1.24.0",
"1.25.0",
"1.25.1",
"1.26.0",
"1.26.1",
"1.27.0",
"1.28.0",
"1.29.0",
"1.3.0",
"1.30.0",
"1.30.1",
"1.4.0",
"1.5.0",
"1.6.0",
"1.7.0",
"1.7.1",
"1.7.2",
"1.8.0",
"1.9.0",
"1.9.1",
"2.0.0",
"2.0.0rc0",
"2.0.1",
"2.1.0",
"2.1.1",
"2.2.0",
"2.2.1",
"2.2.2",
"2.3.0",
"2.3.1",
"2.3.2",
"2.4.0",
"2.4.1",
"2.4.2",
"2.5.0",
"2.6.0",
"2.7.0",
"2.7.1",
"2.8.0",
"2.8.1",
"2.9.0",
"2.9.1",
"2.9.2"
]
}
],
"aliases": [
"BIT-mlflow-2024-27133",
"CVE-2024-27133",
"PYSEC-2024-241"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": true,
"github_reviewed_at": "2024-02-27T21:57:34Z",
"nvd_published_at": "2024-02-23T22:15:55Z",
"severity": "CRITICAL"
},
"details": "Insufficient sanitization in MLflow leads to XSS when running a recipe that uses an untrusted dataset. This issue leads to a client-side RCE when running the recipe in Jupyter Notebook. The vulnerability stems from lack of sanitization over dataset table fields.",
"id": "GHSA-3v79-q7ph-j75h",
"modified": "2025-04-08T22:30:59.347458Z",
"published": "2024-02-24T00:30:20Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-27133"
},
{
"type": "WEB",
"url": "https://github.com/mlflow/mlflow/pull/10893"
},
{
"type": "WEB",
"url": "https://github.com/mlflow/mlflow/commit/c43823750bffa5b6abcc086683b15a068513b67b"
},
{
"type": "WEB",
"url": "https://github.com/mlflow/mlflow/commit/cfa71879a884cc3520e23ccab998c9aa78fdf2b1"
},
{
"type": "PACKAGE",
"url": "https://github.com/mlflow/mlflow"
},
{
"type": "WEB",
"url": "https://github.com/pypa/advisory-database/tree/main/vulns/mlflow/PYSEC-2024-241.yaml"
},
{
"type": "WEB",
"url": "https://research.jfrog.com/vulnerabilities/mlflow-untrusted-dataset-xss-jfsa-2024-000631932"
}
],
"schema_version": "1.9.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H",
"type": "CVSS_V3"
}
],
"summary": "MLFlow Cross-site Scripting vulnerability leads to client-side Remote Code Execution"
}
},
{
"http_status": 200,
"name": "Official example · Historical official documentation response",
"request": {
"body": null,
"headers": {},
"path": {
"id": "OSV-2020-111"
},
"query": {}
},
"response_body": {
"affected": [
{
"database_specific": {
"source": "https://github.com/google/oss-fuzz-vulns/blob/main/vulns/poppler/OSV-2020-111.yaml"
},
"ecosystem_specific": {
"severity": "HIGH"
},
"package": {
"ecosystem": "OSS-Fuzz",
"name": "poppler",
"purl": "pkg:generic/poppler"
},
"ranges": [
{
"events": [
{
"introduced": "e4badf4d745b8e8f9a0a25b6c3cc97fbadbbb499"
},
{
"fixed": "155f73bdd261622323491df4aebb840cde8bfee1"
}
],
"repo": "https://anongit.freedesktop.org/git/poppler/poppler.git",
"type": "GIT"
}
]
}
],
"details": "OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=21604\n\n```\nCrash type: Heap-use-after-free WRITE 4\nCrash state:\nint std::__1::__cxx_atomic_fetch_sub<int>\nstd::__1::__atomic_base<int, true>::operator--\nObject::free\n```\n",
"id": "OSV-2020-111",
"modified": "2022-04-13T03:04:37.331327Z",
"published": "2020-06-24T01:51:14.570467Z",
"references": [
{
"type": "REPORT",
"url": "https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=21604"
}
],
"schema_version": "1.4.0",
"summary": "Heap-use-after-free in int std::__1::__cxx_atomic_fetch_sub<int>"
}
}
]
}
```Error handling
| Status | Next step |
|---|---|
400 | Check the offering and request fields. |
401 / 403 | Verify your credentials and access permissions. |
402 | Inspect the selected access mode and returned payment requirements. |
429 | Respect the returned rate limit and retry guidance. |
5xx | Inspect the error and usage record before retrying a paid operation. |
Official example · Live OSV paired capture - 2026-11-19
Example from the provider's documentation. Field values in your results will differ.
Prepare your environment
Use a terminal with cURL installed.
Use an OpenAny API key with shared-balance access. Confirm availability and price before running; a call may charge your balance.
Set the key in your terminal using the hidden prompt below. Keep its value out of source files and logs.
Terminal · macOS / Linuxprintf 'OpenAny API key: ' read -r -s OPENANY_API_KEY export OPENANY_API_KEY printf '\n'Run the request
Paste the complete command below into your terminal.
Values to replace before running 1
Review these request fields before running. Keep the published provider and request method unchanged.
id- Exact case-sensitive identifier of an indexed vulnerability record, e.g. OSV-2020-111. An alias does not guarantee a standalone record.
Terminal · cURLcurl \ 'https://api.openany.si/v1/agent-apis/osv/v1/vulns/OSV-2020-111' \ -X GET \ -H "Authorization: Bearer $OPENANY_API_KEY" \ -H 'Content-Type: application/json'Check the response
Sample response · Documented HTTP 200
Sample response{ "affected": [ { "database_specific": { "source": "https://github.com/google/oss-fuzz-vulns/blob/main/vulns/poppler/OSV-2020-111.yaml" }, "ecosystem_specific": { "severity": "HIGH" }, "package": { "ecosystem": "OSS-Fuzz", "name": "poppler", "purl": "pkg:generic/poppler" }, "ranges": [ { "events": [ { "introduced": "e4badf4d745b8e8f9a0a25b6c3cc97fbadbbb499" }, { "fixed": "155f73bdd261622323491df4aebb840cde8bfee1" } ], "repo": "https://anongit.freedesktop.org/git/poppler/poppler.git", "type": "GIT" } ] } ], "details": "OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=21604\n\n```\nCrash type: Heap-use-after-free WRITE 4\nCrash state:\nint std::__1::__cxx_atomic_fetch_sub<int>\nstd::__1::__atomic_base<int, true>::operator--\nObject::free\n```\n", "id": "OSV-2020-111", "modified": "2022-04-13T03:04:37.331327Z", "published": "2020-06-24T01:51:14.570467Z", "references": [ { "type": "REPORT", "url": "https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=21604" } ], "schema_version": "1.7.3", "summary": "Heap-use-after-free in int std::__1::__cxx_atomic_fetch_sub<int>" }
Common questions
Do I need a separate key for every provider?
Use your OpenAny API key for standard API access. Read it from OPENANY_API_KEY in your environment and keep it out of prompts, source code and logs.
Are these providers interchangeable?
No. Each offering has its own inputs, pricing and response contract. Selecting a catalog offering does not establish automatic routing or fallback. Confirm the service contract before calling.
How is this API billed?
API-key calls use your shared balance at the selected implementation's published rate. Check the billing unit and request-specific pricing rules before making a paid call. Recorded usage determines the final charge under that contract.
Where do the price and contract come from?
The selected implementation publishes its provider, request contract, revision and billing rules through OpenAny's public API catalog. A revision number identifies a contract version, not a price update date. A price update timestamp is not supplied; do not treat a page date as one.
How do OpenAny Balance and x402 differ?
OpenAny Balance uses an API key and one shared balance. Card, USDC and x402 top-ups, card auto top-up and USDC subscriptions fund that balance; available routes appear on the Credits page. Direct x402 is a separate pay-per-request flow, available only on listings that show it and requiring an authorized payment client.
Does Playground send a paid request?
Yes. After you sign in, Run sends a real API request using an active OpenAny API key. Charges follow the published API contract and use your shared balance. Selecting an implementation, editing inputs and viewing sample responses do not send requests.
Use OSV Vulnerability Details API with your agent
Inspect endpoint contracts and confirm availability and pricing before a paid call.