BugTraceAI CORE Ultra 27B Q6 needs about 24.7 GB of memory at Q6_K (a 22.1 GB file) with an 8K context window, so it fits on a 32 GB GPU. Longer context needs more: at 32K tokens the KV cache alone adds about 8.6 GB.
BugTraceAI CORE Ultra 27B Q6 – tooling model for bug bounty artifacts
BugTraceAI CORE Ultra 27B Q6 is a Qwen family model fine‑tuned on 2,541 real‑world bug bounty reports, CVE writeups, and offensive security research. It generates complete, executable artifacts such as Nuclei templates, Python PoC scripts, and CVSS scores. The model is optimized for tooling rather than general reasoning.
Good at
- Generating executable security artifacts
- Providing CVSS scores and bypass exploits
- Creating Nuclei templates and Python PoC scripts
Limits
- No vision support
- Requires ~24.7 GB VRAM at 8k context
- No mixture of experts
Best for
- Bug bounty report generation
- Security tool automation
- CVE PoC creation
Who it’s for. Security researchers, bug bounty hunters, and penetration testers who need ready‑to‑run artifacts. The model is ideal for teams that require precise, functional code outputs rather than explanatory text.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| Q6_K | 22.1 GB | 24.7 GB | Too big | Get file → |
The only available quant is Q6_K with a file size of 22.08 GB. It requires approximately 24.7 GB VRAM at 8k context. For lower VRAM budgets, a different quant would be needed, but none are listed.
What GPU do you need for BugTraceAI CORE Ultra 27B Q6?
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: no quant fits at an 8K context.
- 32 GB VRAM: the best quant that fits is Q6_K (22.1 GB file, about 24.7 GB in use).
Which BugTraceAI CORE Ultra 27B Q6 quant should you choose?
Q6_K (22.1 GB) is the middle option in this repository. Very close to the original quality for most uses, at a clearly larger size than 4-bit.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Source
Frequently asked questions about BugTraceAI CORE Ultra 27B Q6
How much VRAM does BugTraceAI CORE Ultra 27B Q6 need?
About 24.7 GB at Q6_K with an 8K context window. That is the 22.1 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 BugTraceAI CORE Ultra 27B Q6 on an 8 GB GPU?
Not at an 8K context. The smallest file needs about 24.7 GB, so you would need a larger GPU or CPU offloading.
What is the file size of BugTraceAI CORE Ultra 27B Q6 GGUF?
It depends on the quant: Q6_K is 22.1 GB.
What context length does BugTraceAI CORE Ultra 27B Q6 support?
The GGUF header lists a trained context length of 262,144 tokens (256K). 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 BugTraceAI CORE Ultra 27B Q6 GGUF?
The files are on Hugging Face in the BugTraceAI/BugTraceAI-CORE-Ultra-27B-Q6 repository. The download buttons on this page open the file on Hugging Face. ggufmodels.com does not host any model files.
What license does BugTraceAI CORE Ultra 27B Q6 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 model requires about 24.7 GB VRAM at 8k context.
Does this model support vision?
No, it does not support vision.
Was it fine‑tuned on bug bounty data?
Yes, it was fine‑tuned on 2,541 real‑world bug bounty reports and CVE writeups.