dbcve.org
ConvoyApplication · Convoypanel

CVE-2026-33746

CRITICAL · 9.8 CVSS v3.1 Published 2026-04-02
Fix available
A fix is available. Upgrade to 4.5.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Convoy is a KVM server management panel for hosting businesses. From version 3.9.0-beta to before version 4.5.1, the JWTService::decode() method did not verify the cryptographic signature of JWT tokens. While the method configured a symmetric HMAC-SHA256 signer via lcobucci/jwt, it only validated time-based claims (exp, nbf, iat) using the StrictValidAt constraint. The SignedWith constraint was not included in the validation step. This means an attacker could forge or tamper with JWT token payloads — such as modifying the user_uuid claim — and the token would be accepted as valid, as long as the time-based claims were satisfied. This directly impacts the SSO authentication flow (LoginController::authorizeToken), allowing an attacker to authenticate as any user by crafting a token with an arbitrary user_uuid. This issue has been patched in version 4.5.1.

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 confidence

The JWTService::decode() method in Convoy validates time-based claims (exp, nbf, iat) but omits the SignedWith cryptographic signature constraint, allowing attackers to forge JWT tokens by modifying claims like user_uuid and authenticate as any user via the SSO flow.

MitigationUpgrade Convoy to version 4.5.1 or later which includes the patched JWTService::decode() method with proper signature verification.

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
ConvoyApplication
Affected:< 4.5.1

CVSS 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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Convoypanel Convoy version
    Locate the installed Convoypanel version number in the system configuration, about page, or package manager
    Affected if The installed version is below 4.5.1
  2. Determine if JWT authentication is active
    Inspect the Convoypanel configuration files or admin panel to see if JWT-based authentication is enabled for user logins
    Affected if JWT authentication is enabled and the deployed version is below 4.5.1
  3. Locate JWTService implementation
    Search the Convoypanel codebase for the JWTService class and its decode() method
    Affected if The JWTService::decode() method exists and processes tokens without enforcing SignedWith validation
  4. Inspect LoginController authorizeToken flow
    Examine the LoginController::authorizeToken method to verify it relies on JWT tokens for user authentication
    Affected if The authorizeToken flow uses JWT tokens from JWTService::decode() and version is below 4.5.1

A Convoypanel Convoy installation below version 4.5.1 with JWT-based SSO authentication enabled is vulnerable to forged token authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 4.5.1 or later
Fixed in 4.5.1
Interim mitigation

Upgrade Convoy to version 4.5.1 or later which includes the patched JWTService::decode() method with proper signature verification.

Recommended fix High confidence

4.5.1

  1. 1. Backup the Convoy application database and configuration files before proceeding with the upgrade
  2. 2. Check the currently installed Convoy version (e.g., via command line or admin panel)
  3. 3. Upgrade Convoy to version 4.5.1 using your package manager or installation method (e.g., composer update, docker pull, or apt/yum upgrade depending on your setup)
  4. 4. After upgrade, clear any cached JWT tokens or sessions
  5. 5. Verify the upgrade was successful by checking the version number
  6. 6. Test the authentication flow to confirm JWT signature validation is now working properly

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Convoy Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-33746 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-33746 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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