Synapse pagination Denial of Service

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

6.9 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2026-45076: 0.37% estimated exploitation activity in the next 30 days; percentile 30.81 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact In federated rooms, malicious homeservers can craft room events in such a way that prevents Synapse from providing full history to paginating clients. Clients could therefore fail to display room history. Patches Update to Synapse 1.152.1 or later. Workarounds There are no known workarounds for this issue. Identifiers - ELEMENTSEC-2025-1636 For more information If you have any questions or comments about this advisory, please email us at security at element.io.

Published by the source

14 May 2026, 16:18 UTC

Last modified by the source

10 Sep 2026, 03:50 UTC

Source last checked

26 Oct 2026, 13:45 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-6qf2-7x63-mm6v

2. Revision 2 · amended · 25 Oct 2026

   Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-6qf2-7x63-mm6v

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-45076

Advisory: Synapse pagination Denial of Service
IDs: CVE-2026-45076, GHSA-6qf2-7x63-mm6v
Record: https://patchnext.com/advisories/cve-2026-45076 (revision 3, source checked 26 Oct 2026, 13:45 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: matrix-synapse 1.152.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI matrix-synapse: affected < 1.152.1; fixed in 1.152.1

## Suggested inspection (read-only)
- `python -m pip show matrix-synapse`: 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 matrix-synapse.
- 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-6qf2-7x63-mm6v (OSV record GHSA-6qf2-7x63-mm6v lists affected ranges: PyPI matrix-synapse >=0 <1.152.1 (fixed))
- Verified: https://github.com/advisories/GHSA-6qf2-7x63-mm6v (GitHub-reviewed advisory GHSA-6qf2-7x63-mm6v lists affected ranges: PyPI matrix-synapse >=0 <1.152.1)

Commands are suggestions: review each one before running it.