# CVE-2026-22676: Barracuda RMM < 2025.2.2 Privilege Escalation via Insecure Directory Permissions

> Local attackers can gain SYSTEM privileges by modifying files in an insecure directory executed by the automation service.

- **Severity:** High 8.5 (`CVSS:4.0/AV:L/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Apr 2026
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-g6hr-fwwc-8cg8

## What is CVE-2026-22676?

CVE-2026-22676 is a high-severity vulnerability in Barracuda Networks RMM, published on 15 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Barracuda RMM versions prior to 2025.2.2 contain a privilege escalation vulnerability that allows local attackers to gain SYSTEM-level privileges by exploiting overly permissive filesystem ACLs on the C:\Windows\Automation directory. Attackers can modify existing automation content or place attacker-controlled files in this directory, which are then executed under the NT AUTHORITY\SYSTEM account during routine automation cycles, typically succeeding within the next execution cycle.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

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


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

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

## Is CVE-2026-22676 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-22676 is a high-severity vulnerability in Barracuda Networks RMM, published on 15 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-22676 in the wild and no public exploit code.

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

## Sources

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

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