cve cwe qwen3 32b needs about 22.4 GB of memory at Q4_K_M (a 19.8 GB file) with an 8K context window, so it fits on a 24 GB GPU. Longer context needs more: at 32K tokens the KV cache alone adds about 8.6 GB.
Qwen3-32B fine‑tuned for CVE to CWE mapping
The model is a QLoRA fine‑tune of Qwen3-32B for mapping CVE descriptions to CWE IDs. It uses the Qwen3 architecture and retains 32.8B parameters. The fine‑tuned adapter is merged into the base and released in 16‑bit.
Good at
- CVE to CWE classification
- Reasoning and tool use
- Large context handling
Limits
- No vision support
- Requires 22.4 GB VRAM at 8 k context
- Apache‑2.0 license
Best for
- Security analysts mapping CVE to CWE
- Automated vulnerability triage
- Security tool integration
Who it’s for. Security professionals and researchers needing accurate CWE mapping from CVE text. The model is suitable for integration into security pipelines and analysis tools.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| Q4_K_M | 19.8 GB | 22.4 GB | Too big | Get file → |
The only available quant is Q4_K_M with a file size of 19.76 GB. It requires approximately 22.4 GB VRAM at 8 k context. For lower memory budgets, a non‑quantized 16‑bit version would be needed, but it is not provided in the file list.
What GPU do you need for cve cwe qwen3 32b?
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: no quant fits at an 8K context.
- 24 GB VRAM: the best quant that fits is Q4_K_M (19.8 GB file, about 22.4 GB in use).
Which cve cwe qwen3 32b quant should you choose?
Q4_K_M is the usual starting point for cve cwe qwen3 32b: it balances file size and quality well. Here it is a 19.8 GB file.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Source
Frequently asked questions about cve cwe qwen3 32b
How much VRAM does cve cwe qwen3 32b need?
About 22.4 GB at Q4_K_M with an 8K context window. That is the 19.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 cve cwe qwen3 32b on an 8 GB GPU?
Not at an 8K context. The smallest file needs about 22.4 GB, so you would need a larger GPU or CPU offloading.
What is the file size of cve cwe qwen3 32b GGUF?
It depends on the quant: Q4_K_M is 19.8 GB.
What context length does cve cwe qwen3 32b support?
The GGUF header lists a trained context length of 40,960 tokens (40K). The KV cache grows with the context you use: about 2.1 GB at 8K and 8.6 GB at 32K.
Where can I download cve cwe qwen3 32b GGUF?
The files are on Hugging Face in the exploitintel/cve-cwe-qwen3-32b repository. The download buttons on this page open the file on Hugging Face. ggufmodels.com does not host any model files.
What license does cve cwe qwen3 32b 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?
No. The Q4_K_M quant requires about 22.4 GB VRAM at 8 k context, which exceeds an 8 GB budget.
Does the model support vision tasks?
No. The model is a language model and has no vision capabilities.
What license applies to this model?
The model is released under the Apache‑2.0 license.