How broadly exploitable is this vulnerability?

This issue is broadly exploitable in any deployment where Parse Server is reachable by untrusted clients and Google authentication is enabled. An attacker does not need an existing account or special network position—only the ability to send crafted authentication requests.

Does exploitation require valid Google credentials or access to Google's infrastructure?

No. The attacker does not need valid Google credentials or access to Google's systems. They exploit the server's failure to verify token signatures by submitting a forged JWT with `alg: "none"` and a chosen Google account identifier in the payload.

What is the safest general fix pattern for this kind of issue?

The safest pattern is to enforce strict, server-side token verification: hardcode the expected algorithm and issuer, validate the audience, and rely on robust JWT/JWKS libraries that refuse tokens with unsupported algorithms or unknown keys. Avoid custom cryptographic or key-handling code wherever possible.

Severity:

CRITICAL RISK

(9.1)

Improper JWT Verification (CWE-345) in Parse Server Google Authentication

CVE-2026-27804

Published:

Feb 25, 2026

Status:

Analyzed

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-78

CRITICAL RISK

CRITICAL

(9.9)

Command Injection in MCP Stdio Configuration Validation (CWE-78) in WeKnora

Remote Code Execution

March 7, 2026

CWE-89

CRITICAL RISK

CRITICAL

(9.9)

SQL Injection via PostgreSQL Array/Row Expressions (CWE-89) in WeKnora Query Engine

Remote Code Execution via SQL Injection on the Database Server

March 7, 2026

Vulnerability Type

Category:

Authentication Bypass via Insecure Token Validation

CWE:

CWE-327;CWE-345

Impact:

Account Takeover / Authentication Bypass

Severity:

CRITICAL RISK

(9.1)

CVSS Version:

3.1

Vulnerability Type

Category:

Authentication Bypass via Insecure Token Validation

CWE:

CWE-327;CWE-345

Impact:

Account Takeover / Authentication Bypass

Severity:

CRITICAL RISK

(9.1)

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 Verification (CWE-345) in Parse Server Google Authentication

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

CRITICAL RISK

CRITICAL

(9.9)

Command Injection in MCP Stdio Configuration Validation (CWE-78) in WeKnora

CRITICAL RISK

CRITICAL

(9.9)

SQL Injection via PostgreSQL Array/Row Expressions (CWE-89) in WeKnora Query Engine

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