---
title: "Discussion on \"JWT Attack Lab — Part 8: Algorithm Confusion, and a Bug the Attack Uncovered By Accident\" | Hashnode"
description: "Discussion on \"JWT Attack Lab — Part 8: Algorithm Confusion, and a Bug the Attack Uncovered By Accident\". An RS256/HS256 confusion attack gets blocked by PyJWT itself — but the attempt exposes a real bug: an unhandled exception leaking a stack trace."
url: "https://hashnode.com/posts/jwt-attack-lab-part-8-algorithm-confusion/6a5b630ad64a6f3912c535f0"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [JWT Attack Lab — Part 8: Algorithm Confusion, and a Bug the Attack Uncovered By Accident](https://quietbytes.hashnode.dev/jwt-attack-lab-part-8-algorithm-confusion?utm_source=hashnode&utm_medium=feed)

An RS256/HS256 confusion attack gets blocked by PyJWT itself — but the attempt exposes a real bug: an unhandled exception leaking a stack trace.

Jul 18 · 5 min read · quietbytes.hashnode.dev  
Read the article

-   [#jwt](https://hashnode.com/tag/jwt)
-   [#appsec](https://hashnode.com/tag/appsec)
-   [#cryptography](https://hashnode.com/tag/cryptography)
-   [#pyjwt](https://hashnode.com/tag/pyjwt)
-   [#python](https://hashnode.com/tag/python)

## Written by

[Renukashree Murali](https://hashnode.com/@quietbytes)

@quietbytes · Chennai, India

  
[View profile](https://hashnode.com/@quietbytes)

Building defensively. Thinking privately.

Cybersecurity graduate focused into privacy engineering and IAM. I write about the projects I build - what worked, what broke, and what I'd do differently. 👾

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
