How broadly exploitable is this vulnerability?

Exploitability depends on who can supply JWTs to the SSO endpoint. If external clients or integrated services can present arbitrary tokens, an attacker with network access to the login flow can forge tokens and gain access. In tightly isolated environments where token submission is heavily constrained, practical exploitability may be reduced but not eliminated.

Does an attacker need valid credentials or prior access?

No. The flaw resides in how tokens are validated, not how they are obtained. An attacker does not need a legitimate token to start from; they can construct a syntactically valid JWT from scratch with chosen claims and rely on the absence of signature verification to have it accepted.

What is the safest general fix pattern?

The safest pattern is to centralize JWT handling and require that every token pass both integrity and validity checks: validate the signature against a known key and expected algorithm, confirm issuer/audience constraints, and check time-based claims, failing closed on any discrepancy. Avoid custom ad-hoc validation and rely on library primitives that enforce these checks by default.

Severity:

CRITICAL RISK

(9.8)

Improper JWT Signature Verification (CWE-347) Enabling Broken Authentication (CWE-287) in Convoy SSO

CVE-2026-33746

Published:

Apr 2, 2026

Status:

Awaiting Analysis

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

NDV

Recent Vulnerabilities

CWE-77;CWE-78

HIGH RISK

HIGH

(7.3)

OS Command Injection (CWE-78) in Totolink A7100RU setGameSpeedCfg CGI Handler

Remote Code Execution on the Router

April 6, 2026

CWE-77;CWE-78

HIGH RISK

HIGH

(7.3)

OS Command Injection (CWE-78) in Totolink A7100RU setFirewallType Handler

Remote Code Execution on Router Firmware

April 6, 2026

Vulnerability Type

Category:

Broken Authentication / Improper Signature Verification

CWE:

CWE-287;CWE-347

Impact:

Authentication Bypass and Account Impersonation

Severity:

CRITICAL RISK

(9.8)

CVSS Version:

3.1

Vulnerability Type

Category:

Broken Authentication / Improper Signature Verification

CWE:

CWE-287;CWE-347

Impact:

Authentication Bypass and Account Impersonation

Severity:

CRITICAL RISK

(9.8)

CVSS Version:

3.1

Catch This CVE While Code Is Being Written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Get Started

Ship clean & secure code faster

START 14 DAYS FREE TRIAL

BOOK A DEMO

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Improper JWT Signature Verification (CWE-347) Enabling Broken Authentication (CWE-287) in Convoy SSO

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

Recent Vulnerabilities

HIGH RISK

HIGH

(7.3)

OS Command Injection (CWE-78) in Totolink A7100RU setGameSpeedCfg CGI Handler

HIGH RISK

HIGH

(7.3)

OS Command Injection (CWE-78) in Totolink A7100RU setFirewallType Handler

Vulnerability Type

Vulnerability Type

Vulnerability Type

Catch This CVE While Code Is Being Written

Ship clean & secure code faster

Product

Pricing

Company

Legal

Developers

Compare

Product

Pricing

Company

Legal

Developers

Compare

Product

Pricing

Company

Legal

Developers

Compare