# CVE-2026-92763: Rundeck through 6.2.1 Authorization Bypass via Project Import

> Attackers with import permissions can bypass authorization to modify security settings, potentially leading to privilege escalation and code execution.

- **Severity:** High 8.6 (`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`)
- **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 Sep 2026
- **Updated:** 17 Sep 2026
- **Also known as:** GHSA-9cq6-jmp6-5vf7

## What is CVE-2026-92763?

CVE-2026-92763 is a high-severity missing authorization vulnerability in rundeck, published on 16 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Rundeck through 6.2.1 fails to properly authorize the importConfig and importNodesSources parameters in the project archive import endpoint. Attackers with only the import action can replace project configuration files including security-relevant settings like node executors and SSH key paths that affect job execution.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-92763 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92763 is a high-severity missing authorization vulnerability in rundeck, published on 16 Sep 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-92763 exists.

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

## Sources

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

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