# CVE-2026-40624: AVer PTC cameras Files or Directories Accessible to External Parties

> Remote unauthenticated attackers can achieve arbitrary code execution on AVer PTC cameras via crafted web requests due to improper input validation.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Jun 2026
- **Updated:** 22 Jun 2026
- **Also known as:** GHSA-pg6m-mhv8-fpmp

## What is CVE-2026-40624?

CVE-2026-40624 is a critical path traversal vulnerability in AVer PTC115, published on 18 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Improper input validation in AVer PTC500S, PTC115, PTC500+, and PTC115+ 
cameras may allow a remote, unauthenticated attacker to achieve 
arbitrary code execution via a specially crafted web request.

Weakness: CWE-552 (Files or Directories Accessible to External Parties)

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


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

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

## Is CVE-2026-40624 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-40624 is a critical path traversal vulnerability in AVer PTC115, published on 18 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-40624 in the wild and no public exploit code.

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

## Sources

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

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