CVE-2025-26340
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA CWE-321 "Use of Hard-coded Cryptographic Key" in the JWT signing in Q-Free MaxTime less than or equal to version 2.11.0 allows an unauthenticated remote attacker to bypass the authentication via crafted HTTP requests.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceQ-Free MaxTime versions 2.11.0 and earlier use a hard-coded cryptographic key for signing JWT tokens (CWE-321). An unauthenticated remote attacker can craft malicious HTTP requests using this known key to forge valid JWT tokens and bypass authentication entirely.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 2.11.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify MaxTime installed versionCheck the application version through its admin interface, About page, or version file (commonly version.txt, manifest, or in the application binary metadata). Compare against <= 2.11.0.Affected if The installed version is 2.11.0 or earlier.
-
Determine if JWT authentication is in useReview the application configuration files (e.g., web.config, appsettings.json, application.yml) for JWT-related settings such as 'JwtBearer', 'TokenValidationParameters', 'IssuerSigningKey', or 'Authentication:Schemes:JwtBearer'.Affected if JWT-based authentication is configured and enabled in the MaxTime deployment.
-
Locate the JWT signing key configurationSearch configuration files and source code for the JWT signing key parameter. Look for properties like 'SecretKey', 'SigningKey', 'Key', or similar under JWT/token settings. Also inspect any embedded keys in compiled binaries or application startup code.Affected if A hard-coded string value (not a reference to environment variable or secure vault) is found assigned to the JWT signing key.
-
Verify key is hard-coded rather than externalizedExamine whether the identified signing key value is a literal string embedded in the code/config file, or whether it references an external source (environment variable, key vault, secrets manager). Check for patterns like direct string assignment versus environment variable lookups.Affected if The JWT signing key is a static, hard-coded string value present in configuration or code files.
A user is affected if they are running MaxTime version 2.11.0 or earlier AND the application uses JWT authentication with a hard-coded signing key found in configuration or code.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataReplace the hard-coded cryptographic key with a securely managed key (e.g., environment variable, secure vault) and implement JWT token rotation. Audit for any other hard-coded secrets in the codebase.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-26340 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-26340 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data