CVE-2026-14165
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 · uneditedAn Authorization Bypass Through User-Controlled Key vulnerability affecting Tuleap Enterprise Edition from 17.0 through 17.5 could allow an attacker to access data of other users without authorization.
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 confidenceThis is an Insecure Direct Object Reference (IDOR) vulnerability in Tuleap Enterprise Edition where an attacker can manipulate a user-controlled key (likely a database ID or reference parameter) to access sensitive data belonging to other users without proper authorization checks.
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
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Identify Tuleap installation and versionLocate the Tuleap installation directory and check the version file, typically found in /etc/tuleap or via the admin interface under 'System Information'. Run: grep -r 'version' /etc/tuleap/ 2>/dev/null or access /tuleap/admin/system_info.php via web browser.Affected if The installed version is Tuleap Enterprise Edition prior to 17.5.1
-
Confirm Enterprise Edition is in useCheck the Tuleap admin panel or configuration files for the edition type. Look for 'Enterprise' in license information at /tuleap/admin/ or check /etc/tuleap/basemap.php for edition indicators.Affected if The product is Tuleap Enterprise Edition (not Community Edition)
-
Identify endpoints handling user data referencesReview Tuleap's API endpoints and web routes that accept user-controlled object identifiers (such as user_id, document_id, artifact_id parameters). Check /usr/share/tuleap/src/ for route definitions.Affected if Endpoints accept numeric or sequential IDs as parameters without additional authorization validation
-
Audit access logs for IDOR indicatorsExamine Tuleap access logs in /var/log/tuleap/ for requests where user IDs or object references change unexpectedly between sequential requests from the same session, indicating potential unauthorized access to other users' data.Affected if Logs show requests accessing sequential or predictable IDs belonging to different users without corresponding authentication context changes
-
Test affected endpoints for authorization gapsUsing an authenticated low-privilege account, attempt to modify object reference parameters in API calls or form submissions to access data belonging to a different user. Compare response behavior when ID parameters are incremented or changed.Affected if Requests with manipulated ID parameters return data belonging to other users without proper authorization errors
A user is affected if running Tuleap Enterprise Edition version before 17.5.1 and the system exposes API endpoints accepting user-controlled object references without proper authorization validation.
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 dataApply the vendor patch for Tuleap Enterprise Edition 17.5.1 or later. In the meantime, restrict access to affected endpoints via network segmentation and monitor for unusual access patterns.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-14165 — 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-2026-14165 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