listmonk's active sessions remain valid after password reset and password change

Exploitation

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

CVSS

7.1 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N

EPSS

• CVE-2026-34828: 0.31% estimated exploitation activity in the next 30 days; percentile 24.15 (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.

Summary A session management vulnerability allows previously issued authenticated sessions to remain valid after sensitive account security changes, specifically password reset and password change. As a result, an attacker who has already obtained a valid session cookie can retain access to the account even after the victim changes or resets their password. This weakens account recovery and session security guarantees. I reproduced the issue on listmonk v6.0.0. Details The application updates account credentials successfully, but existing active sessions are not revoked afterward. This behavior was confirmed in two flows: 1. Password reset flow - A user resets their password through the forgot/reset flow. - The old password becomes invalid. - The new password works. - However, a session cookie issued before the reset remains valid and continues to authenticate successfully. 2. Authenticated password change flow - The same user logs in from two separate sessions. - Using session A,…

Published by the source

1 Apr 2026, 23:48 UTC

Last modified by the source

6 Apr 2026, 17:25 UTC

Source last checked

26 Oct 2026, 15:19 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-h5j9-cvrw-v5qh

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

# Patch Next advisory brief: CVE-2026-34828

Advisory: listmonk's active sessions remain valid after password reset and password change
IDs: CVE-2026-34828, GHSA-h5j9-cvrw-v5qh
Record: https://patchnext.com/advisories/cve-2026-34828 (revision 1, source checked 26 Oct 2026, 15:19 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/knadh/listmonk 1.1.1-0.20260329113754-1b5e8d38c778. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/knadh/listmonk: affected >= 1.1.1-0.20241028090858-319053dd7a90, < 1.1.1-0.20260329113754-1b5e8d38c778; fixed in 1.1.1-0.20260329113754-1b5e8d38c778

## Suggested inspection (read-only)
- Go github.com/knadh/listmonk: check the installed version with your package manager.

## 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 github.com/knadh/listmonk.
- 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://github.com/advisories/GHSA-h5j9-cvrw-v5qh (GitHub-reviewed advisory GHSA-h5j9-cvrw-v5qh lists affected ranges: Go github.com/knadh/listmonk >=1.1.1-0.20241028090858-319053dd7a90 <1.1.1-0.20260329113754-1b5e8d38c778)

Commands are suggestions: review each one before running it.