qwen35 9b pentest v5 needs about 7.2 GB of memory at Q4_K_M (a 5.6 GB file) with an 8K context window, so it fits on a 8 GB GPU. This repository has 3 quants, from 5.6 GB (Q4_K_M) to 17.9 GB (BF16). Longer context needs more: at 32K tokens the KV cache alone adds about 4.4 GB.
Qwen3.5‑9B fine‑tuned for penetration testing
qwen35 9b pentest v5 is a QLoRA fine‑tune of Qwen/Qwen3.5‑9B. It focuses on reasoning and tool use for security tasks. The model was trained on authorized‑penetration‑testing and defensive‑security instruction data.
Good at
- Security reasoning
- Tool invocation
- Penetration testing instructions
Limits
- No vision support
- License not specified
- Context limited to 262144 tokens
Best for
- Security analysts drafting attack plans
- Automated vulnerability assessment scripts
- Security training simulations
Who it’s for. Developers and security professionals who need a specialized LLM for penetration testing workflows. The model offers focused knowledge without multimodal capabilities.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| Q4_K_M | 5.6 GB | 7.2 GB | Tight | Get file → | |
| Q5_K_M | 6.5 GB | 8.1 GB | Too big | Get file → | |
| BF16 | 17.9 GB | 19.5 GB | Too big | Get file → |
For 8 GB VRAM, use Q4_K_M (file size 5.63 GB, estimated 7.2 GB memory at 8 k context). For 12 GB VRAM, Q5_K_M (6.47 GB, 8.1 GB memory) is suitable. BF16 requires 17.92 GB and 19.5 GB memory, suitable for high‑end GPUs.
What GPU do you need for qwen35 9b pentest v5?
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: the best quant that fits is Q4_K_M (5.6 GB file, about 7.2 GB in use).
- 12 GB VRAM: the best quant that fits is Q5_K_M (6.5 GB file, about 8.1 GB in use).
- 16 GB VRAM: the best quant that fits is Q5_K_M (6.5 GB file, about 8.1 GB in use).
- 24 GB VRAM: the best quant that fits is BF16 (17.9 GB file, about 19.5 GB in use).
Which qwen35 9b pentest v5 quant should you choose?
Q4_K_M is the usual starting point for qwen35 9b pentest v5: it balances file size and quality well. Here it is a 5.6 GB file.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Source
Frequently asked questions about qwen35 9b pentest v5
How much VRAM does qwen35 9b pentest v5 need?
About 7.2 GB at Q4_K_M with an 8K context window. That is the 5.6 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 qwen35 9b pentest v5 on an 8 GB GPU?
Yes, with Q4_K_M: the 5.6 GB file needs about 7.2 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of qwen35 9b pentest v5 GGUF?
It depends on the quant: Q4_K_M is 5.6 GB, Q5_K_M is 6.5 GB, BF16 is 17.9 GB.
What context length does qwen35 9b pentest v5 support?
The GGUF header lists a trained context length of 262,144 tokens (256K). The KV cache grows with the context you use: about 1.1 GB at 8K and 4.4 GB at 32K.
Where can I download qwen35 9b pentest v5 GGUF?
The files are on Hugging Face in the HRB25/qwen35-9b-pentest-v5 repository. The download buttons on this page open the file on Hugging Face. ggufmodels.com does not host any model files.
Can I run this model on 8 GB VRAM?
Yes, the Q4_K_M quantization requires about 7.2 GB of VRAM at 8 k context, which fits within an 8 GB GPU.
Does this model support vision inputs?
No, the model has no vision capabilities and is text‑only.
What is the context length of this model?
The trained context token limit is 262144 tokens.