# CVE-2026-7292: o2oa NodeAgent NodeAgent.java syncFile improper authorization

> Remote attackers can exploit improper authorization in o2oa NodeAgent's syncFile function to access or modify data without proper permissions.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Apr 2026
- **Updated:** 29 Apr 2026
- **Also known as:** GHSA-6vc8-m3xm-53rv

## What is CVE-2026-7292?

CVE-2026-7292 is a medium-severity missing authorization vulnerability in o2oa, published on 28 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A security vulnerability has been detected in o2oa up to 10.0. This impacts the function syncFile of the file NodeAgent.java of the component NodeAgent. The manipulation leads to improper authorization. The attack can be initiated remotely. The complexity of an attack is rather high. The exploitability is said to be difficult. The exploit has been disclosed publicly and may be used. The project was informed of the problem early through an issue report but has not responded yet.

Weakness: CWE-285 (Improper Authorization), CWE-266 (Incorrect Privilege Assignment)

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


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

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

## Is CVE-2026-7292 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-7292 is a medium-severity missing authorization vulnerability in o2oa, published on 28 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-7292 exists.

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

## Sources

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

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