Indico has a missing access check in the event series management API
CVE-2026-28352GHSA-rfpp-2hgm-gp5v
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (indico 3.3.11), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
PyPI indico
- Affected
- < 3.3.11
- Fixed in
- 3.3.11
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-rfpp-2hgm-gp5v lists affected ranges: PyPI indico >=0 <3.3.11 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-rfpp-2hgm-gp5v lists affected ranges: PyPI indico >=0 <3.3.11
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 6.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
- EPSS
- CVE-2026-28352: 0.30% estimated exploitation activity in the next 30 days; percentile 22.70 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Impact The API endpoint used to manage event series is missing an access check, allowing unauthenticated/unauthorized access to this endpoint. The impact of this is limited to: - Getting the metadata (title, category chain, start/end date) for events in an existing series - Deleting an existing event series: This just removes the series metadata, ie (if enabled) the links between events in the same series and the lecture series number in the event title - Modifying an existing event series: Just like for deleting, it would only allow to toggle the metadata display. It could also be used to set an event title pattern for the series, but this is only used when cloning an event from that series. That this vulnerability does NOT allow unauthorized access to events (beyond the basic metadata mentioned above), nor any kind of tampering with user-visible data in events. Patches Developers should to update to Indico 3.3.11 as soon as possible. See the docs for instructions on how to update.…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from ghsa record GHSA-rfpp-2hgm-gp5v
- Revision 1 · created ·
Published from osv record GHSA-rfpp-2hgm-gp5v
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-28352 Advisory: Indico has a missing access check in the event series management API IDs: CVE-2026-28352, GHSA-rfpp-2hgm-gp5v Record: https://patchnext.com/advisories/cve-2026-28352 (revision 2, source checked 26 Oct 2026, 13:36 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 6.5) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: indico 3.3.11. A vendor fix does not mean a deployment is fixed. ## Affected components - PyPI indico: affected < 3.3.11; fixed in 3.3.11 ## Suggested inspection (read-only) - `python -m pip show indico`: prints the installed version. Run with the environment that serves production active. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on indico. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/GHSA-rfpp-2hgm-gp5v (OSV record GHSA-rfpp-2hgm-gp5v lists affected ranges: PyPI indico >=0 <3.3.11 (fixed)) - Verified: https://github.com/advisories/GHSA-rfpp-2hgm-gp5v (GitHub-reviewed advisory GHSA-rfpp-2hgm-gp5v lists affected ranges: PyPI indico >=0 <3.3.11) Commands are suggestions: review each one before running it.
Loading voting…