Approved changes feed: RSS · Atom
cpe:2.3:a:convoypanel:convoy:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Convoypanel (1c1cf3dd-8aef-5b4b-b367-e5d13c853302) |
|---|---|
| Product | Convoy (84cc8ae1-a32e-5695-a37b-0fb44a731151) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from purl2cpe mapping |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/convoypanel/panel |
purl2cpe | 2026-06-01 10:13:28.057076 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-33746 |
vulnerable | 2026-06-08 07:59:10.690252 |
Convoy: JWT Signature Verification Bypass Allows Authentication as Arbitrary Users
CRITICAL (9.8)
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.
Published: 2026-04-02T15:06:05.832Z
Updated: 2026-04-02T18:50:14.459Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.