# CVE-2026-10549: Privilege escalation in Yandex Database

> Remote attackers with valid LDAP credentials can bypass group checks to gain unauthorized database access and escalate privileges.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:L/SI:L/SA:L/AU:Y`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Jun 2026
- **Updated:** 2 Jun 2026
- **Also known as:** GHSA-4x3h-p6xh-h5x5

## What is CVE-2026-10549?

CVE-2026-10549 is a medium-severity authentication bypass vulnerability in Yandex Database, published on 2 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

LDAP filter injection vulnerability in Yandex Database prior to 25.3.1.25 allows a remote attacker with valid LDAP credentials to bypass group membership checks resulting in unauthorized access to the database.

Weakness: CWE-280 (Improper Handling of Insufficient Permissions or Privileges)

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


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

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

## Is CVE-2026-10549 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-10549 is a medium-severity authentication bypass vulnerability in Yandex Database, published on 2 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-10549 in the wild and no public exploit code.

Affected product: Yandex Database. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-10549/ (Markdown: https://insights.sbomify.com/CVE-2026-10549/index.md)
```

## Sources

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

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