Skip to content
Applications

CVE-2026-61574

8.8
High
EPSS 0.36%Patch availableAug 19, 2026

authentik endpoint exposure leaks stored RDP/SSH/VNC credentials to any authenticated user.

common questions

Is CVE-2026-61574 being exploited?

Not confirmed. CVE-2026-61574 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.36% probability of exploitation in the next 30 days.

How severe is CVE-2026-61574?

CVE-2026-61574 is rated High with a CVSS score of 8.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-61574?

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

What does CVE-2026-61574 affect?

CVE-2026-61574 affects authentik < 2026.2.6, authentik < 2026.5.5, Managed RDP/SSH/VNC targets via authentik Remote Access Control. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-61574?

Upgrade to 2026.2.6 or 2026.5.5 immediately; rotate any stored credentials and audit access logs.

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

executive summary
technical analysis
affected
authentik < 2026.2.6authentik < 2026.5.5Managed RDP/SSH/VNC targets via authentik Remote Access Control
impact

Authenticated users can read stored RDP/SSH/VNC credentials and open remote sessions, enabling lateral movement and unauthorized access.

action required

Immediate action required

affected versions
goauthentik authentik
  • affected< 2026.2.6
  • affected>= 2026.5.0 and < 2026.5.5

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