# Parse Server OAuth2 adapter app ID validation sends wrong token to introspection endpoint

Advisory record · `GHSA-69xg-f649-w5g2`

- **Identifiers:** `GHSA-69xg-f649-w5g2` · `BIT-parse-2026-32269` · `CVE-2026-32269`
- **State:** Confirmed
- **Severity:** CVSS 6.3 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-683](https://cwe.mitre.org/data/definitions/683.html)
- **Tags:** [CWE-683](https://agentprime.io/advisories/tag/cwe-683.md)
- **Published:** 13 Mar 2026
- **Updated:** 16 Mar 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 13 Mar 2026, 20:02 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `parse-server` (npm): affected `>=9.0.0, <9.6.0-alpha.13 || >=8.0.2, <8.6.39`; fixed in `9.6.0-alpha.13`, `8.6.39`

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 6.3 Medium, CVSS 4.0: `CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0031, the 24th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the GitHub Advisory Database, published 13 Mar 2026. New records show when each source confirmed them.

## Sources

- [GitHub Advisory Database: GHSA-69xg-f649-w5g2](https://github.com/advisories/GHSA-69xg-f649-w5g2)
- [OSV: GHSA-69xg-f649-w5g2](https://osv.dev/vulnerability/GHSA-69xg-f649-w5g2)
- <https://github.com/parse-community/parse-server/security/advisories/GHSA-69xg-f649-w5g2>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-32269>
- <https://github.com/parse-community/parse-server>
- <https://github.com/parse-community/parse-server/releases/tag/8.6.39>
- <https://github.com/parse-community/parse-server/releases/tag/9.6.0-alpha.13>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-69xg-f649-w5g2>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-69xg-f649-w5g2/>. Everything for agents: <https://agentprime.io/llms.txt>.
