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…

CVE-2026-30835: CWE-209: Generation of Error Message Containing Sensitive Information in parse-community parse-server

0
Medium
VulnerabilityCVE-2026-30835cvecve-2026-30835cwe-209
Published: Fri Mar 06 2026 (03/06/2026, 20:28:27 UTC)
Source: CVE Database V5
Vendor/Project: parse-community
Product: parse-server

Description

Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to versions 8.6.7 and 9.5.0-alpha.6, malformed $regex query parameter (e.g. [abc) causes the database to return a structured error object that is passed unsanitized through the API response. This leaks database internals such as error messages, error codes, code names, cluster timestamps, and topology details. The vulnerability is exploitable by any client that can send query requests, depending on the deployment's permission configuration. This issue has been patched in versions 8.6.7 and 9.5.0-alpha.6.

AI-Powered Analysis

AILast updated: 03/06/2026, 21:00:51 UTC

Technical Analysis

CVE-2026-30835 affects parse-community's parse-server, an open-source backend framework running on Node.js. The vulnerability is due to improper handling of malformed $regex query parameters, such as unbalanced brackets (e.g., [abc), which cause the underlying database to generate structured error objects. These error objects contain sensitive internal information including error messages, error codes, code names, cluster timestamps, and topology details. The parse-server API previously passed these error objects directly to clients without sanitization, resulting in an information disclosure vulnerability classified under CWE-209 (Generation of Error Message Containing Sensitive Information). Since the vulnerability is triggered by malformed queries, any client capable of sending queries to the parse-server can exploit it without authentication or user interaction, contingent on the server's permission configuration. This leakage can aid attackers in reconnaissance and facilitate further targeted attacks. The vulnerability affects all parse-server versions prior to 8.6.7 and 9.5.0-alpha.6, where the issue has been patched. The CVSS v4.0 base score is 6.9, reflecting a medium severity with network attack vector, low complexity, and no privileges or user interaction required.

Potential Impact

The primary impact of CVE-2026-30835 is unauthorized disclosure of sensitive internal database information through error messages. This information leakage can reveal database structure, error codes, cluster timestamps, and topology details, which attackers can leverage for reconnaissance to map the backend infrastructure and identify further vulnerabilities. While it does not directly allow code execution or data modification, the exposure of internal details increases the attack surface and can facilitate more sophisticated attacks such as injection, privilege escalation, or targeted exploitation of backend components. Organizations relying on parse-server for backend services risk exposing sensitive operational details to unauthenticated remote attackers, potentially undermining confidentiality and aiding in lateral movement within their infrastructure. The vulnerability's ease of exploitation and lack of required authentication make it a significant concern for any publicly accessible parse-server deployments.

Mitigation Recommendations

To mitigate CVE-2026-30835, organizations should immediately upgrade parse-server to version 8.6.7 or later, or 9.5.0-alpha.6 or later, where the vulnerability is patched. Additionally, implement strict input validation and sanitization on all query parameters, especially those involving regular expressions, to prevent malformed queries from reaching the database layer. Configure API permissions to restrict query capabilities to authenticated and authorized users only, minimizing exposure to unauthenticated clients. Employ web application firewalls (WAFs) or API gateways to detect and block suspicious malformed queries that could trigger error leaks. Monitor logs for unusual query patterns or error message disclosures indicative of exploitation attempts. Finally, review and harden database error handling to ensure internal details are never exposed in API responses, applying the principle of least privilege and secure error reporting practices.

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
GitHub_M
Date Reserved
2026-03-05T21:06:44.606Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 69ab3d0ec48b3f10ffd4f2dc

Added to database: 3/6/2026, 8:46:06 PM

Last enriched: 3/6/2026, 9:00:51 PM

Last updated: 3/7/2026, 12:48:46 AM

Views: 5

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 in Console -> Billing 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