Skip to main content
Menu
CVEs

CVE

Radicale 3.3.0 before 3.8.3 Authorization Bypass via Stale Group Memberships

CVE-2026-130838

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

9.1CriticalCNA
Exploited
No known exploitation
Fix
Fixed in 3.8.3
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 3.8.3.

Published
Last modified
Reference
Last checked
36/100 · provisional
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
None on Exploit-DB, Metasploit or GitHub

Summary

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.

cve.now Index

36Pcve.now Index 36 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
  • Reach10/20Affects PyPI packages
  • Severity9.1/10CVSS 9.1
  • No patch0/5No signal

What would change the score

  • Would score about 81 if added to CISA KEV
  • Would score about 76 if CISA's SSVC rates exploitation active
  • Would score about 41 if advisories confirm default setups are exposed

Impact

  • Widely used

    radicale has 34.2k weekly downloads.Source: pypistats.org

What to do

  • Upgrade to a fixed version: 3.8.3.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

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"}.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • 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.

Evidence 7

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 5

  1. Patch
  2. Repository
  3. Repository
  4. Repository
  5. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-130838

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: cve.now feed data

Which versions are affected by CVE-2026-130838?

radicale (PyPI): from 3.3.0 before 3.8.3.Source: cve.now feed data

How do I fix CVE-2026-130838?

Upgrade to a fixed version: 3.8.3.Source: cve.now feed data

More CVEs