Skip to content
Applications

CVE-2026-55652

9.8
Critical
EPSS 0.62%Patch availableJul 16, 2026

Auth bypass via X-Forwarded-For allows attacker to obtain admin session tokens.

common questions

Is CVE-2026-55652 being exploited?

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

How severe is CVE-2026-55652?

CVE-2026-55652 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-55652?

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

What does CVE-2026-55652 affect?

CVE-2026-55652 affects Wekan < 9.46, Self-hosted Wekan instances, Meteor-based Wekan with HEADER_LOGIN_TRUSTED_IPS. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-55652?

Upgrade to Wekan 9.46+ or disable HEADER_LOGIN_TRUSTED_IPS; validate proxy X-Forwarded-For handling.

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

executive summary
technical analysis
affected
Wekan < 9.46Self-hosted Wekan instancesMeteor-based Wekan with HEADER_LOGIN_TRUSTED_IPS
impact

Client-supplied X-Forwarded-For trusted by server lets remote attacker obtain meteor_login_token for any user, including admins, enabling full account takeover and privileged actions.

action required

Immediate action required

affected versions
wekan wekan
  • affected< 9.46

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