# CVE-2026-18348: Velociraptor NETWORK ACL bypass via upload_azure / upload_sftp / upload_smb VQL plugins

> Authenticated analysts can bypass network ACLs via upload plugins to perform internal reconnaissance and exfiltrate data.

- **Severity:** Medium 4.1 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Aug 2026
- **Updated:** 11 Aug 2026
- **Also known as:** GHSA-qx94-26r3-gv6g

## What is CVE-2026-18348?

CVE-2026-18348 is a medium-severity missing authorization vulnerability in Rapid7 Velociraptor, published on 11 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Missing authorization check in the upload_azure, upload_sftp, and upload_smb VQL plugins allows an authenticated analyst-role user can initiate attacker-controlled outbound network connections from the Velociraptor server, bypassing the NETWORK ACL permission boundary. This enables internal network reconnaissance via port oracle and potential data exfiltration to external endpoints.

Weakness: CWE-863 (Incorrect Authorization)

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


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

Apply the vendor's patch.

## Is CVE-2026-18348 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-18348 is a medium-severity missing authorization vulnerability in Rapid7 Velociraptor, published on 11 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-18348 in the wild and no public exploit code.

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

## Sources

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

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