CVE-2026-62418
Authenticated SSRF in Apache Syncope allowing server-side requests to internal services.
Is CVE-2026-62418 being exploited?
Not confirmed. CVE-2026-62418 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.47% probability of exploitation in the next 30 days.
How severe is CVE-2026-62418?
CVE-2026-62418 is rated High with a CVSS score of 8.1. 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-62418?
Yes. A fix has been recorded for CVE-2026-62418. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-62418 affect?
CVE-2026-62418 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-62418?
Upgrade to Apache Syncope 4.0.7 or 4.1.2 immediately
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated low-privilege SSRF permitting arbitrary server-side HTTP requests to internal services/APIs, risking data exposure and lateral movement.
Patch when possible
- 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.