---
title: "Discussion on \"Why Decoding a JWT Is Not Verifying It (And How Security Bugs Slip Through)\" | Hashnode"
description: "Discussion on \"Why Decoding a JWT Is Not Verifying It (And How Security Bugs Slip Through)\". Decoding a JWT only unmasks Base64URL strings. Here is how alg: none bypasses, algorithm confusion, and unverified claims slip into production."
url: "https://hashnode.com/posts/why-decoding-a-jwt-is-not-verifying-it-and-how-security-bugs-slip-through/6ac5eb3c2394c1780713a651"
---

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

Discussion

# [Why Decoding a JWT Is Not Verifying It (And How Security Bugs Slip Through)](https://devomnitools.hashnode.dev/why-decoding-a-jwt-is-not-verifying-it-and-how-security-bugs-slip-through?utm_source=hashnode&utm_medium=feed)

Decoding a JWT only unmasks Base64URL strings. Here is how alg: none bypasses, algorithm confusion, and unverified claims slip into production.

Oct 7 · 6 min read · devomnitools.hashnode.dev  
Read the article

-   [#security](https://hashnode.com/tag/security)
-   [#web-development](https://hashnode.com/tag/web-development)
-   [#javascript](https://hashnode.com/tag/javascript)
-   [#backend](https://hashnode.com/tag/backend)

## Written by

[Umair Rana](https://hashnode.com/@umairrana)

@umairrana · Karachi, Pakistan

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

Creator of DevOmniTools | Full-Stack & Systems Developer passionate about 100% client-side privacy & developer tooling.

Software Engineer &amp; Full-Stack Developer. Creator of DevOmniTools (free private in-browser developer utilities). Writing about web architecture, APIs, debugging, and production engineering.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
