Investigate in your agent.

Turn this advisory into a focused investigation. Ask your agent to check your project’s versions, explain the evidence, and suggest a compatible fix.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

Skip to content
Check your stack
CVE-2026-116163critical9.1

Parse Server 9.0.0 before 9.10.5-alpha.2 Authentication Bypass via AuthAdapter Subclasses

Impact

Parse Server versions 9.0.0 before 9.10.5-alpha.2 and before 8.6.102 contain an authentication bypass vulnerability. Attackers can supply arbitrary authData to authenticate. The validateSetUp, validateLogin, and validateUpdate methods of custom AuthAdapter subclasses are not called.

Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.

Affected packages

This source has no supported package-version data for matching. You can read the advisory here, but this record alone cannot power a dependency check.

Affected products

Vendor version evidence. Product records are separate from automatic dependency matching.

parse-community · VulnCheck

parse-server

2 ranges

Package identity

pkg:npm/parse-serverExplore parse-server →

Identity supplied by VulnCheck. Version matching requires compatible range evidence.

Compare with this publisher’s ranges. This does not inspect your installation.

affected

9.0.0 → before 9.10.5-alpha.2

semver versions

unaffected

9.10.5-alpha.2

semver versions

unknown

Other versions: unaffected

parse-community · VulnCheck

parse-server

2 ranges

Package identity

pkg:npm/parse-serverExplore parse-server →

Identity supplied by VulnCheck. Version matching requires compatible range evidence.

Compare with this publisher’s ranges. This does not inspect your installation.

affected

0 → before 8.6.102

semver versions

unaffected

8.6.102

semver versions

unknown

Other versions: unaffected

Original source description

Parse Server before 8.6.102 and 9.0.0 before 9.10.5-alpha.2 contains an authentication bypass because the validateSetUp, validateLogin, and validateUpdate methods of custom adapters subclassing AuthAdapter are never called, and an inherited default that accepts any authData is used instead. Attackers can supply arbitrary authData to sign up, link identities, log in as existing users, or skip custom additional authentication factors.

Inside the record

Evidence available

Package identity
Version evidence
Remediation guidance · not supplied
Weakness classification
Additional publishers

Describes the evidence in this view, not whether the product is safe.

Original records

CVE-2026-116163

View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.

cve.new JSON →

Underlying weaknesses

The source’s classification of what caused the vulnerability.

CWE-287 ↗

Improper Authentication

VulnCheck

Related →

Environment requirements

These conditions apply together as specified by the publisher. A matching product name alone does not establish exposure.

VulnCheck · platform conditions

Any condition may hold

Vulnerable product

cpe:2.3:a:parseplatform:parse-server:*:*:*:*:*:*:*:*

From (inclusive): 9.0.0

Before: 9.10.5-alpha.2

Vulnerable product

cpe:2.3:a:parseplatform:parse-server:*:*:*:*:*:*:*:*

Before: 8.6.102

Original applicability statements
[
  {
    "nodes": [
      {
        "operator": "OR",
        "negate": false,
        "cpeMatch": [
          {
            "vulnerable": true,
            "criteria": "cpe:2.3:a:parseplatform:parse-server:*:*:*:*:*:*:*:*",
            "versionStartIncluding": "9.0.0",
            "versionEndExcluding": "9.10.5-alpha.2"
          },
          {
            "vulnerable": true,
            "criteria": "cpe:2.3:a:parseplatform:parse-server:*:*:*:*:*:*:*:*",
            "versionEndExcluding": "8.6.102"
          }
        ]
      }
    ]
  }
]
Contributing organizations · 2
VulnCheck

Assigning organization

2026-10-25
CISA-ADP

Additional data publisher

2026-10-26

What changed

Follow changes
No substantive changes have been recorded here yet. History starts when cve.new observes a change after tracking is enabled; earlier edits are not reconstructed.

Large field values are marked as truncated previews. Original source snapshots remain retained.

References

2 sources