Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…
EPSS 0.3%top 81%

CVE-2026-36721: n/a

0
Critical
VulnerabilityCVE-2026-36721cvecve-2026-36721
Published: 06/09/2026 (06/09/2026, 00:00:00 UTC)
Source: CVE Database V5

Description

A critical vulnerability in bookcars v8.3 exists due to the lack of cryptographic signature verification in the validateAccessToken function. This flaw allows attackers to bypass authentication by using a forged JWT token. The vulnerability is identified as CVE-2026-36721 and has a CVSS score of 9.8, indicating a high impact on confidentiality, integrity, and availability.

CVSS v3.1

Score 9.8critical

Attack Vector
Network
Attack Complexity
Low
Privileges Required
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

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 06/17/2026, 09:01:01 UTC

Technical Analysis

CVE-2026-36721 describes a vulnerability in bookcars version 8.3 where the validateAccessToken function does not perform cryptographic signature verification on JSON Web Tokens (JWT). This omission enables attackers to craft forged JWT tokens that bypass authentication controls, potentially granting unauthorized access to the system. The vulnerability is classified under CWE-347 (Improper Verification of Cryptographic Signature). No patch or official remediation guidance has been provided as of the published date.

Potential Impact

Successful exploitation of this vulnerability allows an unauthenticated attacker to bypass authentication mechanisms, leading to full compromise of confidentiality, integrity, and availability of the affected system. This can result in unauthorized access to sensitive data and system functions.

Mitigation Recommendations

Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, users should consider implementing additional access controls or monitoring to detect unauthorized access attempts involving JWT tokens. Avoid relying solely on the vulnerable validateAccessToken function for authentication.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
mitre
Date Reserved
2026-04-06T00:00:00.000Z
Cvss Version
null
State
PUBLISHED
Remediation Level
null

Threat ID: 6a2923fb8dd33fbd851290fd

Added to database: 06/10/2026, 08:44:43 UTC

Last enriched: 06/17/2026, 09:01:01 UTC

Last updated: 07/31/2026, 19:22:58 UTC

Views: 64

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses