What is CVE-2026-105828?

CVE-2026-105828 is Parse Server 9.0.0 before 9.10.1-alpha.12 Class Name Disclosure via GraphQL Errors. The supplied enrichment data classifies it as Info Disclosure mapped to CWE-209 CWE-209.

Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Active exploitation is not confirmed from current sources for CVE-2026-105828. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

No. CVE-2026-105828 is not listed in CISA KEV in the supplied enrichment data. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

Is there a public exploit?

A public PoC is not confirmed from current sources for CVE-2026-105828. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with web/proxy/WAF logs, application logs, network IDS/IPS where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2026-105828 using CVSS 6.3, EPSS 0%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

The supplied mitigation guidance says to apply vendor patches and restrict external exposure until fixed. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

No public threat actor linkage is confirmed from current sources. Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Prioritize based on EPSS, PoC availability, and external exposure. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

mediumInfo Disclosure

CVE-2026-105828

CVE-2026-105828 — Parse Server 9.0.0 before 9.10.1-alpha.12 Class Name Disclosure via GraphQL Errors

Parse Server 8.2.2 before 8.6.92 and 9.0.0 before 9.10.1-alpha.12 contains an information disclosure vulnerability in which GraphQL validation error messages reveal hidden class names when public introspection is disabled. Unauthenticated attackers holding only the public Application Id can send crafted operations triggering unknown-argument or invalid enum value errors to learn pointer and relation target classes.

Published Oct 8, 2026Updated Oct 8, 2026Sources: NVD, parse-community (CNA), GitHub, GitHub Security Advisory, SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Unreported

no source claims exploitation

EPSS

ahead of 0% of scored CVEs

Affects

parse-community

4 products listed

CVSS base

6.3

medium

Remediation

The vendor's own words where we have them.

Upgrade parse-server to a fixed release (9.10.1-alpha.12). Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

Identify exposed assets running affected vendor/product/version combinations.
Prioritize based on EPSS, PoC availability, and external exposure.
Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Vendor	Product	Versions	Status
parse-community	parse-server	9.0.0 to < 9.10.1-alpha.12	Vulnerable
parse-community	parse-server	9.10.1-alpha.12	Patched
parse-community	parse-server	8.2.2 to < 8.6.92	Vulnerable
parse-community	parse-server	8.6.92	Patched

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Scope

Attack Complexity

Low

Attack Vector

Network

Privileges Req

None

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
6.3	CVSS 4.0	medium	—	—	parse-community (CNA)

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

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-209 · Generation of Error Message Containing Sensitive Information

Read Application Data

Mitigation: Ensure that error messages only contain minimal details that are useful to the intended audience and no one else. The messages need to strike the balance between being too cryptic (which can confuse users) or being too detailed (which may reveal more than intended). The messages should not reveal the methods that were used to determine the error. Attackers can use detailed information to refine or optimize their original attack, thereby increasing their chances of success. If errors must be captured in some detail, record them in log messages, but consider what could occur if the log messages can be viewed by attackers. Highly sensitive information such as passwords should never be saved to log files. Avoid inconsistent messaging that might accidentally tip off an attacker about internal state, such as whether a user account exists or not.

Weakness & attack patterns

CWE-209

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

CAPEC-463 · Padding Oracle Crypto AttackCAPEC-214 · Fuzzing for garnering J2EE/.NET-based stack traces, for application mappingCAPEC-7 · Blind SQL InjectionCAPEC-54 · Query System for InformationCAPEC-215 · Fuzzing and observing application log data/errors for application mapping

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

Prioritize edge telemetry for network-reachable parse-server.

web/proxy/WAF logsapplication logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

2026
Added · CVSS 3.1 6.3 (AV:N)
Oct 8, 2026 · NVD
Initial · CVE published
Oct 8, 2026 · NVD
Added · GHSA-c9g3-rrm7-955v published (medium)
Oct 8, 2026 · GitHub Security Advisory
CVE published by MITRE.
Oct 8, 2026 · SOCRadar CTI

References

4 on the record

github.com/parse-community/parse-server/security/advisories/GHSA-6m77-f8xr-f723
Exploit, Third Party Advisory, Mitre, NIST
www.vulncheck.com/advisories/parse-server-9.0.0-before-9.10.1-alpha.12-class-name-disclosure-via-graphql-errors
Vendor Advisory, Mitre, NIST
nvd.nist.gov/vuln/detail/CVE-2026-105828
NVD
github.com/advisories/GHSA-c9g3-rrm7-955v
Exploit, Third Party Advisory

Elsewhere on this site

parse-communityevery CVE for this vendor
Info Disclosuresame class
CWE-209other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record1

What should defenders know first?

CVE-2026-105828 is Parse Server 9.0.0 before 9.10.1-alpha.12 Class Name Disclosure via GraphQL Errors, a medium vulnerability affecting parse-server from parse-community. The current evidence does not list it in CISA KEV, and the exploit status is: Active exploitation is not confirmed from current sources for CVE-2026-105828. Public exploit evidence is: A public PoC is not confirmed from current sources for CVE-2026-105828. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 6.3 describes technical severity, while EPSS 0% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.