Skip to content
Web

CVE-2026-57308

9.8
Critical
EPSS 0.83%Patch availableJul 22, 2026

Authenticated-admin SQL injection in Apache Syncope via unsanitized sort parameter.

common questions

Is CVE-2026-57308 being exploited?

Not confirmed. CVE-2026-57308 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.83% probability of exploitation in the next 30 days.

How severe is CVE-2026-57308?

CVE-2026-57308 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-57308?

Yes. A fix has been recorded for CVE-2026-57308. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-57308 affect?

CVE-2026-57308 affects Apache Syncope 3.0.0-M0 through 3.0.16, Apache Syncope 4.0.0-M0 through 4.0.6, Apache Syncope 4.1.0-M0 through 4.1.1. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-57308?

Upgrade to 4.0.7 or 4.1.2; restrict admin access and review DB logs.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Apache Syncope 3.0.0-M0 through 3.0.16Apache Syncope 4.0.0-M0 through 4.0.6Apache Syncope 4.1.0-M0 through 4.1.1
impact

Authenticated admin can inject stacked SQL via sort parameter to run arbitrary DB queries, enabling data exfiltration, tampering, or DB compromise.

action required

Immediate action required

affected versions
Apache Software Foundation Apache Syncope
  • affected>= 3.0.0-M0 and <= 3.0.16
  • affected>= 4.0.0-M0 and <= 4.0.6
  • affected>= 4.1.0-M0 and <= 4.1.1

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free