dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2025-68667

CRITICAL · 9.9 CVSS v4.0 Published 2025-12-23
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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 · unedited
Conduit is a chat server powered by Matrix. A vulnerability that affects a number of Conduit-derived homeservers allows a remote, unauthenticated attacker to force the target server to cryptographically sign arbitrary membership events. Affected products include Conduit prior to version 0.10.10, continuwuity prior to version 0.5.0, Grapevine prior to commit `9a50c244`, and tuwunel prior to version 1.4.8. The flaw exists because the server fails to validate the origin of a signing request, provided the event's state_key is a valid user ID belonging to the target server. Attackers can forge "leave" events for any user on the target server. This forcibly removes users (including admins and bots) from rooms. This allows denial of service and/or the removal of technical protections for a room (including policy servers, if all users on the policy server are removed). Attackers can forge "invite" events from a victim user to themselves, provided they have an account on a server where there is an account that has the power level to send invites. This allows the attacker to join private or invite-only rooms accessible by the victim, exposing confidential conversation history and room state. Attackers can forge "ban" events from a victim user to any user below the victim user's power level, provided the victim has the power level to issue bans AND the target of the ban resides on the same server as the victim. This allows the attacker to ban anyone in a room who is on the same server as the vulnerable one, however cannot exploit this to ban users on other servers or the victim themself. Conduit fixes the issue in version 0.10.10. continuwuity fixes the issue in commits `7fa4fa98` and `b2bead67`, released in 0.5.0. tuwunel fixes the issue in commit `dc9314de1f8a6e040c5aa331fe52efbe62e6a2c3`, released in 1.4.8. Grapevine fixes the issue in commit `9a50c2448abba6e2b7d79c64243bb438b351616c`. As a workaround, block access to the `PUT /_matrix/federation/v2/invite/{roomId}/{eventId}` endpoint using your reverse proxy.

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 confidence

Conduit Matrix homeserver fails to validate the origin of signing requests when the event's state_key is a valid user ID belonging to the target server, allowing a remote unauthenticated attacker to force cryptographic signing of arbitrary membership events. Attackers can forge leave events (removing users from rooms), invite events (joining private rooms as victim), and ban events (banning users on the same server).

MitigationUpgrade to Conduit 0.10.10, continuwuity 0.5.0, tuwunel 1.4.8, or Grapevine commit 9a50c244; alternatively, block PUT /_matrix/federation/v2/invite/{roomId}/{eventId} at the reverse proxy.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:L/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Conduit Matrix homeserver is running
    Identify the running process or check the installed package: ps aux | grep conduit, systemctl status conduit, or check container processes
    Affected if Conduit Matrix homeserver is NOT running (not affected)
  2. Check Conduit version
    Run 'conduit --version' or check the installed package version: dpkg -l matrix-conduit, rpm -q matrix-conduit, or inspect the Docker image tag
    Affected if Version is lower than 0.10.10 (for main Conduit), continuwuity lower than 0.5.0, tuwunel lower than 1.4.8, or Grapevine before commit 9a50c244
  3. Verify federation endpoint is accessible
    Check if PUT /_matrix/federation/v2/invite/{roomId}/{eventId} is exposed externally: curl -X PUT https://your-server/_matrix/federation/v2/invite/test/test -k (should return 400 or 404, not 401/403)
    Affected if Federation endpoint is publicly accessible without authentication (higher risk)
  4. Review server logs for unauthorized signing requests
    Check Conduit logs for entries containing 'signing' or 'invite' from unexpected origins: grep -i 'signing.*invite' /var/log/conduit.log or journalctl -u conduit | grep -i invite
    Affected if Logs show signing requests with state_key user IDs belonging to your server from untrusted origins

Your server is affected if it runs a Conduit-based Matrix homeserver version below 0.10.10 (or the other fixed versions) and has federation enabled, allowing unauthenticated remote attackers to forge membership events.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Upgrade to Conduit 0.10.10, continuwuity 0.5.0, tuwunel 1.4.8, or Grapevine commit 9a50c244; alternatively, block PUT /_matrix/federation/v2/invite/{roomId}/{eventId} at the reverse proxy.

Recommended fix High confidence

Conduit 0.10.10, continuwuity 0.5.0, tuwunel 1.4.8, or Grapevine commit 9a50c244

  1. 1. Identify which Conduit-derived homeserver software is running in your environment (Conduit, continuwuity, Grapevine, or tuwunel)
  2. 2. For Conduit: Upgrade to version 0.10.10 or later
  3. 3. For continuwuity: Upgrade to version 0.5.0 or later (which includes fixes from commits 7fa4fa98 and b2bead67)
  4. 4. For tuwunel: Upgrade to version 1.4.8 or later (which includes fix from commit dc9314de1f8a6e040c5aa331fe52efbe62e6a2c3)
  5. 5. For Grapevine: Update to commit 9a50c2448abba6e2b7d79c64243bb438b351616c or later
  6. 6. After upgrading, verify the server still functions correctly and test Matrix federation
  7. 7. As an additional mitigation, configure your reverse proxy to block unauthorized access to the PUT /_matrix/federation/v2/invite/{roomId}/{eventId} endpoint if upgrading is not immediately possible

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get the patch applied

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-68667 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-68667 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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