# CVE-2026-63085: Axelor Open Platform 8.x < 8.2.2 Authorization Bypass via Nested Relational Record Persistence

> Authenticated non-admin users can escalate privileges to admin by bypassing field restrictions during nested relational record persistence.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/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:** 16 Jul 2026
- **Updated:** 17 Jul 2026
- **Also known as:** GHSA-fgwg-8qwr-qvw3

## What is CVE-2026-63085?

CVE-2026-63085 is a high-severity vulnerability in axelor-open-platform, published on 16 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Axelor Open Platform versions 8.x prior to 8.2.2 contains an authorization bypass vulnerability that allows authenticated non-admin users to escalate privileges by exploiting unenforced field restrictions on nested relational save operations. Attackers can modify sensitive User record fields such as roles and group by submitting changes through a related entity's save path, bypassing the USER_RESTRICTED_FIELDS control and causing the JPA persistence layer to flush attacker-supplied admin role and group assignments on commit.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2026-63085 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-63085 is a high-severity vulnerability in axelor-open-platform, published on 16 Jul 2026. 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-2026-63085 exists.

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

## Sources

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

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