# Vulnesis Advisory Database

The advisories Vulnesis publishes as GCVE Numbering Authority 110: identifiers, formats, index files, withdrawn records and disputes.

Vulnesis is [GCVE](https://gcve.eu) Numbering Authority (GNA) **110**, short name **VVD**. The advisories it issues are published in the public [Vulnesis Advisory Database](https://github.com/Vulnesis/advisory-database). Use it to consume Vulnesis's malicious-package and weakness findings in your own tools, or to check and dispute a record about a package you maintain.

Every record was reviewed before publication: approved by a Vulnesis analyst, or by a published approval rule after automated quality checks passed. Records and schemas are licensed under CC BY 4.0. Attribute "Vulnesis (GCVE GNA 110)".

## Identifiers

```text
GCVE-110-<FAMILY>-<YEAR>-<SEQUENCE>
```

For example, `GCVE-110-VULN-PYPI-2026-000499`.

| Family | Meaning |
|---|---|
| `NPM`, `PYPI`, `CARGO`, `GO`, `COMPOSER`, `PUB`, `MAVEN`, `NUGET`, `GEM`, `HEX`, `CRAN`, `JULIA`, `CONAN`, `AUR`, `BREW`, `APK`, ... | A malicious package found by the Vulnesis registry scanners |
| `VULN-<REGISTRY>` | A dual-use capability in a package: a weakness, with a CWE. **Not** a claim that the package is malicious |
| `XPL` | An exploit |
| `OSM`, `CERTCC`, `HSEC`, `ACSC`, `MAGEIA`, `TWILIO`, ... | An advisory from another feed that Vulnesis issued a GCVE identifier for. The upstream id is an alias. |

## Formats

Each record is published three ways, at the same relative path under each format directory:

```text
cvelistv5/<FAMILY>/<YEAR>/<BUCKET>/<ID>.json   CVE JSON 5.1 (CVE Record Format), with the GCVE id as cveId
osv/<FAMILY>/<YEAR>/<BUCKET>/<ID>.json         OSV 1.6
vulnetix/<FAMILY>/<YEAR>/<BUCKET>/<ID>.json    Vulnesis Advisory format
```

`<BUCKET>` groups sequences by thousand (`0xxx`, `21xxx`), as the CVE list does.

| Format | What to know |
|---|---|
| `cvelistv5` | The CVE Record Format, unchanged except that `cveMetadata.cveId` is a GCVE identifier. `assignerOrgId` is `4c0d58bb-5895-4ca8-94cf-1885b1c0f000`, a fixed UUID for GNA 110. `x_vulnetix_classification` and `x_vulnetix_aliases` are Vulnesis extensions. |
| `osv` | `database_specific.vulnetix` carries the classification, family and CWE ids. A malicious package follows the OSV malicious-packages convention: one `ECOSYSTEM` range introduced at `0`. An affected entry is listed only where an OSV ecosystem can be named correctly. |
| `vulnetix` | Everything Vulnesis asserts, including `classification` (`malware`, `weakness`, `exploit`, `vulnerability`) and the `review` block. Each record declares its `schema_version` and validates against `schemas/vulnetix-advisory-<schema_version>.schema.json`. Every schema version stays in `schemas/`. |

The `review` block says how a record was approved. `method` is `human_approved` or `human_edited` (a Vulnesis analyst approved it) or `auto_rule` (an approval rule matched it, named by `rule.id` and `rule.version`). No reviewer is named.

### Affected code

Where it is known, every format says which code is affected, not only which versions, so a scanner can tell whether the vulnerable code is in the installed package and whether a project reaches it.

| | Vulnesis | cvelistv5 | OSV |
|---|---|---|---|
| Modules or import paths | `affected[].code.modules` | `affected[].modules` | `affected[].ecosystem_specific.imports[].path` |
| Source files | `affected[].code.files` | `affected[].programFiles` | |
| Functions and methods | `affected[].code.routines[].name` | `affected[].programRoutines[].name` | `affected[].ecosystem_specific.imports[].symbols` |
| Tree-sitter queries | `detection.tree_sitter[]` | | |
| Lines a Vulnesis registry scanner matched | `detection.matched_lines[]` | | |

A tree-sitter query names its grammar (`language`), carries the query text with its predicates, and lists the `purls` it applies to. Run it over the installed package first (is the affected construct there?), then over the project (does it use it?).

## Index files

| File | Contents |
|---|---|
| `index/manifest.json` | Every record, with its classification, state, modification time and paths |
| `index/withdrawn.json` | Withdrawn records, with the path of each one's OpenVEX document where one was published |

```json
{
  "count": 60671,
  "gna": 110,
  "gna_short_name": "VVD",
  "records": [
    {
      "id": "GCVE-110-APK-2026-000001",
      "family": "APK",
      "classification": "malware",
      "state": "withdrawn",
      "modified": "2026-10-25T11:33:10Z",
      "schema_version": "1.2.0",
      "enriched": "unevaluated",
      "paths": {
        "cvelistv5": "cvelistv5/APK/2026/0xxx/GCVE-110-APK-2026-000001.json",
        "openvex": "openvex/APK/2026/0xxx/GCVE-110-APK-2026-000001.openvex.json",
        "osv": "osv/APK/2026/0xxx/GCVE-110-APK-2026-000001.json",
        "vulnetix": "vulnetix/APK/2026/0xxx/GCVE-110-APK-2026-000001.json"
      }
    }
  ]
}
```

`state` is `published` or `withdrawn`. Read `modified` to fetch only what changed since your last sync.

## Withdrawn records

A record Vulnesis rejects on review, or an identifier it withdraws, stays at its path so the identifier keeps resolving:

| Format | Marker |
|---|---|
| `cvelistv5` | `state: REJECTED` |
| `osv` | `withdrawn` |
| `vulnetix` | `state: withdrawn`, with `withdrawn_reason` |

When a record is withdrawn because the package is not affected (a false positive), Vulnesis also publishes an [OpenVEX](https://openvex.dev) 0.2.0 document at `openvex/<FAMILY>/<YEAR>/<BUCKET>/<ID>.openvex.json`. It holds one `not_affected` statement with a justification, for the package versions the record listed. The withdrawn record links to it in every format (Vulnesis reference tag `x_vex`, OSV reference type `EVIDENCE`, cvelistv5 `x_vulnetix_references`), and its index entry lists it as `paths.openvex`.

> [!CAREFUL] Treat withdrawn records as not affected
> A withdrawn record is still a file in the repository. A consumer that reads every file without checking `state` will raise alerts for packages Vulnesis has cleared. Filter on `state`, or read `index/withdrawn.json`.

## Disputing a record

If you maintain a package and a record about it is wrong, in particular if the package is wrongly listed as malicious, open an [issue](https://github.com/Vulnesis/advisory-database/issues/new) or email security@vulnes.is. To report privately, use email or the [Vulnerability Disclosure Policy](https://www.vulnes.is/vdp). Include:

- the GCVE identifier, for example `GCVE-110-VULN-PYPI-2026-000499`
- what is wrong: the classification, the versions, or the finding itself
- anything that shows it: a link to the code, a release, or a fix commit

Every dispute is read and decided by a person, who reviews the published packages and the tagged source for every version the record names. It ends in one or more of:

| Outcome | When | What you see |
|---|---|---|
| Withdrawn | The finding is wrong, for example a false positive, or code that does what it is documented to do | The record stays at its path as withdrawn, is listed in `index/withdrawn.json`, and gets an OpenVEX `not_affected` statement if the package is not affected |
| Reclassified | Something is wrong, but not what the record said | The same identifier is rewritten with the correct title, description, CWE, CVSS and affected versions, for example malware reclassified as a vulnerability |
| Fixed version added | The finding is right and you have released a fix | The affected range ends before your release, which is marked not affected. The fix commit and the release are added as references. |

While an issue is open, the record links to it in every format: a Vulnesis reference tagged `issue-tracking` and `x_disputed`, an OSV `DISCUSSION` reference, and in cvelistv5 an `issue-tracking` reference plus `containers.cna.tags: ["disputed"]`. The reply comes on the issue or by email, with what changed and why. Changes are published within 24 hours of the reply.

Pull requests that edit records are not merged. Records are corrected at the source and republished.

## In the Vulnesis API

The Vulnerability Database API lists GCVE issuances by month at `GET /v2/gcve/{year}/{month}`. See [Endpoint reference](/vdb-api/reference/endpoints.md).
