I made an interesting discovery. Microsoft, HashiCorp, Apache and Spring have all had a kind of bug you wouldn't believe. It has been happening for a while now, and it's crazy. Let me share it.
I came across this while researching Kotlin and Spring Boot security, reading JetBrains' tutorial Secure Your APIs: OAuth2 and JWT for Beginners , by Mdu Sibisi. If you write Kotlin and Spring Boot and haven't set up Spring Security before, it walks you through the fix.
The problem: an API receives a JWT, verifies its signature and expiry, and lets the request in. It never checks the issuer ( iss , who created the token) or the audience ( aud , which app the token is for). So a real, properly signed token meant for a different app, or from an issuer you never meant to trust, still gets accepted.
Since 2023, at least five projects and platforms have accepted tokens that were genuinely signed but never meant for them.…