Privilege escalation via hard-coded JWT signing key
Published Feb 23, 2023 · Updated Mar 12, 2025
Hard-coded credentials in ThingsBoard 3.4.1 allow remote attackers with server or source access to gain elevated privileges. The security.jwt.tokenSigningKey setting defaults to the known static value thingsboardDefaultSigningKey, allowing attackers to create accepted JWTs. Exploitation requires obtaining the application configuration or source code; a forged token grants the privileges encoded in that token.
Summary
What happened
Hard-coded credentials in ThingsBoard 3.4.1 allow remote attackers with server or source access to gain elevated privileges. The security.jwt.tokenSigningKey setting defaults to the known static value thingsboardDefaultSigningKey, allowing attackers to create accepted JWTs. Exploitation requires obtaining the application configuration or source code; a forged token grants the privileges encoded in that token.
The record
- CVE
- CVE-2023-26462
- Published
- Feb 23, 2023
- Updated
- Mar 12, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-798, T1552.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 23, 2023CVE publishedPublication date reported by the CVE source.
- Mar 12, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo