dbcve.org
CodecheckerApplication · Ericsson

CVE-2026-25660

CRITICAL · 9.8 CVSS v3.1 Published 2026-04-24
Fix available
A fix is available. Upgrade to 6.27.4 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
CodeChecker is an analyzer tooling, defect database and viewer extension for the Clang Static Analyzer and Clang Tidy. Authentication bypass occurs when the URL ends with Authentication with certain function calls.  This bypass allows assigning arbitrary permission to any user existing in CodeChecker. This issue affects CodeChecker: through 6.27.3.

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 · moderate confidence

CodeChecker versions through 6.27.3 contain an authentication bypass vulnerability where specially crafted URLs ending with 'Authentication' combined with certain function calls allow attackers to bypass authentication checks. This enables privilege escalation by assigning arbitrary permissions to any existing user in the system.

MitigationUpgrade CodeChecker to a version beyond 6.27.3 that addresses this vulnerability. Alternatively, implement additional server-side validation of authentication tokens and authorization checks independent of URL path patterns.

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
CodecheckerApplication
Affected:< 6.27.4

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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. Identify CodeChecker installation and version
    Run 'codechecker --version' or check the package manager for installed CodeChecker version (e.g., pip show codechecker, rpm -qi codechecker, or docker images). Compare the version number to the affected range (versions through 6.27.3).
    Affected if The installed version is 6.27.3 or lower, or any version less than 6.27.4.
  2. Verify CodeChecker web server is running
    Check if the CodeChecker web interface/service is running. Look for processes listening on the CodeChecker web port (default 8001) using commands like 'netstat -tlnp' or 'ss -tlnp', or check if the service is active via 'systemctl status codechecker' or similar service management tools.
    Affected if The CodeChecker web server is running and accessible.
  3. Confirm authentication is enabled in CodeChecker
    Review the CodeChecker configuration file (commonly located in the config directory where CodeChecker is installed, or in /etc/codechecker) for authentication settings. Check for 'authentication' or 'auth' enabled flags.
    Affected if Authentication is enabled and configured in the CodeChecker deployment.
  4. Inspect web server access logs for suspicious URL patterns
    Review CodeChecker web server access logs for requests ending with 'Authentication' (case-sensitive URL path ending). Look for patterns like '/Authentication' or paths containing 'Authentication' combined with permission modification endpoints.
    Affected if Any access logs contain requests to URLs ending with 'Authentication' that bypass normal authentication flow.

You are affected if CodeChecker version is less than 6.27.4 AND the web authentication interface is enabled and exposed.

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
Upgrade available Upgrade to 6.27.4 or later
Fixed in 6.27.4
Interim mitigation

Upgrade CodeChecker to a version beyond 6.27.3 that addresses this vulnerability. Alternatively, implement additional server-side validation of authentication tokens and authorization checks independent of URL path patterns.

Recommended fix Moderate confidence

CodeChecker 6.27.4

  1. 1. Backup your current CodeChecker configuration and database
  2. 2. Stop the CodeChecker server if it is running
  3. 3. Upgrade CodeChecker to version 6.27.4 or later using your package manager or installation method
  4. 4. Verify the upgrade completed successfully
  5. 5. Restart the CodeChecker server
  6. 6. Test that authentication is working correctly and that permission assignments are properly restricted
  7. 7. Verify that users can no longer assign arbitrary permissions to other users

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

Fix this in Codechecker Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-25660 — 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-2026-25660 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