How severe is CVE-2026-36721?

CVE-2026-36721 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2026-36721 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (19th percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2026-36721?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

Does CVE-2026-36721 have an EU (EUVD) identifier?

Yes. CVE-2026-36721 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-35923.

When was CVE-2026-36721 published?

CVE-2026-36721 was published on 2026-06-09 and last updated on 2026-07-23.

CVE-2026-36721

CVE-2026-36721 is a critical-severity vulnerability with a CVSS 3.x base score of 9.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-347.

Key facts

Severity: Critical (CVSS 3.x base score 9.8)
EPSS exploit prediction: 0% (19th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2026-35923
Weakness: CWE-347
Published: 2026-06-09
Last modified: 2026-07-23

Description

A lack of cryptographic signature verification in the validateAccessToken function of bookcars v8.3 allows attackers to bypass authentication via a forged JWT token.

Frequently asked questions

What is CVE-2026-36721?: A lack of cryptographic signature verification in the validateAccessToken function of bookcars v8.3 allows attackers to bypass authentication via a forged JWT token.
How severe is CVE-2026-36721?: CVE-2026-36721 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2026-36721 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (19th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2026-36721?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
Does CVE-2026-36721 have an EU (EUVD) identifier?: Yes. CVE-2026-36721 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-35923.
When was CVE-2026-36721 published?: CVE-2026-36721 was published on 2026-06-09 and last updated on 2026-07-23.

References

https://github.com/CC-T-454455/Vulnerabilities/tree/master/bookcars/vulnerability-2

Other CWE-347 (Improper Verification of Cryptographic Signature) vulnerabilities

CVE-2026-5430 — Critical (CVSS 10.0): The JWT authentication mechanism accepts tokens signed with algorithms other than those explicitly configured or…
CVE-2026-56451 — Critical (CVSS 10.0): A vulnerability has been identified in Opcenter X (All versions < V2604). Affected applications do not properly…
CVE-2026-48558 — Critical (CVSS 10.0): SimpleHelp versions 5.5.15 and prior and 6.0 pre-release versions contain an authentication bypass vulnerability in the…
CVE-2023-25574 — Critical (CVSS 10.0): `jupyterhub-ltiauthenticator` is a JupyterHub authenticator for learning tools interoperability (LTI).…
CVE-2024-45409 — Critical (CVSS 10.0): The Ruby SAML library is for implementing the client side of a SAML authorization. Ruby-SAML in <= 12.2 and 1.13.0 <=…
CVE-2024-32962 — Critical (CVSS 10.0): xml-crypto is an xml digital signature and encryption library for Node.js. In affected versions the default…

Browse all CWE-347 (Improper Verification of Cryptographic Signature) vulnerabilities →