Unverified50% confidenceFactExact time
The root cause of GHSA-7hp6-4w63-5g45 is that the LiteLLM proxy uses the same key both to encrypt stored secrets and to issue session tokens, causing the ciphertext returned by an encryption request to become a valid administrator token.
1
Sources
50%
Confidence
Long-term
Relevance
10/13/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedThe commit hash for langchain-core 1.6.9 is fc7dc77, signed using GitHub's verified signature mechanism (GPG key ID: B5690EEEBB952194).68% similarUnverified1Password uses PBKDF2-HMAC-SHA256 combined with a proprietary Secret Key mechanism, in which a 128-bit local key and the master password jointly participate in derivation.66% similarUnverifiedTokenRouter's vendor keys are AES-encrypted at rest, decrypted in memory only at request time, and are never written to logs.65% similarUnverifiedUnless EXPERIMENTAL_UI_LOGIN is explicitly set to false, the LiteLLM proxy will attempt to decrypt any incoming token not starting with sk- as a UI session token; the GHSA-7hp6 advisory states that versions 1.87.0 to 1.90.x are likewise exploitable when it is set to true.62% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1017238API
curl https://kongchang.com/api/v1/knowledge/claims/1017238MCP
get_claim(id=1017238)