NVD / CVE Program· CNA GitHub_M

CVE-2021-32676: Session Fixation in Nextcloud Talk

Noroxi assessment

Priority: Monitor (action score 26/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.95% (FIRST EPSS); higher than 61.3% of all records.
Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
According to the record, no fixed version is available yet.

Low priority for now. Update when a fix is released; follow the vendor's advisory.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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

MediumCVSS 6.5 · v3.1—No exploit No fix recorded

Published: Jun 15, 2021
Updated: Jun 16, 2026
EPSS: 0.9% · 61th percentile
CWE: CWE-384

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 26 / 40 · 6.5 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.9%

CNA vs NVD score

NVD: 6.5
CNA · GitHub_M: 6.5; agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
nextcloud	talk	cpe:2.3:a:nextcloud:talk

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

nextcloud talkbefore 9.0.10
nextcloud talk10.0.0 and later · before 10.0.8
nextcloud talk11.2.0 and later · before 11.2.2

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

nextcloud security-advisories
- < 9.0.10, >= 10.0.0, < 10.0.8, >= 11.0.0, < 11.2.2affected

Same product

nextcloud: all records

Other highest-scoring records for the same primary product.

CVE-2020-8180A too lax check in Nextcloud Talk 6.0.4, 7.0.2 and 8.0.7 allowed a code injection when a not correctly sanitized talk command was added by a
40Plan
CVE-2023-39957Path traversal allows tricking the Talk Android app into writing files into it's root directory
31Monitor
CVE-2021-32689Nextcloud Talk not properly disassociating users from chats after account deletion
26Monitor

Published before and after this one in the same product

← EarlierCVE-2018-3781Aug 13, 2018 · A missing sanitization of search results for an autocomplete field in NextCloud Talk <3.2.5 could lead to a stored XSS requiring user-intera
21Monitor
← EarlierCVE-2019-15620Feb 4, 2020 · Improper access control in Nextcloud Talk 6.0.3 leaks the existance and the name of private conversations when linked them to another shared
10Monitor
Later →CVE-2021-39222Nov 15, 2021 · Nextcloud is an open-source, self-hosted productivity platform.
24Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope