---
id: CVE-2026-82232
title: >-
  Improper neutralization of special elements used in an SQL command ('SQL
  injection') vulnerability in Apache Syncope.




  An administrator with adequate entitlements can achieve execution of arbitrary
  SQL via stacked queries, leveraging u…
summary: >-
  Improper neutralization of special elements used in an SQL command ('SQL
  injection') vulnerability in Apache Syncope.




  An administrator with adequate entitlements can achieve execution of arbitrary
  SQL via stacked queries, leveraging u…
severity: critical
cvss: 9.8
cvssVector: 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'
cwe:
  - CWE-89
vendor: Apache Software Foundation
product: 'org.apache.syncope.core:syncope-core-persistence-jpa'
affected:
  - 'org.apache.syncope.core:syncope-core-persistence-jpa >= 3.0.0-M0 <= 3.0.16'
  - 'org.apache.syncope.core:syncope-core-persistence-jpa >= 4.0.0-M0 <= 4.0.7'
  - 'org.apache.syncope.core:syncope-core-persistence-jpa >= 4.1.0-M0 <= 4.1.2'
published: '2026-09-14'
updated: '2026-09-14'
sourceUpdated: '2026-09-14T20:58:48.430'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-82232'
references:
  - url: 'https://lists.apache.org/thread/v5zrdqcn0w0v4pk1d22ndt7frcrplo2b'
    label: security@apache.org
  - url: 'http://www.openwall.com/lists/oss-security/2026/09/14/21'
    label: af854a3a-2127-422b-91ae-364da2661108
tags:
  - nvd
  - cve.org
ssvc:
  exploitation: none
  automatable: 'yes'
  technicalImpact: total
  timestamp: '2026-09-14T19:47:58.170810Z'
ingestedAt: '2026-09-14T15:23:07.462Z'
epss: 0.00602
epssPercentile: 0.46561
---

## Overview

Improper neutralization of special elements used in an SQL command ('SQL injection') vulnerability in Apache Syncope.



An administrator with adequate entitlements can achieve execution of arbitrary SQL via stacked queries, leveraging unsanitized sort clauses for Task search.

This issue affects Apache Syncope: from 3.0.0-M0 through 3.0.16, from 4.0.0-M0 through 4.0.7, from 4.1.0-M0 through 4.1.2.



Users are recommended to upgrade to version 4.0.8 / 4.1.3, which fix this issue.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.