Security context
What an agent needs to avoid regressing past fixes and find the next vuln in this repo.
nats-io/jwt
main @ 8201723
6
Fixes
0
CVEs
HIGH
Peak severity
Highlights
Auth Bypass: 6 prior fixes. Scrutinize any change in this area.
v2/authorization_claims.go: most-fixed (2 issues). Treat as high-risk during review.
5 high-severity fixes in this history; regressions here are high-impact.
Recurring patterns
The bug types that recur here, drawn from past fixes, not open vulnerabilities.
Auth Bypass: Incomplete verification of key types and missing requirements for valid public user nkeys in authorization claims allowed malformed or unauthorized JWT signatures to bypass authentication controls.
Auth Bypass: Validation of NATS activation tokens within imports failed to escalate critical mismatches, such as token subjects and signing keys, to blocking errors, allowing invalid token ingestion.
Auth Bypass: Omission of strict constraints in external authorization configuration permitted defining allowed accounts without enforcing specified authorized users, bypassing authorization scope.