Security · JetBrains plugin
JWT Signature Verification Companion
FreeJWT / Auth Tooling
Warning icon on a jjwt Jwts.parser()...parse(token) call chain: jjwt's own parse method accepts a JWT whose signature is empty or doesn't match, even when a signing key has been configured on the parser. This is a documented real vulnerability class: CodeQL ships a dedicated "Missing JWT signature check" query for exactly this pattern, and jjwt's own issue tracker confirms it. The fix is easy
The gap it fixes
Jwts.parser().setSigningKey(key).build().parse(token) compiles fine, runs fine, and looks like it verifies the token — a signing key was even configured. It doesn't. An attacker can hand this code an unsigned or mismatched-signature JWT and it gets accepted, exactly the "algorithm confusion" / signature-bypass class of bug this plugin exists to catch before it ships.
Facts and pricing
- Category
- Security
- Pricing
- Free
- Platform
- IntelliJ-family
- First published
- 2026-08-25
- Marketplace ID
- #33813
- Repository
jwt-signature-verification-companion- Growth
- New listing
Related plugins
All Security pluginsLightweight, 100% local API-security checks for Java and Kotlin: hardcoded secrets, plaintext HTTP, TLS misconfiguration, and OWASP API Security Top 10 patterns.
Decode and verify JSON Web Tokens directly in a dedicated tool window: no browser round-trip, no data leaving the IDE.
A native, client-side viewer for X.509 certificates and keystores: decode a .pem, .crt, .cer, .der, .jks, .p12, or .pfx file without leaving the IDE.
Flags known-vulnerable dependency versions directly in pom.xml, build.gradle(.kts), package.json, and requirements.txt, matched against a vulnerability database bundled inside the plugin: zero account, zero token, zero network call, ever.
Download and star counts as of 2026-10-18, refreshed twice daily from the JetBrains Marketplace and GitHub APIs.