CVE-PUBLISH-ADP(1)

💖 CVE-PUBLISH-ADP(1) 💖

okay bestie, welcome to the cve publish-adp manual — she lives in the cve publish-adp Manual family and she is literally the girl who adds or updates an ADP container in a CVE. no cap. let's get into it 🫶

---

✨ NAME ✨

cve-publish-adp — add or update an ADP container in a CVE... 🦋

---

✨ SYNOPSIS ✨

cve publish-adp [OPTIONS] CVE_ID

---

✨ DESCRIPTION ✨

so what she does is: add or update an ADP container in a CVE record for a published CVE ID. that's the whole vibe. 💅

⚠️ NOTE, and this one MATTERS bestie: a published ADP container cannot be removed — only updated with new data. so like… once she's in, she's in. periodt. 💀

you can hand her the ADP container as a string:

cve publish-adp CVE-2022-1234 -j '{"affected": [], "descriptions": [], "references": {}, ...}'

or you can pass it in a file:

cve publish-adp CVE-2022-1234 -f adp.json

and if you wanna know what properties a given ADP container of a CVE record actually needs? the schema is right here, go look, iykyk:

https://cveproject.github.io/cve-schema/schema/docs/

here's the tea tho 🍓 — because the CVE Services API only expects the ADP container contents of the full CVE v5 record, the data you pass to this command can specify just the attributes defined by the adpContainer subschema. no need to bring the whole record, she's not asking for all that. 🙈

---

✨ OPTIONS ✨

• -j, --adp-json TEXT — the JSON body of the ADP container to publish. drop it in as text, that's it. 🌸
• -f, --adp-json-file FILENAME — a file containing the JSON body of the ADP container to publish. same energy, just from a file bestie. 🎀
• --raw — print the response JSON. raw. unedited. iconic. 👑

---

and that's the whole page, gorgeous ✨ she's version 1.8.0, dated 2025-09-29, and she ate, no crumbs. go publish something slay 💖🦋🌈