CVE-REJECT(1)

💅 CVE-REJECT(1)

okay bestie, welcome to cve-reject — she's part of the cve reject Manual and she's here to help you ✨reject✨ things. Buckle up. 🎀

---

🌸 NAME 🌸

cve-reject — Reject a CVE record for a reserved or... 🫠

---

✨ SYNOPSIS ✨

cve reject [OPTIONS] CVE_ID

---

🦋 DESCRIPTION 🦋

So like, this whole thing rejects a CVE record for a reserved or published CVE ID. That's the vibe. 👑

If the CVE is already rejected, this action will update its record if one is supplied. No cap. And listen:

• A rejected CVE with a record can only be moved to the published state (see cve publish).
• A rejected CVE without a record can be moved to the reserved state.
• A published CVE can only be rejected with an accompanying record.
• Reserved CVEs can be rejected with or without a record.

⚠️ Note: rejecting a published CVE removes both the CNA and ADP data of that record. Gone. Poof. 💀 So maybe don't do that by accident, bestie.

---

The CVE reject record can be specified as a string, like:

cve reject CVE-2022-1234 -j '{"rejectedReasons": [{"lang": "en",
"value": "A reason."}]}'

Or passed in a file, if that's more your thing 🍓:

cve reject CVE-2022-1234 -f v5_reject_record.json

For information on the required properties in a given CVE JSON record, see the schema in:

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

Because the CVE Services API only expects the cnaRejectedContainer contents of the full record, the record you pass to this command can specify just that data, and not the full record. iykyk 😌

---

💖 OPTIONS 💖

• -j, --cve-json TEXT — JSON body of CVE record to reject. literally just hand it the JSON, queen. ✨
• -f, --cve-json-file FILENAME — File containing JSON body of CVE record to reject. for when your JSON is too iconic to fit on one line 🎀
• --raw — Print response JSON. raw. unfiltered. no makeup. 💅

---

that's the whole page, bestie — go reject something (responsibly) 🫶

cve reject Manual, version 1.8.0, dated 2025-09-29 — mwah, thanks for reading, ily, bye!! 💖🌈⭐