CVE-RESERVE(1)

📦
version 1.8.0 · 5 versions
, in fedora 44, ubuntu resolute, ubuntu stonking

💖 CVE RESERVE(1) 💖

okay bestie, welcome to the cve reserve manual — this is the glow-up guide for reserving your very own CVE IDs, and honestly? it's giving main character energy. 🎀

✨ NAME ✨

cve-reserve — Reserve one or more CVE IDs. 🦋

✨ SYNOPSIS ✨

cve reserve [OPTIONS] [COUNT]

✨ DESCRIPTION ✨

So like, this is the whole vibe: you reserve one or more CVE IDs. 💅

COUNT is literally just how many CVEs you wanna reserve — and bestie, it defaults to 1. no cap.

Now here's where it gets fun. You can reserve CVE IDs one by one (and when you do that, the lowest IDs get reserved first, periodt) OR you can do it in batches of multiple IDs per single request. iconique behavior, honestly.

And when you're reserving multiple IDs, you get to choose how they're generated:

  • Sequentially (the default, the classic, the reliable queen 👑)
  • Non-sequentially — random IDs are selected from your CVE ID range 🎲

ngl if you want the full deep dive, go read the "Developer Guide to CVE Services API":

https://github.com/CVEProject/cve-services/wiki/Developer-Guide-to-CVE-Services-API#different-reservation-types

(it's the #different-reservation-types section specifically, iykyk 🔥)

✨ OPTIONS ✨

  • -r, --random — Reserve multiple CVE IDs non-sequentially. random era activated 🎲✨
  • -y, --year TEXT — Reserve CVE ID(s) for a given year. [default: (current year)] 🗓️
  • --raw — Print response JSON. the raw, unfiltered truth fr fr 💀

🌈 a lil sign-off 🌈

this page was brought to you by version 1.8.0, dated 2025-09-29, and yes it lives in the cve reserve Manual. go forth and reserve, bestie — you ate. 💖🫶🌸

📦 where this page comes from