CVE-2026-33163

MEDIUMNVD 6.56.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This medium-severity CVE scores 6.5 under NVD CVSS v3. EPSS exploit probability: 0.5% (41st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3

Also known asEUVD-2026-12994 (ENISA EUVD) · GHSA-5hmj-jcgp-6hff (GitHub Security Advisories)Source: ENISA EUVD

6.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 6.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.35 and 8.6.50, when a Parse.Cloud.afterLiveQueryEvent trigger is registered for a class, the LiveQuery server leaks protected fields and authData to all subscribers of that class. Fields configured as protected via Class-Level Permissions (protectedFields) are included in LiveQuery event payloads for all event types (create, update, delete, enter, leave). Any user with sufficient CLP permissions to subscribe to the affected class can receive protected field data of other users, including sensitive personal information and OAuth tokens from third-party authentication providers. The vulnerability was caused by a reference detachment bug. When an afterEvent trigger is registered, the LiveQuery server converts the event object to a Parse.Object for the trigger, then creates a new JSON copy via toJSONwithObjects(). The sensitive data filter was applied to the Parse.Object reference, but the unfiltered JSON copy was sent to clients. The fix in versions 9.6.0-alpha.35 and 8.6.50 ensures that the JSON copy is assigned back to the response object before filtering, so the filter operates on the actual data sent to clients. As a workaround, remove all Parse.Cloud.afterLiveQueryEvent trigger registrations. Without an afterEvent trigger, the reference detachment does not occur and protected fields are correctly filtered.

CVSS v3
6.5
EG Score
6.5MEDIUMmedium confidence
EG Risk
44
EG Risk 44/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity65% × 45%
Impact severity (EG Severity): CVSS 6.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
41st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (6.5): severity, escalated by confirmed exploitation. This CVE's 6.5 is its impact severity (EG Severity), not escalated.

EG Severity
6.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

March 18, 2026

Last Modified

June 17, 2026

Advisory Details (3)

Auto-updated Aug 6, 2026
Patch available. Sources: github_pr, github.
GitHub advisoryMentions a patch (unverified)

Protected fields leak via LiveQuery afterEvent trigger · Advisory · parse-community/parse-server · GitHub

https://github.com/parse-community/parse-server/security/advisories/GHSA-5hmj-jcgp-6hff
GitHub pull request Patch Available

fix: Protected fields leak via LiveQuery afterEvent trigger (GHSA-5hmj-jcgp-6hff)

Patch available: parse-community/parse-server 8.6.81 (PR #10233 merged 2026-03-17)

https://github.com/parse-community/parse-server/pull/10233
GitHub pull request Patch Available

fix: Protected fields leak via LiveQuery afterEvent trigger (GHSA-5hmj-jcgp-6hff)

Patch available: parse-community/parse-server 9.9.1-alpha.6 (PR #10232 merged 2026-03-17)

https://github.com/parse-community/parse-server/pull/10232

Vendor Advisories for CVE-2026-33163(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npmparse-server @ 9.6.0-alpha.35 (fixes >= 9.0.0, < 9.6.0-alpha.35)—ghsa
npmparse-server @ 8.6.50 (fixes < 8.6.50)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
parse-server—
  • 9.0.0 up to 9.6.0-alpha.35: fixed in 9.6.0-alpha.35
  • every version up to 8.6.50: fixed in 8.6.50
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 32× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 121 rows on record for this CVE, as 96 entries (4 repeats merged).

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 4 repeat rows among the latest 100 are merged into the row they repeat. The 21 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-13 16:52 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  2. 2026-11-12 16:33 UTCEPSS rescoreEPSS 0.4% · 39th percentile
  3. 2026-11-11 16:39 UTCEPSS rescoreEPSS 0.4% · 39th percentile
  4. 2026-11-10 16:43 UTCEPSS rescoreEPSS 0.4% · 39th percentile
  5. 2026-11-09 16:35 UTCEPSS rescoreEPSS 0.4% · 39th percentile
  6. 2026-11-08 16:39 UTCEPSS rescoreEPSS 0.4% · 39th percentile
  7. 2026-11-07 16:38 UTCEPSS rescoreEPSS 0.4% · 39th percentile
  8. 2026-11-06 16:37 UTCEPSS rescoreEPSS 0.4% · 39th percentile
  9. 2026-11-05 16:37 UTCEPSS rescoreEPSS 0.4% · 39th percentile
  10. 2026-11-04 16:35 UTCEPSS rescoreEPSS 0.4% · 39th percentile
  11. 2026-11-03 16:47 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  12. 2026-11-02 16:44 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  13. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  14. 2026-11-01 07:54 UTCGHSA enrichmentGHSA-5hmj-jcgp-6hff · GitHub severity HIGH
  15. 2026-11-01 07:54 UTCEchelonGraph re-scored
  16. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  17. 2026-10-30 21:25 UTCOSV refresh
  18. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  19. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  20. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  21. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  22. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  23. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  24. 2026-10-25 14:35 UTCEchelonGraph re-scored
  25. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
Show 71 more
  1. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  2. 2026-10-23 03:33 UTCEchelonGraph re-scored
  3. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  4. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  5. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  6. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  7. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  8. 2026-10-18 03:47 UTCEchelonGraph re-scored
  9. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  10. 2026-10-16 16:41 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  11. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  12. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  13. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  14. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  15. 2026-10-12 16:13 UTCEchelonGraph re-scored
  16. 2026-10-11 19:55 UTCEchelonGraph re-scored
  17. 2026-10-11 17:09 UTCEchelonGraph re-scored
  18. 2026-10-11 14:36 UTCEchelonGraph re-scored
  19. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  20. 2026-10-11 09:14 UTCOSV refresh
  21. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  22. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  23. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  24. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  25. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  26. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  27. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  28. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  29. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  30. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  31. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  32. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  33. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  34. 2026-09-26 00:26 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  35. 2026-09-21 21:45 UTCOSV refresh
  36. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  37. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  38. 2026-09-17 19:30 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  39. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  40. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  41. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  42. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  43. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  44. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  45. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  46. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  47. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  48. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  49. 2026-09-02 18:08 UTCOSV refresh
  50. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  51. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  52. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  53. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  54. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  55. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  56. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  57. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  58. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  59. 2026-08-24 14:17 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  60. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  61. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  62. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  63. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  64. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  65. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  66. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  67. 2026-08-16 11:14 UTCEchelonGraph re-scored
  68. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  69. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  70. 2026-08-14 07:22 UTCEchelonGraph re-scored
  71. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.4% · 34th percentile

Frequently asked(5)

What is CVE-2026-33163?
CVE-2026-33163 is a medium-severity vulnerability; its CVE record was published on March 18, 2026. 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.35 and 8.6.50, when a Parse.Cloud.afterLiveQueryEvent trigger is registered for a class, the LiveQuery server leaks protected fields and authData to all subscribers of that…
When was the CVE record for CVE-2026-33163 published?
The CVE record for CVE-2026-33163 was published on March 18, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of June 17, 2026; the record at its source may have been updated since.
Is CVE-2026-33163 actively exploited?
CVE-2026-33163 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (41st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-33163?
CVE-2026-33163 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-33163?
A fix for CVE-2026-33163 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-33163 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-33163

Explore →

Is Your Infrastructure Affected by CVE-2026-33163?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.