# CVE-2026-12686: Incorrect authorisation in Adiss’s Biloop

> Authenticated users can bypass authorization checks to access and modify other companies' sensitive data in Adiss Biloop.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:L/SC:H/SI:H/SA: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:** 6 Jul 2026
- **Updated:** 6 Jul 2026
- **Also known as:** GHSA-67j5-pj6c-m82p

## What is CVE-2026-12686?

CVE-2026-12686 is a critical missing authorization vulnerability in Adiss Biloop, published on 6 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An authenticated user could manipulate a company ID parameter in a POST request to the backend to gain unauthorised access to other companies hosted within the same subdomain environment. The application does not adequately verify whether the requested company ID belongs to the authenticated user’s session, resulting in a cross-tenant authorisation bypass. If this vulnerability is successfully exploited, it allows unauthorised access to sensitive customer information, including billing data, and may enable the unauthorised modification of third-party data.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-12686 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-12686 is a critical missing authorization vulnerability in Adiss Biloop, published on 6 Jul 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-12686 in the wild and no public exploit code.

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

## Sources

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

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