Advisory · CVE-2026-130838
Radicale stale group memberships let unauthenticated attackers read and write shared calendars
Radicale 3.3.0 before 3.8.3 has an authorization bypass flaw that lets unauthenticated attackers inherit group-based rights by reusing group memberships that are never reset between requests. Attackers can send credential-less requests after a group member logs in to read and write group-shared calendar and address book collections evaluated by the from_file rights backend; fixed in 3.8.3.
- Vendor
- Kozea
- Product
- Radicale
- Identifier / CWE
- CVE-2026-130838
CWE-488 - Action timing
- Immediate
Explain it like I’m five
Radicale checks which groups you belong to when you log in, then forgets to clear that list. Anyone who knocks afterwards is treated as a member of those groups and can read and change the shared calendars and address books.
- 01Group member logs in
A legitimate group member authenticates to Radicale.
- 02Memberships persist
Group memberships from that session are never reset between requests.
- 03Credential-less request follows
An unauthenticated attacker sends requests that inherit the stale group rights.
- 04Shared collections exposed
The attacker reads and writes group-shared calendar and address book collections.
What happened
Radicale 3.3.0 before 3.8.3 contains an authorization bypass vulnerability that allows unauthenticated attackers to inherit group-based rights by reusing group memberships never reset between requests. Attackers can send credential-less requests after a group member logs in to read and write group-shared calendar and address book collections evaluated by the from_file rights backend. The record rates it critical at CVSS 9.1 (v4.0).
What to do
- Upgrade Radicale to 3.8.3 or later.\n2. Restrict network access to Radicale while remediation is underway.\n3. Review access logs for unauthenticated requests to group-shared collections.\n4. Check shared calendars and address books for unexpected reads, writes, or deletions.\n5. Confirm the patched version is running.
Management note
An authorization check that only runs once per login is barely a check at all. Any Radicale server with group-shared collections should be patched first, then audited for quiet access.