How severe is GHSA-vr35-jm2f-8wg2?

GHSA-vr35-jm2f-8wg2 has a CVSS score of 4.9/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-vr35-jm2f-8wg2?

GHSA-vr35-jm2f-8wg2 affects the following packages: org.apache.syncope.core:syncope-core-provisioning-api (Maven), org.apache.syncope.core:syncope-core-provisioning-api (Maven), org.apache.syncope.core:syncope-core-provisioning-api (Maven). Ecosystems affected: Maven.

How do I fix GHSA-vr35-jm2f-8wg2?

No patched version of org.apache.syncope.core:syncope-core-provisioning-api has shipped for GHSA-vr35-jm2f-8wg2 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect GHSA-vr35-jm2f-8wg2 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.syncope.core:syncope-core-provisioning-api. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-vr35-jm2f-8wg2 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-vr35-jm2f-8wg2?

O3 pinpoints whether GHSA-vr35-jm2f-8wg2 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-vr35-jm2f-8wg2 actively exploited in the wild?

No public exploit code has been indexed for GHSA-vr35-jm2f-8wg2 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is GHSA-vr35-jm2f-8wg2?

GHSA-vr35-jm2f-8wg2 is classified as CWE-202 (CWE-202). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-vr35-jm2f-8wg2 published, and has it been updated?

GHSA-vr35-jm2f-8wg2 was published on May 26, 2026 and was last updated on June 30, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

GHSA-vr35-jm2f-8wg2

MEDIUM

Apache Syncope Vulnerable to Exposure of Sensitive Information Through Data Queries

Also known asCVE-2026-42797

Published

May 26, 2026

Updated

Jun 30, 2026

Affected

3 pkgs

Patched

2 / 3

Exploits

None indexed

Blast Radius

3 pkgs affected

☕org.apache.syncope.core:syncope-core-provisioning-api☕org.apache.syncope.core:syncope-core-provisioning-api☕org.apache.syncope.core:syncope-core-provisioning-api

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Exposure of Sensitive Information Through Data Queries vulnerability in Apache Syncope.

An administrator with adequate entitlements for Derived Schemas can create a malicious JEXL expression which allows any administrator with sufficient entitlements for User read to access User-related security-sensitive information.

This issue affects Apache Syncope: 3.0 through 3.0.16, 4.0 through 4.0.5, 4.1.0.

Users are recommended to upgrade to version 4.0.6 / 4.1.1, which fix this issue by further restricting the JEXL expression definition.

Affected Packages

3 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.syncope.core:syncope-core-provisioning-api`	≥ 3.0.0-M0	No fix
☕Maven	`org.apache.syncope.core:syncope-core-provisioning-api`	≥ 4.0.0-M0&&< 4.0.6	4.0.6
☕Maven	`org.apache.syncope.core:syncope-core-provisioning-api`	≥ 4.1.0-M0&&< 4.1.1	4.1.1

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.syncope.core:syncope-core-provisioning-api. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
No patched version of org.apache.syncope.core:syncope-core-provisioning-api has shipped for GHSA-vr35-jm2f-8wg2 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-vr35-jm2f-8wg2 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-vr35-jm2f-8wg2. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Exposure of Sensitive Information Through Data Queries vulnerability in Apache Syncope. An administrator with adequate entitlements for Derived Schemas can create a malicious JEXL expression which allows any administrator with sufficient entitlements for User read to access User-related security-sensitive information. This issue affects Apache Syncope: 3.0 through 3.0.16, 4.0 through 4.0.5, 4.1.0. Users are recommended to upgrade to version 4.0.6 / 4.1.1, which fix this issue by further restricting the JEXL expression definition.

O3 Security · Impact-Aware SCA

Is GHSA-vr35-jm2f-8wg2 in your dependencies?

O3 detects GHSA-vr35-jm2f-8wg2 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works