# CVE-2026-28511: elabftw has entry title leakage through autocompletion search

> Authenticated users can view titles of unauthorized resources via search, potentially leaking sensitive project or patient identifiers.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **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:** 1 Jun 2026
- **Updated:** 2 Jun 2026
- **Also known as:** GHSA-wm4r-p2jg-2mj3

## What is CVE-2026-28511?

CVE-2026-28511 is a medium-severity vulnerability in elabftw, published on 1 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

eLabFTW is an open source electronic lab notebook. Prior to version 5.4.2, in certain cases, an authenticated user performing a numeric reference/search can return results that include resources the requesting user is not authorized to view. The exposed information is limited (only the title). Attempts to access the underlying protected resource content remain blocked by authorization checks. Version 5.4.2 fixes the issue.

# Affected Scope

Cross-scope visibility of titles.
No confirmed bypass of content-level access controls

# Preconditions

An authenticated user account

No special privileges required beyond standard access

# Impact

This may enable unauthorized disclosure of sensitive information if confidential data is included in resource titles. Examples could include project names, patient identifiers, or other regulated information embedded in titles.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Elabftw Elabftw.

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

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

## Is CVE-2026-28511 being exploited?

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

## Other vulnerabilities in elabftw

- [CVE-2021-43834](https://insights.sbomify.com/CVE-2021-43834/): Incorrect Authentication in elabftw (critical 9.1)
- [CVE-2024-28100](https://insights.sbomify.com/CVE-2024-28100/): Stored Cross-site Scripting leading to arbitrary actions taken on behalf of users in elabftw (high 8.9)
- [CVE-2019-12185](https://insights.sbomify.com/CVE-2019-12185/): File upload in n/a (high 8.8)
- [CVE-2024-25632](https://insights.sbomify.com/CVE-2024-25632/): Unauthorised granting of administrator privileges over arbitrary teams under certain circumstances (high 8.6)
- [CVE-2025-25206](https://insights.sbomify.com/CVE-2025-25206/): Incorrect input validation could allow an authenticated user to read sensitive information (high 8.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-28511 is a medium-severity vulnerability in elabftw, published on 1 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-28511 in the wild and no public exploit code.

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

## Sources

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

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