What is CVE-2026-30949?

CVE-2026-30949 is a high-severity improper authentication vulnerability in parse-server (npm), affecting versions >= 9.0.0, < 9.5.2-alpha.5. It is fixed in 9.5.2-alpha.5, 8.6.18. The application does not adequately verify the identity of a user, device, or process before granting access.

Which versions of parse-server are affected by CVE-2026-30949?

parse-server (npm) versions >= 9.0.0, < 9.5.2-alpha.5 is affected.

Is there a fix for CVE-2026-30949?

Yes. CVE-2026-30949 is fixed in 9.5.2-alpha.5, 8.6.18. Upgrade to this version or later.

Is CVE-2026-30949 exploitable, and should I be worried?

Whether CVE-2026-30949 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2026-30949 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2026-30949?

Upgrade: parse-server to 9.5.2-alpha.5 or later, parse-server to 8.6.18 or later.

CVE-2026-30949 in parse-server | Intelligent Application Security

Q: Which versions of parse-server are affected by CVE-2026-30949?

parse-server (npm) versions >= 9.0.0, < 9.5.2-alpha.5 is affected.

Q: Is there a fix for CVE-2026-30949?

Yes. CVE-2026-30949 is fixed in 9.5.2-alpha.5, 8.6.18. Upgrade to this version or later.

Q: Is CVE-2026-30949 exploitable, and should I be worried?

Whether CVE-2026-30949 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2026-30949 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2026-30949?

Upgrade: parse-server to 9.5.2-alpha.5 or later, parse-server to 8.6.18 or later.

Summary

Workarounds

None.

References

GitHub security advisory: https://github.com/parse-community/parse-server/security/advisories/GHSA-48mh-j4p5-7j9v
Fix Parse Server 9: https://github.com/parse-community/parse-server/releases/tag/9.5.2-alpha.5
Fix Parse Server 8: https://github.com/parse-community/parse-server/releases/tag/8.6.18

Impact

The Keycloak authentication adapter does not validate the azp (authorized party) claim of Keycloak access tokens against the configured client-id. A valid access token issued by the same Keycloak realm for a different client application can be used to authenticate as any user on the Parse Server that uses the Keycloak adapter. This enables cross-application account takeover in multi-client Keycloak realms.

All Parse Server deployments that use the Keycloak authentication adapter with a Keycloak realm that has multiple client applications are affected.

The application does not adequately verify the identity of a user, device, or process before granting access. Typical impact: unauthorized access to functions or data reserved for authenticated parties.

Affected versions

parse-server (>= 9.0.0, < 9.5.2-alpha.5) parse-server (< 8.6.18)

Security releases

parse-server → 9.5.2-alpha.5 (npm) parse-server → 8.6.18 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

See it in your environment

Remediation advice

The fix replaces the userinfo HTTP call with local JWT verification and enforces azp claim validation against the configured client-id.

Frequently Asked Questions

What is CVE-2026-30949? CVE-2026-30949 is a high-severity improper authentication vulnerability in parse-server (npm), affecting versions >= 9.0.0, < 9.5.2-alpha.5. It is fixed in 9.5.2-alpha.5, 8.6.18. The application does not adequately verify the identity of a user, device, or process before granting access.
Which versions of parse-server are affected by CVE-2026-30949? parse-server (npm) versions >= 9.0.0, < 9.5.2-alpha.5 is affected.
Is there a fix for CVE-2026-30949? Yes. CVE-2026-30949 is fixed in 9.5.2-alpha.5, 8.6.18. Upgrade to this version or later.
Is CVE-2026-30949 exploitable, and should I be worried? Whether CVE-2026-30949 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2026-30949 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2026-30949?
- Upgrade parse-server to 9.5.2-alpha.5 or later
- Upgrade parse-server to 8.6.18 or later

Other vulnerabilities in parse-server

CVE-IDSeverityPackage summary

GHSA-97PR-9HGG-3P8RLowparse-server: parse-server: LiveQuery discloses object data to a subscriber across an ACL read-access change CVE-2026-55778Lowparse-server: parse-server: Stored XSS via non-standard file extension bypassing file upload extension blocklist CVE-2026-53726Mediumparse-server: parse-server: Relation `$relatedTo` query bypasses `protectedFields` and owning-object ACL CVE-2026-53725Mediumparse-server: parse-server: Endpoints `/login` and `/verifyPassword` disclose MFA secrets and protected fields…CVE-2026-53724Lowparse-server: parse-server: Stored XSS via trailing-dot filename bypassing file upload extension blocklist