cve.bz

CVE-2026-33042 parseplatform parse-server: Improper Authentication

6.9 mediumEPSS 0.3%Fix available

Medium (6.9) in parseplatform parse-server. EPSS 0.3% estimated probability of exploitation activity in the next 30 days. Fixed in parse-server 8.6.49, 9.6.0-alpha.29.

On this page
Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to 9.6.0-alpha.29 and 8.6.49, a user can sign up without providing credentials by sending an empty `authData` object, bypassing the username and password requirement. This allows the creation of authenticated sessions without proper credentials, even when anonymous users are disabled. The fix in 9.6.0-alpha.29 and 8.6.49 ensures that empty or non-actionable `authData` is treated the same as absent `authData` for the purpose of credential validation on new user creation. Username and password are now required when no valid auth provider data is present. As a workaround, use a Cloud Code `beforeSave` trigger on the `_User` class to reject signups where `authData` is empty and no username/password is provided.

Severity

CVSS 4.0

6.9 medium
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

CVSS 3.1

5.3 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
EPSS
0.3% (unchanged from 0.3% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 27th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-03-20. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-287 Improper Authentication
OWASP Top 10
A07:2025 Authentication Failures
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-33042 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-33042?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-33042?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-33042 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
parseplatform:parse-serverbefore 8.6.49
parseplatform:parse-serverfrom 9.0.0 before 9.6.0
parseplatform:parse-server9.6.0:alpha1
parseplatform:parse-server9.6.0:alpha10
parseplatform:parse-server9.6.0:alpha11
parseplatform:parse-server9.6.0:alpha12
parseplatform:parse-server9.6.0:alpha13
parseplatform:parse-server9.6.0:alpha14
parseplatform:parse-server9.6.0:alpha15
parseplatform:parse-server9.6.0:alpha16
parseplatform:parse-server9.6.0:alpha17
parseplatform:parse-server9.6.0:alpha18
parseplatform:parse-server9.6.0:alpha19
parseplatform:parse-server9.6.0:alpha2
parseplatform:parse-server9.6.0:alpha20
parseplatform:parse-server9.6.0:alpha21
parseplatform:parse-server9.6.0:alpha22
parseplatform:parse-server9.6.0:alpha23
parseplatform:parse-server9.6.0:alpha24
parseplatform:parse-server9.6.0:alpha25
parseplatform:parse-server9.6.0:alpha26
parseplatform:parse-server9.6.0:alpha27
parseplatform:parse-server9.6.0:alpha28
parseplatform:parse-server9.6.0:alpha3
parseplatform:parse-server9.6.0:alpha4
parseplatform:parse-server9.6.0:alpha5
parseplatform:parse-server9.6.0:alpha6
parseplatform:parse-server9.6.0:alpha7
parseplatform:parse-server9.6.0:alpha8
parseplatform:parse-server9.6.0:alpha9

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-wjqw-r9x4-j59vnpmparse-server>=9.0.0 <9.6.0-alpha.299.6.0-alpha.29
GHSA-wjqw-r9x4-j59vnpmparse-server<8.6.498.6.49

Attack patterns (CAPEC)

  • CAPEC-22 Exploiting Trust in Client Likelihood: High · Severity: High
  • CAPEC-57 Utilizing REST's Trust in the System Resource to Obtain Sensitive Data Likelihood: Medium · Severity: Very High
  • CAPEC-94 Adversary in the Middle (AiTM) Likelihood: High · Severity: Very High
  • CAPEC-114 Authentication Abuse Severity: Medium
  • CAPEC-115 Authentication Bypass Severity: Medium
  • CAPEC-151 Identity Spoofing Likelihood: Medium · Severity: Medium
  • CAPEC-194 Fake the Source of Data Severity: Medium
  • CAPEC-593 Session Hijacking Likelihood: High · Severity: Very High
  • CAPEC-633 Token Impersonation Severity: Medium
  • CAPEC-650 Upload a Web Shell to a Web Server Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON