GPT OSS Cybersecurity 20B Merged 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 25 quants, from 0.0 GB to 22.2 GB (Q6_K). Longer context needs more: at 32K tokens the KV cache alone adds about 1.6 GB.
GPT OSS Cybersecurity 20B Merged – 20.9B‑parameter MoE model fine‑tuned for security tasks
GPT OSS Cybersecurity 20B Merged is a 20.9B‑parameter Mixture of Experts model. It was trained on 50,000 cybersecurity instruction‑response pairs and focuses on threat analysis, incident response, and vulnerability assessment. The model is available in GGUF format for efficient deployment.
Good at
- Threat classification
- Incident response guidance
- Vulnerability assessment
Limits
- Requires 40GB+ VRAM for BF16 inference
- No vision support
- License is apache‑2.0
Best for
- Security analysts reviewing alerts
- Automated incident response scripts
- Malware analysis pipelines
Who it’s for. Security teams and researchers needing a large‑scale, expert‑based model for cybersecurity workflows. The model is suitable for environments with high‑end GPUs or for quantized deployment on lower‑end hardware.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| — | 0.0 GB | 0.9 GB | Fits | Get file → | |
| IQ1_M | 12.0 GB | 12.9 GB | Too big | Get file → | |
| IQ1_S | 12.0 GB | 12.9 GB | Too big | Get file → | |
| IQ2_XXS | 12.0 GB | 12.9 GB | Too big | Get file → | |
| IQ2_XS | 12.0 GB | 12.9 GB | Too big | Get file → | |
| Q3_K_S | 12.1 GB | 13.0 GB | Too big | Get file → | |
| IQ2_M | 12.1 GB | 13.0 GB | Too big | Get file → | |
| IQ2_S | 12.1 GB | 13.0 GB | Too big | Get file → | |
| IQ3_S | 12.1 GB | 13.0 GB | Too big | Get file → | |
| IQ3_XS | 12.1 GB | 13.0 GB | Too big | Get file → | |
| IQ3_XXS | 12.1 GB | 13.0 GB | Too big | Get file → | |
| Q2_K | 12.1 GB | 13.0 GB | Too big | Get file → | |
| IQ4_XS | 12.1 GB | 13.0 GB | Too big | Get file → | |
| MXFP4_MOE | 12.1 GB | 13.0 GB | Too big | Get file → | |
| Q2_K_S | 12.1 GB | 13.0 GB | Too big | Get file → | |
| Q4_0 | 12.1 GB | 13.1 GB | Too big | Get file → | |
| IQ3_M | 12.2 GB | 13.1 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 → | |
| 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_K_M | 16.9 GB | 17.8 GB | Too big | Get file → | |
| Q6_K | 22.2 GB | 23.1 GB | Too big | Get file → |
For 8GB VRAM, use Q4_0 (file size 12.15GB, estimated memory 13.1GB) or lower‑bit IQ quants if available. For 16GB VRAM, Q4_K_M (15.81GB, 16.7GB) or Q5_K_S (15.89GB, 16.8GB) are suitable. For 32GB VRAM, Q6_K (22.19GB, 23.1GB) provides the full model with minimal quantization loss.
What GPU do you need for GPT OSS Cybersecurity 20B Merged?
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: the best quant that fits is the main file (0.0 GB file, about 0.9 GB in use).
- 6 GB VRAM: the best quant that fits is the main file (0.0 GB file, about 0.9 GB in use).
- 8 GB VRAM: the best quant that fits is the main file (0.0 GB file, about 0.9 GB in use).
- 12 GB VRAM: the best quant that fits is the main file (0.0 GB file, about 0.9 GB in use).
- 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 Q6_K (22.2 GB file, about 23.1 GB in use).
Which GPT OSS Cybersecurity 20B Merged quant should you choose?
Q4_K_M is the usual starting point for GPT OSS Cybersecurity 20B Merged: it balances file size and quality well. Here it is a 15.8 GB file.
If memory is tight, the smallest file is the first one in the table at 0.0 GB, with the quality trade-offs that come with fewer bits.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Source
Frequently asked questions about GPT OSS Cybersecurity 20B Merged
How much VRAM does GPT OSS Cybersecurity 20B Merged 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 Cybersecurity 20B Merged on an 8 GB GPU?
Yes, with the smaller files: the 0.0 GB file needs about 0.9 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of GPT OSS Cybersecurity 20B Merged GGUF?
It depends on the quant: file is 0.0 GB, IQ1_M is 12.0 GB, IQ1_S is 12.0 GB, IQ2_XXS is 12.0 GB, IQ2_XS is 12.0 GB, Q3_K_S is 12.1 GB and 19 more.
What context length does GPT OSS Cybersecurity 20B Merged 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 Cybersecurity 20B Merged GGUF?
The files are on Hugging Face in the mradermacher/GPT-OSS-Cybersecurity-20B-Merged-i1-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 Cybersecurity 20B Merged 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?
The smallest quantized version requires 13.1GB of VRAM at 8k context, so 8GB VRAM is insufficient for full inference.
Does the model support vision tasks?
No, the model is purely text‑based and has no vision capabilities.
What license applies to this model?
The model is released under the apache‑2.0 license.