2026no writeups on CTFtime

squ1rrel CTF 2026

19 challenges with 25 published solutions between them. CTFtime lists this event but has no writeups filed against it, so it is absent from the index CTFtime feeds. These were found in public repositories instead. Each link is pinned to the commit it was read from.

The event on CTFtime

Web7

Reach data or functionality the application meant to keep from you - through its inputs, its tokens, or its trust in the client.

Solve it with:JWT decoder and signature verifier JWT alg=none bypass generator Web attack payload catalog JWT secret brute force Learn: Web attacks and session tokens

Uncategorised5

The upstream scoreboard did not say, so neither do we.

Solve it with:Cipher identifier and automatic decoder Learn: Recognising encodings

Misc3

Everything that fits no other box: esolangs, puzzles, scripting exercises, and the jail escapes that have not yet earned their own category.

Solve it with:Brainfuck and esolang decoder Cipher identifier and automatic decoder Regex tester with match offsets and capture groups Learn: Recognising encodings

Reverse engineering3

Work out what a compiled program does without its source, then work backwards from the check to the input that passes it.

Solve it with:Strings extractor for binaries and blobs WebAssembly disassembler Java .class disassembler Python .pyc bytecode disassembler Learn: Binary exploitation

Squ1rrel O Tron
2 official solutions
Squ1rrel O Tron 2
2 official solutions
Redactr
1 official solution

Binary exploitation1

Turn a memory-safety bug in a native binary into control of execution. Usually a stack overflow, a format string, or a heap primitive.

Solve it with:ROP gadget finder Shellcode assembler and library Cyclic pattern generator and offset finder Format string exploit builder Learn: Binary exploitation

Gaem
1 official solution

Other 2026 events