Gpt Oss 20b Cve Cybersecurity needs about 16.7 GB of memory at Q4_K_M (a 15.8 GB file) with an 8K context window, so it fits on a 24 GB GPU. This repository has 18 quants, from 12.1 GB (Q3_K_S) to 41.9 GB (F16). Longer context needs more: at 32K tokens the KV cache alone adds about 1.6 GB.
GPT‑OSS‑20B fine‑tuned for CVE analysis and security recommendations
GPT‑OSS‑20B is a 20.9 billion‑parameter model specialized for CVE analysis. It uses DoRA fine‑tuning and provides structured security recommendations. The model supports tool usage and runs on llama.cpp.
Good at
- CVE vulnerability analysis
- Security recommendation generation
- Tool integration
Limits
- No vision support
- Large context required
- License is Apache‑2.0
Best for
- Security analysts reviewing CVE data
- Automated vulnerability report generation
- Tool‑enabled security workflows
Who it’s for. This model is intended for security professionals and researchers who need detailed CVE analysis and actionable recommendations. It is suitable for integration into security pipelines that support tool calls.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| Q3_K_S | 12.1 GB | 13.0 GB | Too big | Get file → | |
| Q2_K | 12.1 GB | 13.0 GB | Too big | Get file → | |
| TQ1_0 | 12.1 GB | 13.0 GB | Too big | Get file → | |
| TQ2_0 | 12.1 GB | 13.0 GB | Too big | Get file → | |
| Q4_0 | 12.1 GB | 13.0 GB | Too big | Get file → | |
| Q3_K_M | 12.9 GB | 13.8 GB | Too big | Get file → | |
| Q3_K_L | 13.3 GB | 14.2 GB | Too big | Get file → | |
| Q4_1 | 13.4 GB | 14.3 GB | Too big | Get file → | |
| Q5_0 | 14.6 GB | 15.5 GB | Too big | Get file → | |
| Q4_K_S | 14.7 GB | 15.6 GB | Too big | Get file → | |
| Q4_K_M | 15.8 GB | 16.7 GB | Too big | Get file → | |
| Q5_K_S | 15.9 GB | 16.8 GB | Too big | Get file → | |
| Q5_1 | 15.9 GB | 16.8 GB | Too big | Get file → | |
| Q5_K_M | 16.9 GB | 17.8 GB | Too big | Get file → | |
| Q6_K | 22.2 GB | 23.1 GB | Too big | Get file → | |
| Q8_0 | 22.3 GB | 23.2 GB | Too big | Get file → | |
| Q8_0 | 22.3 GB | 23.2 GB | Too big | Get file → | |
| F16 | 41.9 GB | 42.8 GB | Too big | Get file → |
For 8 GB VRAM, use Q3_K_S or Q2_K (file size 12.06 GB, estimated memory 13 GB). For 16 GB VRAM, Q4_K_M (15.81 GB, 16.7 GB). For 24 GB VRAM, Q6_K (22.19 GB, 23.1 GB).
What GPU do you need for Gpt Oss 20b Cve Cybersecurity?
These figures add the file size, an fp16 KV cache at an 8K context window (worked out from this model’s own header) and about 0.5 GB for the runtime. They are estimates, so leave a little headroom, and expect to use less context or a smaller quant if you are right at the limit.
- 4 GB VRAM: no quant fits at an 8K context.
- 6 GB VRAM: no quant fits at an 8K context.
- 8 GB VRAM: no quant fits at an 8K context.
- 12 GB VRAM: no quant fits at an 8K context.
- 16 GB VRAM: the best quant that fits is Q4_K_S (14.7 GB file, about 15.6 GB in use).
- 24 GB VRAM: the best quant that fits is Q8_0 (22.3 GB file, about 23.2 GB in use).
- 32 GB VRAM: the best quant that fits is Q8_0 (22.3 GB file, about 23.2 GB in use).
- 48 GB VRAM: the best quant that fits is F16 (41.9 GB file, about 42.8 GB in use).
Which Gpt Oss 20b Cve Cybersecurity quant should you choose?
Q4_K_M is the usual starting point for Gpt Oss 20b Cve Cybersecurity: it balances file size and quality well. Here it is a 15.8 GB file.
The Q8_0 file is 22.3 GB, about 1.4 times the size of Q4_K_M. It keeps the weights closer to the original, which only matters if you have the memory to spare.
If memory is tight, the smallest file is Q3_K_S at 12.1 GB, with the quality trade-offs that come with fewer bits. A reasonable choice when a 4-bit file will not fit, mostly on larger models. Quality loss is noticeable but often acceptable.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Frequently asked questions about Gpt Oss 20b Cve Cybersecurity
How much VRAM does Gpt Oss 20b Cve Cybersecurity need?
About 16.7 GB at Q4_K_M with an 8K context window. That is the 15.8 GB file, plus the KV cache and roughly 0.5 GB of runtime overhead. Smaller quants need less and longer context needs more.
Can I run Gpt Oss 20b Cve Cybersecurity on an 8 GB GPU?
Not at an 8K context. The smallest file needs about 13.0 GB, so you would need a larger GPU or CPU offloading.
What is the file size of Gpt Oss 20b Cve Cybersecurity GGUF?
It depends on the quant: Q3_K_S is 12.1 GB, Q2_K is 12.1 GB, TQ1_0 is 12.1 GB, TQ2_0 is 12.1 GB, Q4_0 is 12.1 GB, Q3_K_M is 12.9 GB and 12 more.
What context length does Gpt Oss 20b Cve Cybersecurity support?
The GGUF header lists a trained context length of 131,072 tokens (128K). The KV cache grows with the context you use: about 0.4 GB at 8K and 1.6 GB at 32K.
Where can I download Gpt Oss 20b Cve Cybersecurity GGUF?
The files are on Hugging Face in the piotreknow02/gpt-oss-20b-cve-cybersecurity-GGUF repository. The download buttons on this page open the file on Hugging Face. ggufmodels.com does not host any model files.
What license does Gpt Oss 20b Cve Cybersecurity use?
Hugging Face lists the license as apache-2.0. Licenses can differ between the quantized files and the original model, so check the repository and the base model before commercial use.
Can I run this model on 8 GB VRAM?
Use the Q3_K_S or Q2_K quantized files; they require about 13 GB of VRAM at 8 k context.
Does the model support image input?
No, the model does not have vision capabilities.
What license applies to this model?
The model is released under the Apache‑2.0 license.