CVE-2026-24791
Public tokens bypass authorization on /api/v1/user self API, exposing private user resources.
Is CVE-2026-24791 being exploited?
Not confirmed. CVE-2026-24791 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.25% probability of exploitation in the next 30 days.
How severe is CVE-2026-24791?
CVE-2026-24791 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-24791?
Yes. A fix has been recorded for CVE-2026-24791. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-24791 affect?
CVE-2026-24791 affects Web applications with /api/v1/user self endpoints, APIs using public-only tokens, Custom user-management APIs. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-24791?
Revoke/rotate public tokens; enforce authZ checks; audit user endpoints; apply vendor patch when released.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Public-only tokens can access/modify private /api/v1/user 'self' endpoints, enabling unauthorized data access, account actions, and potential account takeover.
Immediate action required
- affected>= 1.22.3 and <= 1.26.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.