CVE-2025-67796
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 · uneditedIKUS Rdiffweb before 2.10.5 has an improper authorization flaw that allows an attacker with any valid or stolen access token to act as other users. The API does not enforce binding between the authenticated subject and the targeted user/tenant, so crafted requests can read or modify other users data and, in some cases, perform privileged actions. This issue may enable cross-tenant access. Fixed in version 2.10.6.
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 confidenceIKUS Rdiffweb before 2.10.5 contains an improper authorization vulnerability where the API fails to enforce binding between the authenticated subject and the targeted user/tenant. An attacker with any valid access token can read or modify other users' data and potentially perform cross-tenant attacks by crafting requests that target resources belonging to other users.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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.
-
Identify installed Rdiffweb versionRun 'rdiffweb --version' or check the web interface footer/summary page for the version number, or inspect the installed package (e.g., pip show rdiffweb, docker image tag, or rpm/deb package version)Affected if The version is lower than 2.10.5 (e.g., 2.10.4, 2.10.3, 2.9.x, etc.)
-
Confirm API module is enabledCheck the Rdiffweb configuration file (typically /etc/rdiffweb/rdiffweb.conf or ~/rdiffweb.conf) for API-related settings such as 'api_enabled', 'api_token_auth', or inspect if the /api/ endpoints are accessible on the serverAffected if The API feature is enabled and accessible on the instance
-
Verify API token-based authentication is configuredCheck if API tokens have been generated and are active. Look for 'api_token' entries in the configuration or database, or check the web interface under API settings or user profile pages for active tokensAffected if Any valid API tokens exist in the system
-
Inspect API access logs for cross-user requestsReview Rdiffweb logs (typically in /var/log/rdiffweb/ or accessible via the web interface) for API calls where the authenticated user differs from the target user/tenant identifier in the request path or parametersAffected if Logs show API requests accessing data belonging to users/tenants other than the token holder
-
Check user and tenant configurationExamine the Rdiffweb admin interface or user database to identify if multiple users or tenants (repositories with different owners) are configured in the systemAffected if Multiple users or tenants exist in the environment
If the installed Rdiffweb version is below 2.10.5 and the API is enabled with active tokens in a multi-user or multi-tenant environment, the vulnerability is present and exploitable.
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.
dbcve · scopedUpgrade to Rdiffweb version 2.10.6 or later to obtain the fixed API authorization logic that enforces user/tenant binding.
2.10.6
- Upgrade IKUS Rdiffweb to version 2.10.6 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-67796 — 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-2025-67796 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