Unverified50% confidenceDecision RuleExact time
For JWT signing algorithms, HS256 or RS256 must be explicitly specified, and tokens with alg: none must be rejected, otherwise algorithm confusion attacks will occur.
1
Sources
50%
Confidence
Long-term
Relevance
10/13/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedJWT存在算法混淆攻击风险，例如将RS256篡改为HS25678% similarUnverifiedThe algorithm confusion attack between RS256 and HS256 can allow an attacker to use the public key as an HMAC secret to forge tokens that the server will accept as valid.70% similarUnverifiedThe Payload portion of a JWT is by default only Base64-encoded rather than encrypted, and therefore highly sensitive information such as passwords should not be placed in it.69% similarUnverifiedJWT is not encrypted by default (only signed), tokens are difficult to actively revoke once issued, and improper key management can lead to wholesale token forgery.68% similarUnverified企业级接口通常涉及多层安全机制：JWT用于无状态身份认证，OAuth 2.0处理第三方授权，HMAC-SHA256负责请求签名防篡改，AES/RSA用于敏感参数加密66% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1016440API
curl https://kongchang.com/api/v1/knowledge/claims/1016440MCP
get_claim(id=1016440)