TalkApplication · Nextcloud
CVE-2021-32676
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedNextcloud Talk is a fully on-premises audio/video and chat communication service. Password protected shared chats in Talk before version 9.0.10, 10.0.8 and 11.2.2 did not rotate the session cookie after a successful authentication event. It is recommended that the Nextcloud Talk App is upgraded to 9.0.10, 10.0.8 or 11.2.2. No workarounds for this vulnerability are known to exist.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceNextcloud Talk before versions 9.0.10, 10.0.8, and 11.2.2 contained a session fixation vulnerability in password-protected shared chats. The session cookie was not rotated after successful authentication, allowing an attacker who obtained a valid session cookie prior to authentication to potentially hijack the authenticated session.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
TalkApplication
< 9.0.10>= 10.0.0, < 10.0.8>= 11.2.0, < 11.2.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate installed Nextcloud Talk versionIn the Nextcloud web UI, navigate to Apps > Your apps > Talk, or check the version via occ command: 'occ app:list' and look for 'spreed' or 'talk' in the outputAffected if The displayed version is less than 9.0.10, or between 10.0.0 and 10.0.8 (exclusive), or between 11.2.0 and 11.2.2 (exclusive)
-
Verify Talk app is installed and enabledRun 'occ app:list | grep -i talk' or check in the Nextcloud admin interface under Apps > Your apps whether the Talk app is present and enabledAffected if Talk app is installed and enabled but version falls into the affected ranges listed above
-
Check if password-protected chat links are in useReview existing chat shares via the Talk UI or API: look for shared chats where a password was set, or check if the 'password protection' option was ever used when sharing conversation linksAffected if Password-protected shared chat links exist or were created in the affected version range
If the installed Nextcloud Talk version is 9.0.10, 10.0.8, 11.2.2 or later, you are not affected; otherwise, you are running a vulnerable version and should verify whether password-protected shared chats were used.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data9.0.1010.0.811.2.2
Upgrade Nextcloud Talk to version 9.0.10, 10.0.8, 11.2.2 or later. No workarounds exist; the patch must be applied.
Fix this in Talk
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-32676 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-32676 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data