---
title: "Discussion on \"JWT Attack Lab — Part 7: When exp Isn't Actually Enforced Everywhere\" | Hashnode"
description: "Discussion on \"JWT Attack Lab — Part 7: When exp Isn't Actually Enforced Everywhere\". A valid, correctly-expiring JWT still slips through a second endpoint that forgot to check exp — and why the real fix isn't just flipping a flag."
url: "https://hashnode.com/posts/jwt-attack-lab-part-7-expiry-enforcement/6a5b2551a1568345def09b21"
---

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

Discussion

# [JWT Attack Lab — Part 7: When exp Isn't Actually Enforced Everywhere](https://quietbytes.hashnode.dev/jwt-attack-lab-part-7-expiry-enforcement?utm_source=hashnode&utm_medium=feed)

A valid, correctly-expiring JWT still slips through a second endpoint that forgot to check exp — and why the real fix isn't just flipping a flag.

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

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

## 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.
