An insecure authentication vulnerability in the /api/social-sign-in endpoint of bookcars v8.3 allows attackers to bypass authentication via a forged JWT token.
CVE-2026-36727
CRITICALPre-NVD 9.19.1—
EchelonGraph scoreHIGH confidence
Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-06-09. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.1; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
9.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 9.1Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.1
- EG Score
- 9.1(high)
- EPSS
- 28.5%
- KEV
- Not listed
Published
June 9, 2026
Last Modified
June 10, 2026
Advisory Details (1)
Auto-updated Jun 10, 2026🔬 Proof of concept available. No patch confirmed yet.
generic🟡 PoC Available
Vulnerabilities/bookcars/vulnerability-1 at master · CC-T-454455/Vulnerabilities · GitHub
https://github.com/CC-T-454455/Vulnerabilities/tree/master/bookcars/vulnerability-1Vendor Advisories for CVE-2026-36727(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Frequently asked(5)
What is CVE-2026-36727?
CVE-2026-36727 is a critical vulnerability published on June 9, 2026. An insecure authentication vulnerability in the /api/social-sign-in endpoint of bookcars v8.3 allows attackers to bypass authentication via a forged JWT token.
When was CVE-2026-36727 disclosed?
CVE-2026-36727 was first published in the National Vulnerability Database on June 9, 2026, with the most recent update on June 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-36727 actively exploited?
CVE-2026-36727 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 28.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-36727?
CVE-2026-36727 has a CVSS v3.1 base score of 9.1 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-36727?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-36727, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-36727
Is Your Infrastructure Affected by CVE-2026-36727?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.