# CVE-2025-27101: Broken Access Control in Opal filesystem's copy functionality exposes all user data

> Low-privilege users can copy parent directories to temp folders, exposing all user data and bypassing access controls in the Opal biobank application.

- **Severity:** High 7.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:P`)
- **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:** 11 Mar 2025
- **Updated:** 12 Mar 2025
- **Also known as:** AZL-62432, GHSA-rxmx-gqjj-vhv8

## What is CVE-2025-27101?

CVE-2025-27101 is a high-severity missing authorization vulnerability in obiba opal, published on 11 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Opal is OBiBa’s core database application for biobanks or epidemiological studies. Prior to version 5.1.1, when copying any parent directory to a folder in the /temp/ directory, all files in that parent directory are copied, including files which the user should not have access to. All users of the application are impacted, as this is exploitable by any user to reveal all files in the opal filesystem. This also means that low-privilege users such as DataShield users can retrieve the files of other users. Version 5.1.1 contains a patch for the issue.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2025-27101?


## How do I fix CVE-2025-27101?

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

## Is CVE-2025-27101 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-27101 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-27101 and fix it if it is affected.

What it is: CVE-2025-27101 is a high-severity missing authorization vulnerability in obiba opal, published on 11 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-27101 exists.

Affected product: obiba opal. 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-2025-27101/ (Markdown: https://insights.sbomify.com/CVE-2025-27101/index.md)
```

## Sources

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

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