# CVE-2026-25660: Authentication bypass for certain API calls

> Attackers can bypass authentication to assign arbitrary permissions to any user in CodeChecker, leading to privilege escalation.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:P/S:N/AU:Y/R:U/V:C/RE:M/U:Red`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Apr 2026
- **Updated:** 24 Apr 2026
- **Also known as:** GHSA-4v9x-cqc5-j645, PYSEC-2026-317

## What is CVE-2026-25660?

CVE-2026-25660 is a critical authentication bypass vulnerability in Ericsson CodeChecker, published on 24 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-863 (Incorrect Authorization), CWE-290 (Authentication Bypass by Spoofing)

## Which versions are affected by CVE-2026-25660?

3 open source packages ship an affected version, including codechecker. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `codechecker` | PyPI | All versions to 6.27.3 | None |
| `codechecker` | PyPI | All versions to 6.27.3 | None |
| `codechecker` | PyPI | All versions to 6.27.3 | None |

Products: Ericsson Codechecker.

## How do I fix CVE-2026-25660?

No fix has been published for CVE-2026-25660 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-25660 being exploited?

There is no known exploitation of CVE-2026-25660 in the wild and no public exploit code.

## Other vulnerabilities in Ericsson CodeChecker

- [CVE-2024-10081](https://insights.sbomify.com/CVE-2024-10081/): codechecker vulnerable to authentication bypass when using specifically crafted URLs (critical 10.0)
- [CVE-2024-10082](https://insights.sbomify.com/CVE-2024-10082/): codechecker authentication method confusion vulnerability allows logging in as the built-in root user from an external service (high 8.7)
- [CVE-2024-53829](https://insights.sbomify.com/CVE-2024-53829/): Cross-Site Request Forgery in CodeChecker API (high 8.2)
- [CVE-2023-49793](https://insights.sbomify.com/CVE-2023-49793/): Path traversal in `CodeChecker server` in the endpoint of `CodeChecker store` (medium 6.5)
- [CVE-2025-1300](https://insights.sbomify.com/CVE-2025-1300/): Open redirect in CodeChecker web server (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-25660 and fix it if it is affected.

What it is: CVE-2026-25660 is a critical authentication bypass vulnerability in Ericsson CodeChecker, published on 24 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-25660 in the wild and no public exploit code.

Affected packages and fixed versions:
- codechecker (PyPI): affected all versions up to 6.27.3; no fix listed
- codechecker (PyPI): affected all versions up to 6.27.3; no fix listed
- codechecker (PyPI): affected all versions up to 6.27.3; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-25660/ (Markdown: https://insights.sbomify.com/CVE-2026-25660/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-25660
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-25660
- OSV: https://osv.dev/vulnerability/CVE-2026-25660

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-25660/
Summaries are generated and may contain mistakes; the official description above is the record.