Authentication bypass via hard-coded JWT signing key
Published Feb 12, 2025 · Updated Feb 17, 2025
Authentication bypass in Q-Free MAXTIME Suite 2.11.0 and earlier allows remote attackers to gain unauthorized access via crafted HTTP requests. The management web application signs JSON Web Tokens with a hard-coded cryptographic key, allowing attackers to forge accepted authentication material. No account is required, but exploitation requires crafted HTTP requests and user interaction; successful bypass grants unauthorized access to controller management functions.
Summary
What happened
Authentication bypass in Q-Free MAXTIME Suite 2.11.0 and earlier allows remote attackers to gain unauthorized access via crafted HTTP requests. The management web application signs JSON Web Tokens with a hard-coded cryptographic key, allowing attackers to forge accepted authentication material. No account is required, but exploitation requires crafted HTTP requests and user interaction; successful bypass grants unauthorized access to controller management functions.
The record
- CVE
- CVE-2025-26340
- Published
- Feb 12, 2025
- Updated
- Feb 17, 2025
- Vendor
- Q-Free
- Product
- MAXTIME Suite
- Classifications
- CWE-321, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 12, 2025CVE publishedPublication date reported by the CVE source.
- Feb 17, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=2.11.0
What conditions does exploitation require?
What is affected?
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